Quantcast
Channel: Network Infrastructure Servers forum
Viewing all articles
Browse latest Browse all 5877

DIRECTACCESS DNS configuration problem or is a product limitation?

$
0
0

Hi Everyone,

Now that i have the DirectAccess environment working i have seen a problem and i don't know if it is a configuration problem or is a product limitation.

* Connection is done using IPHTTPS

* 2 Interfaces configuration

* Internal DNS Servers are IPv4

When the client connect to directaccess these are applied configuration...

On directaccess, the DNS resolution policy uses fdaa:9bf2:476f:3333::1 servers as DNS server (This is our DirectAccess server intelnal IP).

All Works OK, but now the problem.

Suppose that i'm connected on a remote branch office with local resources using ethernet cable, on this situation, the NLS server is reachable so i work OK.

The problem is if connectivity of the remote branch office is down and there is no access to internet and there is no access to DirectAccess infraestructure (no Directaccess server and no NLS server). On this case, i have IP connectivity (i can access everywhere using IP), i have dns resolution for not principal domain, but i have no dns resolution for the principal domain, because it is trying to use fdaa:9bf2:476f:3333::1 server and this server is not reachable.

This is a configuration problem or is a product limitation ??? i have tryied changing the local name resolution (on directaccess configuration) but i still have the same problem .

Thanks for your help


Viewing all articles
Browse latest Browse all 5877

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>