Page not found

  • Thread starter Thread starter John P
  • Start date Start date
J

John P

I have an intranet server running 2000. Sometimes when the
clients (2kpro and xp) try to hit the FQDN they receive
page not found. Typing in the ip will work everytime.
NSLOOKUP will resolve the name from the client every time.
If the client is a dhcp client, renewing the adapter will
allow the FQDN to work once again. I have tried moving my
DNS to a 2000 server as it was on an NT server. This did
not help. I looked at the article by MS about the DHCP
client running and this is not the case. Any help would be
greatly appreciated.
 
Because nslookup works evertime and browsing does not (I also assume ping
would not), then I assume you may have two or more dns servers IPs
configured on the client and one or more of them have differing namespace
trees. Point *ALL dns servers on your clients to internal dns servers that
all resolve the same namespace tree. Don't have one pointing to private dns
and another pointing to ISP forwarder - that could/does cause this problem.
Use "ipconfig /all" to check the clients configured DNS Server list.
 
I do have it configured as you say. I will remove the
external DNS entry from my DHCP server and change the
static ones all to point to my internal servers. Thanks
for the quick response. We will know in about 3 days.
Thanks again.
 
3 days? You should know right away. Refresh the client your testing with
using "ipconfig /renew" and check the dns servers and your other tests -
they should all work. Also I don't get something. On first sentense you
say "I do have it configured as you say." Then on next sentense you say "I
will remove the external DNS entry...". That means your changing something
in my mind. Anyway, I think we found the issue and your on the right track.
Post back if more issues.
 
When I said I do have it configured as you say, I refered
to your statement "then I assume you may have two or more
dns servers IPs configured on the client and one or more
of them have differing namespace trees." I won't know
right away because the client currently having the problem
already had an ipconfig /renew completed which usually
fixes it for a while (couple days) and did. I will go test
the machine with the static ip that is having the problem.
Thanks again for the help.
 
OK. This sounds more and more like the issue exactly. The reason an
"ipconfig /registerdns" or /renew works for awhile is because it resets the
DNS Server list to use the first one in the list. This works until a
condition makes the Server List pick the next one in the list, then your
problem starts happening. nslookup does not use the dns client so it always
starts with the first server in the list. That is why a ping may not work,
but nslookup does. hth
 
Back
Top