Azure AD Domain Services - auto assigned DNS vs VM IP address conflict?

%3CLINGO-SUB%20id%3D%22lingo-sub-91711%22%20slang%3D%22en-US%22%3EAzure%20AD%20Domain%20Services%20-%20auto%20assigned%20DNS%20vs%20VM%20IP%20address%20conflict%3F%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-91711%22%20slang%3D%22en-US%22%3E%3CP%3EHi%2C%3C%2FP%3E%3CP%3ENew%20to%20Azure%2C%20so%20please%20bear%20with%20me...%3C%2FP%3E%3CP%3EI've%20created%20a%20new%20domain%20(registered%20a%20domain%20within%20Azure)%20and%20then%20activated%20AD%20Domain%20Services%20for%20that%20domain.%3C%2FP%3E%3CP%3ESo%20far%20so%20good.%3C%2FP%3E%3CP%3EI%20have%20created%20a%20new%20VM%20which%20I%20want%20to%20join%20to%20the%20AD%20domain%20and%20use%20it%20to%20administrate%2Fmanage%20AD%26nbsp%3B%3C%2FP%3E%3CP%3EAll%20good%20-%20I%20have%20a%20public%20IP%20address%20and%20an%20auto-assigned%20%26nbsp%3Bprivate%20IP%20address%20%3D%2010.0.2.4%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20can%20RDP%20to%20the%20new%20VM%20via%20its%20public%20IP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20next%20I%20have%20followed%20this%20guide%20to%20configure%20DNS%20settings%20for%20the%20AD%26nbsp%3BService%26nbsp%3B%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Factive-directory-domain-services%2Factive-directory-ds-getting-started-dns%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Factive-directory-domain-services%2Factive-directory-ds-getting-started-dns%3C%2FA%3E%3C%2FP%3E%3CP%3EAnd%20in%20the%20portal%20I%20discover%20that%20there%20are%202x%20IP%20addresses%20available%20to%20configure%20for%20AD%20DNS%20and%20here's%20where%20it%20gets%20confusing%3A%3C%2FP%3E%3CP%3EDNS%20IP%20addresses%20available%20%3D%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fdocs.microsoft.com%2Fen-gb%2Fazure%2Factive-directory-domain-services%2Factive-directory-ds-getting-started-dns%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3E10.0.2.4%3C%2FA%3E%3C%2FP%3E%3CP%3E10.0.2.5%3C%2FP%3E%3CP%3ESo%20the%20first%2010.0.2.4%20is%20the%20same%20as%20for%20my%20new%20VM%20-%20implying%20that%20this%20VM%20is%20a%20DNS%20server%2C%20which%20would%20be%20news%20to%20me%20as%20it%20is%20a%20vanilla%2C%20unconfigured%20VM%20-%20all%20I%20have%20done%20is%20successfully%20RDP%20to%20it.%3C%2FP%3E%3CP%3ESo%20why%20is%20it%20sharing%20an%20IP%20address%26nbsp%3Bthat%20is%20somehow%20associated%20with%20AD%20DNS%20in%20Azure%3F%3C%2FP%3E%3CP%3E%3CBR%20%2F%3EI%20have%20also%20tried%20joining%20the%20VM%20to%20the%20domain%20-%20it%20fails.%20It%20is%20unable%20to%20communicate%20with%2Ffind%20a%20domain%20controller.%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EAny%20ideas%2Fsuggestions%20what%20I%20am%20doing%20wrong%20or%20what%20to%20do%20about%20this%20odd%20DNS%20IP%20addresss%20conflict%20with%20the%20VM%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%20in%20advance%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-91711%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EAzure%20AD%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Occasional Contributor

Hi,

New to Azure, so please bear with me...

I've created a new domain (registered a domain within Azure) and then activated AD Domain Services for that domain.

So far so good.

I have created a new VM which I want to join to the AD domain and use it to administrate/manage AD 

All good - I have a public IP address and an auto-assigned  private IP address = 10.0.2.4

 

I can RDP to the new VM via its public IP.

 

So next I have followed this guide to configure DNS settings for the AD Service 

https://docs.microsoft.com/en-gb/azure/active-directory-domain-services/active-directory-ds-getting-...

And in the portal I discover that there are 2x IP addresses available to configure for AD DNS and here's where it gets confusing:

DNS IP addresses available =

10.0.2.4

10.0.2.5

So the first 10.0.2.4 is the same as for my new VM - implying that this VM is a DNS server, which would be news to me as it is a vanilla, unconfigured VM - all I have done is successfully RDP to it.

So why is it sharing an IP address that is somehow associated with AD DNS in Azure?


I have also tried joining the VM to the domain - it fails. It is unable to communicate with/find a domain controller. 

 

Any ideas/suggestions what I am doing wrong or what to do about this odd DNS IP addresss conflict with the VM?

 

Thanks in advance

 

 

 

0 Replies