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
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 · 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. Check the below articles may help you to resolve this issue:
This test will list DNS records for a domain in priority order. The DNS lookup is done directly against the domain's authoritative name server, so changes to DNS Records should show up instantly. By default, the DNS lookup tool will return an IP address if you give it a name (e.g. www.example.com)
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):
8 maj 2018 · But I’m showing error 4013 “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.
