NLS has stopped working (setup through DirectAccess Wizard)

[chazzy2501]

I guess I'm fallling foul of the Wizard. It setup everfthing and it's been great for the last 3 weeks. The issue now is that the Network Location Server (which is the DA server) is not working correctly. This was all setup by the wizard so I have no idea how to troubleshoot.

 

it does say that the "https://DirectAccess-NLS.DCC-SCH-4505.local" may not be pingable but my DA server is called "DA1.dcc-sch-4505.local" I saw these through the wizards setups in group policy at the time but figured it had put DNS aliases within my DNS server. I've been going through DNS and can't find this or "directaccess-WebProbeHost.DCC-SCH-4505.local" on my DNS server?

 

The outside dns is "server.beaminster.dorset.sch.uk" Direct access was working fine until 3 days ago?

 

Would the DNS expiration kill the aliases?

 

I did a "netsh http show sslcert" and it showed certificates bound to ipv6 and ipv4 addresses, not sure what to check for?

[chazzy2501]

I think DNS scavenging has removed the DNS entries made during the wizard. re-registering the DNS of the DA server only places it's record not the AAAA records. I could rebuild them but should I use the ipv4 or the ipv6 address. why do the ipv6 address and in different numbers they look like port numbers?

[chazzy2501]

fixed... added a aaaa host pointing to my da servers ipv4 address.

[chazzy2501]

could someone post the AAAA records created by the DA wizard? This should give me an idea of how to fix them. (unsure if they should be ipv6 or not...)

[chazzy2501]

Well, I redid the wizard and recorded the DNS entries.

 

 

This doesn't include the servers name da1 which was also 10.44.8.26