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: slow Windows startup
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
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. If events in the AD DS event log indicate that there is a problem with DNS name resolution, consider adding the IP address of another DNS server for this domain to the DNS server ...
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):
Symptoms. On a Windows-based computer that is hosting Active Directory domain controllers, the DNS server roles stop responding (hangs) for 15 to 25 minutes after the Preparing network connections message is displayed and before the Windows logon prompt (Ctrl+Alt+Del) is displayed.
Perform a quick DNS propagation lookup for any hostname or domain, and check DNS data collected from all available DNS Servers to confirm that the DNS records are fully propagated. Ads keep servers running.
