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 · DNS Event ID 4013 in the DNS event log indicates that DNS service startup was delayed. It's because inbound replication of Active Directory partitions hadn't occurred. Multiple conditions can exacerbate the following issues:
28 lut 2023 · It could be one of many things causing this issue. Go through this troubleshooting guide which should help you resolve this issue. https://learn.microsoft.com/en-us/windows-server/identity/ad-ds/manage/troubleshoot/verify-dns-functionality-to-support-directory-replication. kind regards.
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
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.
You need to configure the domain controllers such that the primary DNS resolver on DC1 is DC2, and the primary DNS resolver on DC2 is DC1, then set 127.0.0.1 as the secondary DNS resolver on both DC1 and DC2, and finally, do not reboot them at the same time.
5 cze 2014 · 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.
