Discussion Locked

nslookup and tracert with WINS/DNS

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

I have a workstation which is a DHCP client. The client receives IP, WINS, DNS from the DHCP server.

We have a pre-staged test environment over at another facility. This environ has its own DNS servers that contain duplicate entries for production servers here in the live environ. At a DHCP client we change DNS servers via network manager such that the client resolves off of the pre-stage environ. nslookup from the command line returns pre-stage values for servers. A tracert to one of theseservers (by name, not IP) still traces to the current prod env! How? Why are tracert and nslookup resolving FQDN differently?

BTW: the destination host is a Solaris server, non-registered in WINS, we have no static mappings, the client isn't using a host file. This can be corrected with lmhosts entries. Does WINS refer to DNS servers at all? My thought is that the WINS server might be querying one of the local (prod) DNS servers...

0 replies

No replies were posted before this discussion closed.

This discussion is closed to new replies.