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 · slow Windows startup. the logging of DNS event 4013 on DNS servers that are configured to host AD-integrated zones, which implicitly reside on computers acting as domain controllers. These conditions include: Configuring a DNS server hosting AD-integrated DNS zones.
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 · 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. Check the below articles may help you to resolve this issue: https://serverfault.com/questions/406946/event-id-4013-the-dns-server-is-waiting-for-active-directory-domain-services
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.
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.
30 wrz 2016 · I am running a single Domain Controller which hosts DNS and DHCP services. Here is the error in plain text: The DNS server is waiting for Active Directory Domain Services to signal that the initial synchronization of the directory has been completed.
