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: slow Windows startup
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
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.
5 cze 2014 · 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.
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.
10 sty 2014 · Configuring domain controllers to point to a single DNS server’s IP address, including the 127.0.0.1 loopback address, represents a single point of failure. This is somewhat tolerable in a forest with only one domain controller but not in forests with multiple domain controllers.
