Discussion Locked

Why is this in my DNS?

0 helpful
8 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I noticed a unfamiliar Address in my DNS server it 192.168.1.101 This is not the servers address but if I am on a client machine and I ping the server name this is the address that the name is resolved to. What is this? Will it cause problems?

8 replies

by lordinfidel

A- That is an pvt address.

B, Does any of your network adapters have that address bound to it?

When you ping the server name, does it reply?

If so, go the server that you are "pinging" and disconnect it from the network.

Then from the client machine, ping it again. Does it answer? If so, you have another machine on the netwk with that name and it registered itself with dns.

If it does not answer, then that IP is bound to that NIC on the srvr. I would delete the entry in dns, reboot the server, and see if it re-registers iteslf in DNS. (I am assuming that you have AD installed).

Oh, yes, this will cause problems if this is not the correct server.

When it's unplugged and you get a reply, you then have to search for the machine that is replying. This can be done by looking in the arp table or sending a net message to that IP.

by dennisbv

I my Wins I found this address listed as the master browser. The correct assigned Ip is 192.168.1.2

by thesandman

U did not describe your network, so this is a generic reply.
1. Have any new devices been added to the network (gateway/DHCP Server/Firwall)? If so, this address may be from the new device.
2. Do u have a local or remote server? (this may be the IP assigned by either for DNS resolve)
3. If a new server was added to your network, it may be configured for DNS forwarding to an external DNS location.
4. If u use DHCP for WINS config - the DHCP may be assigning the IP
5. if ur IP auto configured - the script may be corrupted/changed to use the new DNS IP.
6. if all else fails, disconnect the network cable from the server u think supplies DNS (& forwarding) and ping the IP - selectively drop connections until you find the culprit (unless u r not the net admin - then ask them to solve the issue)
** Since the 192.168.x.x series is an internal net use, a NAT system should prevent the DNS requests from leaving the building - more than likely the new DNS is for a forwarding system froman internal server.

by jose_12650

If your DNS server is multihomed, meaning there are more than one NIC in the system, it is possible that one of the NICs has the IP 192.168.1.101, and this address was dynamically assigned by the DHCP. Either you have to remove it or assigned a static IP to it. Try looking into the NIC properties and configure the
DNS tab and input the DNS IP Address. It is also possible that 192.168.1.101, is your alternate DNS IP Address.

This discussion is closed to new replies.