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. Wiele warunków może zaostrzyć następujące problemy: powolne uruchamianie systemu Windows
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:
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 list in the Internet Protocol properties of this computer.
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
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):
5 lis 2015 · 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 list in the Internet Protocol properties of this computer.
The loopback IP address should be configured as one of the DNS servers on each active network adapter, but not as the first DNS server. If the loopback IP address is the first entry in the list of DNS servers, Active Directory might be unable to find its replication partners.
