If this this is the wrong forum I apologize.
I have set up a Windows 2012 DirectAccess Server using the single adapter configuration. I am in a split brain dns
Internal / External domains are the same. Not my doing.
I have an Remote Access operational status page with green ticks on all services. My test client has picked up the Direct Access Client GPO, The client HTTPS adapter is active and shows the correct url to connect to. however the client cannot connect as when is tries to resolve https://directaccess.mydomain.com.au it is putting an additional mydomain.com.au on the end "https://directaccess.mydomain.com.au.mydomain.com.au"
This behavior only happens to domain joined computers as I can resolve the directaccess.mydomain.com.au from an external non domain machine
If I do a nslookup directaccess.mydomain.com.au. Notice the dot on the end!!! the external client resolves the correct direct access external address?
My understanding is if I was to add a NRPT rule for directaccess.mydomain.com.au, the test machine on a external connection would see this and ignore other suffix's.Has anyone seen this behavior before?
Cheers
Shane