Search results
26 gru 2023 · Identyfikator zdarzenia DNS 4013 w dzienniku zdarzeń DNS wskazuje, że uruchamianie usługi DNS zostało opóźnione. Dzieje się tak dlatego, że replikacja przychodząca partycji usługi Active Directory nie miała miejsca.
26 gru 2023 · This article resolves the event ID 4013 logged in the DNS event log of domain controllers that are hosting the DNS server role after Windows starts. Original KB number: 2001093. Symptoms. On a Windows-based computer that's hosting Active Directory domain controllers, the DNS server roles stop responding for 15 to 25 minutes.
28 lut 2023 · I'm trying to troubleshoot 4013 problem on my Domain Controllers. Both randomly present this error, related to AD synchronization with other DCs in the enviroment. Then I run the "dcdiag/test:DNS" and the result is this (name are modified in order to hold privacy): Can someone explain me the output?Becouse seems that the DNS is working.
24 cze 2019 · Try restarting the DC and check again. If this does not help, please make sure that: The DC is pointing as another DC / DNS server as primary DNS server. Use nslookup to check that all is okay with DNS resolution. Needed ports for AD replication are not blocked: Active Directory Replication over Firewalls | Microsoft Learn.
8 maj 2018 · Troubleshoot DNS Event ID 4013 - Windows Server. Solves an issue that the DNS server can't load AD-integrated DNS zones.
The DNS server service cannot start until the initial synchronization is complete because critical DNS data might not yet be replicated onto this domain controller.
12 cze 2014 · It is giving the following error with some regularity: 4013 DNS-Server-Service. The DNS server is waiting for Active Directory Domain Services (AD DS) to signal that the initial synchronization of the directory has been completed.
