Resolution problems...

  • Thread starter Thread starter Scott McDonald
  • Start date Start date
S

Scott McDonald

We have 2 windows DNS servers and one linux DNS server. Generally the linux
box resolves for our web servers and doesn't dynamically update. Internally
all of our systems getting their addresses from the DHCP server can resolve
everything just fine, however external when connected to VPN which uses our
DHCP server to dish out addresses to those clients we constantly have
resolution issues especially with the linux web servers that the linux DNS
box resolves for. Our DNS servers are setup to forward to that linux DNS for
unknown addresses, and our client systems, again including the VPN clients
are given both Windows DNS and the linux DNS through DHCP, yet the VPN
clients can't resolve any of the web sites. We also see problems trying to
get to Outlook Web Access on our Exchange 2003 server when connected to VPN,
but outlook on those same systems on the same VPN connection works fine.

Anyone?

Thanks!

Scott
 
Why set both Ms and Linux dns ip's in "dns server" dhcp scope,
if Ms dns forwards any unknown zone queries anyway?
 
Our Macs use our DHCP and they tend to have issues with not having that
entry in the DHCP scope, I can't recall exactly what the issue was, but I
know we put it there for a reason.

Thing is, why would having it in the scope and as a forwarder for the
Windows systems be a problem? That wouldn't cause this would it?
 
Then why not try to enter Macs dns manually if only
a few or if many isolate to a specific dhcp scope grouping
together in a specific vlan for Macs only. That would be
the ideal in a perfect world anyhow {:-)
 
The thing to remember here is that, when a client is connected by VPN,
they are effectively "inside" your network. They should use the DNS service
which your local workstations use.

Because of this, they will get a different view of your network if they
are on VPN from the view they get over the Internet (when they connect as an
external user).
 
Back
Top