-1

I'm attempting to set up DirectAccess Remote Access on a standalone Windows Server 2012 server (DC, DHCP, DNS etc.) are handled on another server.

I used the wizard but DNS kept throwing warning icons in the status viewer. I've tried setting it manually to the servers local IPv4 address, local IPv6 address, the domain controllers local IPv4 address, and also by deleting the entry and manually hitting Detect and then Verify (passed) but once saved the warning icon comes back with the same error message.

Enterprise DNS servers (192.168.100.33,::1) used by DirectAccess clients for name resolution are not responding. This might affect DirectAccess client connectivity to corporate resources.

enter image description here

enter image description here

How do I sort it?

user6888062
  • 245
  • 1
  • 6
  • 11

1 Answers1

2

When adding the DNS server address here, the best way is to use "detect" as I describe here:

https://directaccess.richardhicks.com/2015/09/22/directaccess-dns-not-working-properly/

You should NOT enter an IPv4 address of an internal DNS server or ::1, those are both incorrect. Also, DNS servers do not have to reside on member servers, they most certainly can be (and are commonly) installed on domain controllers.

Let me know if that doesn't work for you and I'll help you continue troubleshooting. There are a number of other things that can cause server responsiveness warnings in the Remote Access Management console.

Richard M. Hicks
  • 101
  • 3