IE DNS resolution problem

  • Thread starter Thread starter magenb
  • Start date Start date
M

magenb

IE seemes not to resolve an intranet web site in a remote office,
however nslookup does. All the machine on the remote site are having
the problem, all the machine are pointed to internal DNS servers.

If I add the entry into the host file or use the IP adddress then the
site works fine.

External sites work fine.

If I set a machine in head office to use the same DNS server the as the
remote office, I dont have any problems.

Any ideas?
 
In
magenb said:
IE seemes not to resolve an intranet web site in a remote office,
however nslookup does. All the machine on the remote site are having
the problem, all the machine are pointed to internal DNS servers.

If I add the entry into the host file or use the IP adddress then the
site works fine.

External sites work fine.

If I set a machine in head office to use the same DNS server the as
the remote office, I dont have any problems.

Any ideas?
Click to expand...

If you point to the DNS server in the other location and it works, then
that's telling us the entry is not in your local DNS. To fix the issue
highly depends on your configuration, infrastructure and your AD (is using
AD) setup.

Is this under the same domain name? If it is, and you are using
Primary/Secondaries, then it's telling me that zone transfers are not
working.

If the same domain name, and the zone is AD integrated, then it's telling me
AD replication is not functioning properly.

If totally different domain names, then it would be logical to create a copy
of the zone (as a secondary) on your server so your local clients can easily
resolve it.

If not sure which solution to use, please specifically explain your AD
infrastructure (domain names, one or more forests or domains, etc), your DNS
infrastructure, and what operating system, to give you a specific solution.

:-)


--
Regards,
Ace

Please direct all replies ONLY to the Microsoft public newsgroups
so all can benefit.

This posting is provided "AS-IS" with no warranties or guarantees
and confers no rights.

Ace Fekay, MCSE 2003 & 2000, MCSA 2003 & 2000, MCSE+I, MCT, MVP
Microsoft Windows MVP - Windows Server - Directory Services

Security Is Like An Onion, It Has Layers
HAM AND EGGS: A day's work for a chicken;
A lifetime commitment for a pig.
 
We are in the process upgrading to Win2k3 AD, however one of our DNS
servers is still running WinNT4, it is all the same domain.

Both DNS servers are on the same network, over here. DNS1 (Win2k3) and
DNS2(WinNT4).

The remote office is set to use DNS2 as the primary DNS server,
nslookup will resolve the name but IE will not.

When I change a client machine here (Win2k) to use DNS2 and flush the
DNS cache it works fine.

So it appears as though the DNS2 can resolve the name, but for one
reason or another IE and all other apps just can't in the remote
office.
 
In
magenb said:
We are in the process upgrading to Win2k3 AD, however one of our DNS
servers is still running WinNT4, it is all the same domain.

Both DNS servers are on the same network, over here. DNS1 (Win2k3) and
DNS2(WinNT4).

The remote office is set to use DNS2 as the primary DNS server,
nslookup will resolve the name but IE will not.

When I change a client machine here (Win2k) to use DNS2 and flush the
DNS cache it works fine.

So it appears as though the DNS2 can resolve the name, but for one
reason or another IE and all other apps just can't in the remote
office.
Click to expand...


I see. What sort of line do you have to the Internet? If ADSL, it sounds
more like an MTU issue. This is a common issue with ADSL due to the PPPoE
overhead, but not with SDSL, since there is no overhead.

Test it out just to see if it is an MTU issue.

MTU - How to test and how to set in registry:
http://gw.renner.bei.t-online.de/windowsxp/mtu.htm

Ace
 
Back
Top