Intermittent DNS timeouts with AADDS domain-joined VMs

Question

Hello,

We are making use of Azure Active Directory Domain Services, for managing our domain. All of the connected resources are on the same VNET, using the following topology:

Every so often, more so in the past couple of weeks, DNS times out, interrupting our services. All of our virtual machines are running Windows Server 2019, with the errors logged:

Event ID: 1014
Source: Microsoft Windows DNS Client
Message: Name resolution for the name %1 timed out after none of the configured DNS servers responded.

EventID: 30800
Source: SMBClient
Message: The server name cannot be resolved.
Error: The object was not found.
Server name: ***************
Guidance:
The client cannot resolve the server address in DNS or WINS. This issue often manifests immediately after joining a computer to the domain, when the client's DNS
registration may not yet have propagated to all DNS servers. You should also expect this event at system startup on a DNS server (such as a domain controller) that
points to itself for the primary DNS. You should validate the DNS client settings on this computer using IPCONFIG /ALL and NSLOOKUP.

We have not been able to track down a root cause, and we have experienced several issues within the past week.

Any help would be greatly appreciated.

Thank you

Answer 1

Issue seems to have gone away on its own, probably an issue with AADDS. I opened a ticket with Microsoft Support and have been escalated to several different departments. No one at MS seems to know either.

Answer 2

Hi @Mathew Jung ; did this happen again.

I got this intermittent on few VM which are AD DS joined (via peered VNET)

our AD DS size is "Standard" so we have 2 DC/ DNS managed by MS.