New Hosts added to host pool are not using VNet Custom DNS

%3CLINGO-SUB%20id%3D%22lingo-sub-3076172%22%20slang%3D%22en-US%22%3ENew%20Hosts%20added%20to%20host%20pool%20are%20not%20using%20VNet%20Custom%20DNS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3076172%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20to%20the%20point%20where%20I%20am%20creating%20a%20new%20host%20pool%20and%20the%20host%20creation%20join%20to%20AD%20domain%20failed%20and%20when%20I%20logged%20into%20the%20VM%20the%20reason%20it%20failed%20is%20because%20there%20is%20no%20DNS%20on%20the%20NIC%20in%20the%20VM.%26nbsp%3B%20I%20checked%20and%20the%20VNet%20it%20is%20using%20has%20custom%20DNS%20set%20but%20the%20VM%20is%20not%20using%20it%20so%20there%20is%20no%20way%20to%20communicate%20properly%20with%20the%20domain.%26nbsp%3B%20Has%20anyone%20seen%20this%20and%20what%20did%20you%20do%20to%20get%20the%20hosts%20to%20use%20the%20VNet%20DNS%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-3077658%22%20slang%3D%22en-US%22%3ERe%3A%20New%20Hosts%20added%20to%20host%20pool%20are%20not%20using%20VNet%20Custom%20DNS%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-3077658%22%20slang%3D%22en-US%22%3ENormally%20when%20you%20have%20your%20custom%20dns%20on%20the%20vnet%20it%20should%20work.%20Is%20your%20domain%20controller%20in%20the%20same%20vnet%20or%20in%20another%20vnet%3F%3C%2FLINGO-BODY%3E
Contributor

I am to the point where I am creating a new host pool and the host creation join to AD domain failed and when I logged into the VM the reason it failed is because there is no DNS on the NIC in the VM.  I checked and the VNet it is using has custom DNS set but the VM is not using it so there is no way to communicate properly with the domain.  Has anyone seen this and what did you do to get the hosts to use the VNet DNS?

 

** UPDATE -- So I booted the host pool VM again this morning and logged into it and eventhough it isn't showing DNS when I do ipconfig /all I can ping the FQDN of the DC.  So DNS is there just not showing.  So I am more confused now as to what has changed.  I tried to manually join the computer to the domain yesterday and it failed because it couldn't find it and I used the FQDN of the domain.  

I am going to try to create a new host and see if whatever the issue was yesterday is no longer there and it creates and joins it properly.  

Any other reasons anyone can think of why the join to AD extension would fail.  The log doesn't clearly define the problem from what I can see.  I am using a domain admin credential to join them and placing in an OU and the path is correct.

 

** Another Update--

 

So I created a VM from the Image and it looks like when it boots it is locked on the 'Please wait for the windows module installer' screen upon logon.  So I think that must be the issue.  If the host creation can't get to a desktop to run the extension then that would explain the failure.  Will make sure that I reboot a couple of times before SYSPREP and make into an image to deploy.  Will update once that is done.

 

** More updates--

 

I created a new VM from the previous image.  Logged in and made sure that all windows updates and any other updates had run and then rebooted 2 times with 10 minutes between reboots then logged in and did sysprep and then made a new image.  There was no 'please wait for windows module installer' on the screen after the reboots but when I create hosts from that image I can see on the diagnostics screen that it is showing the 'please wait for windows module installer' and will now fail to join again.  Does anyone know why this is happening and any way to fix this?

2 Replies
Normally when you have your custom dns on the vnet it should work. Is your domain controller in the same vnet or in another vnet?
It is in the same VNet but a different subnet. I can place a non-WVD host in that subnet and it can talk to the DC just fine. The issue is that the host creation process for whatever reason is not using the DNS servers on the VNet.