Windows Forum

Ask something
Discussion Locked

More on W2K and DNS

0 helpful
4 replies

by ratherbfishing 3 views

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Okay..a partial answer and another question concerning the earlier post "W2K and DNS."
In the TCP/IP setting for DNS I had to DNS servers specified. Out Internal DNS Server and our ISP's DNS server. Our Internal DNS server is set as the Primary. The ISP' as the secondary.

I discovered that when I took out the secondary DNS server, then I could resolve local names. So for some reason, W2K was bypassing the Primary DNS server(our internal) and going out to the second one to resolve all names including our internal network names.

So the question is, why is is this happening? Shouldn't the client attempt to first use the Primary DNS server, and only when that fails to resolve the name go to the second one? That is how it works on our NT 4.0 clients.

4 replies

by calves

It could be that the entries in the primary are not properly configure, thus preventing a match with the request.

calves

by calves

Perdon my first answer. I guess I missunderstood the question all together.
It works the same way as with NT.
That should not happen.
My question now is, when you take out the secondary, does Win2K still resolve request for the outside world?

If that is so, something is conflicting in the way Win2K receives the DNS information.

calves

by ratherbfishing

Yes, when the secondary was taken out, it still resolves request to the outside world. The secondary is there for a backup. But I did resolve the problem as follows:

Apparently W2K handles DNS suffixes differently then NT 4 clients. To fix the problem I went into DNS advanced properties, selected "Append these DNS suffixes" and added our internal domain name suffix, e.g., ourdomain.org. I also added the "DNS suffix for this connection."

Thanks for your interest!

This discussion is closed to new replies.