Share via

Windows server 2012R2 DNS issue

Oleg Lutskyi 1 Reputation point
2022-04-26T12:06:09.713+00:00

Hi there,
We have two DCs. One installed in the office DC1 (192.168.20.21) and the other in the cloud MainDC (172.31.32.40).
ipcpnfig DC1:

Windows IP Configuration

Host Name . . . . . . . . . . . . : DC1
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local

PPP adapter RAS (Dial In) Interface:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : RAS (Dial In) Interfac
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
IPv4 Address. . . . . . . . . . . : 192.168.20.60(Preferre
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
NetBIOS over Tcpip. . . . . . . . : Enabled

Ethernet adapter NIC1:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Broadcom NetXtreme Gig
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
IPv4 Address. . . . . . . . . . . : 192.168.20.21(Preferre
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.20.1
DHCPv6 IAID . . . . . . . . . . . : 315105126
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-28-C8-6F-C

DNS Servers . . . . . . . . . . . : 172.31.32.40
192.168.20.21
NetBIOS over Tcpip. . . . . . . . : Enabled

Ipconfig DC2:

Windows IP Configuration

Host Name . . . . . . . . . . . . : MainDC
Primary Dns Suffix . . . . . . . : domain.local
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : domain.local

Ethernet adapter Ethernet 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : AWS PV Network Device #
Physical Address. . . . . . . . . :
DHCP Enabled. . . . . . . . . . . : No
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . :
IPv4 Address. . . . . . . . . . . : 172.31.32.40(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 172.31.32.1
DHCPv6 IAID . . . . . . . . . . . : 319697556
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-26-FC-B5-3D

DNS Servers . . . . . . . . . . . : 192.168.20.21
172.31.32.40
NetBIOS over Tcpip. . . . . . . . : Enabled

On DC1 we received every 15 min Error 4015: "The DNS server has encountered a critical error from the Active Directory. Check that the Active Directory is functioning properly. The extended error debug information (which may be empty) is "". The event data contains the error."
From MainDC Error 4015 AND 4004: "The DNS server was unable to complete directory service enumeration of zone TrustAnchors. This DNS server is configured to use information obtained from Active Directory for this zone and is unable to load the zone without it. Check that the Active Directory is functioning properly and repeat enumeration of the zone. The extended error debug information (which may be empty) is "". The event data contains the error."

Replication is currently working fine. All data is mirrored. Ping passed between DCs. But nslookup result:
From MainDC:

Server: UnKnown

Address: 192.168.20.21

Name: domain
Addresses: 172.31.32.40
192.168.20.21

From DC1:

DNS request timed out.

timeout was 2 seconds.

Server: UnKnown
Address: 172.31.32.40

DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out

Please advise what I missed in configuration and how to fix this issue. Thank you!

Windows for business | Windows Client for IT Pros | Networking | Network connectivity and file sharing
Windows for business | Windows Server | User experience | Other
0 comments

2 answers

Sort by: Most helpful
Most helpful Newest Oldest
  1. Anonymous
    2022-04-26T12:23:43.707+00:00

    Multi-homing a domain controller will always cause no end to grief for active directory DNS. Install the RRAS roles on it's own instance of windows.

    --please don't forget to upvote and Accept as answer if the reply is helpful--

  2. Limitless Technology 39,931 Reputation points
    2022-04-28T07:53:13.15+00:00

    Hi there,

    The DNS Server service relies on Active Directory Domain Services (AD DS) to store and retrieve information for AD DS-integrated zones.

    This error indicates that AD DS is not responding to requests from the DNS Server service. Ensure that AD DS is functioning properly, troubleshoot any problems, and then restart the DNS Server service.

    You can follow the troubleshooting steps from the below article and see if that helps you
    Event ID 4015 — DNS Server Active Directory Integration https://learn.microsoft.com/en-us/previous-versions/windows/it-pro/windows-server-2008-R2-and-2008/cc735674(v=ws.10)?redirectedfrom=MSDN

    ------------------------------------------------------------------------------------------------------------------------

    --If the reply is helpful, please Upvote and Accept it as an answer–

Your answer

Answers can be marked as Accepted Answers by the question author, which helps users to know the answer solved the author's problem.