DNS Issues

sfletcher1959
sfletcher1959 used Ask the Experts™
on
Okay, I have a server that we will call server1.domainname.com.  This server has one NIC that has a static IP address of 192.xxx.xxx.11 and pings with good response times.

If I tracert 192.xxx.xxx.11 address it returns server1.domainname.com.  So this is correct.

However is if I ping server1.domainname.com, it returns 192.xxx.xxx.114.  If I tracert 192.xxx.xxx.114 it doesn't resolve to any name, just returns the path and times.

If I look at DNS, there isn't anything  listed for 192.xxx.xxx.114 on any DC.  I am having intermittent connectivity problems with our backups and wasn't sure if it was related to this weird IP address.

How do I determine where this x.114 IP address is coming from?
Comment
Watch Question

Do more with

Expert Office
EXPERT OFFICE® is a registered trademark of EXPERTS EXCHANGE®
Commented:
Open a command prompt.
Type nslookup and hit enter
then do:  set type=ns
and hit enter
then enter the full name of your server:  server1.domainname.com

This will return the nameserver that the dns lookup is coming from.
Check that it is the correct one, and check that the record does not exist in the DNS server database.

Also on you client in the same command window,, do an:  ipconfig /flushdns
this will clear the dns resolver cache and makes sure that you do not have any stale or old records cached on your machine.

Then post results ;-)
Bartender_1Microsoft Network Administrator

Commented:
Could you try this:

run a command from the command prompt on your workstation


ipconfig /flushdns

then try running the ping server1.domainname.com again, does it still return the .114 address?


Bartender_1
Top Expert 2012
Commented:
If you ping -a 192.xxx.xxx.114 what name comes back?

Some where on the network you have a 192.xxx.xxx.114

Commented:
Have you checked DHCP on the server to see if there is an active lease for 192.xxx.xxx.114?

I'm thinking the ipconfig /flushdns command suggested above should likely fix your issue.

Author

Commented:
Okay, the results of the NS Lookup are below and it is showing the wrong IP address.

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Users\myname.domainname>nslookup
Default Server:  DomainController.DomainName.com
Address:  192.xxx.xxx.25

> server1.prorizon.com
Server:  DomainController.Domainname.com
Address:  192.xxx.xxx.25

Name:    server1.prorizon.com
Address:  192.xxx.xxx.114

>

I then did the same thing after a ipconfig /flushdns, with the same results.


C:\>ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.

C:\>nslookup
Default Server: DomainController.prorizon.com
Address:  192.xxx.xxx.25

> server1.DomainName.com
Server:  DomainController.prorizon.com
Address:  192.xxx.xxx.25

Name:    server1.DomainName.com
Address:  192.xxx.xxx.114

>
Top Expert 2012

Commented:
You have a record some where or host file.

If you ping just server1 name without FQDN what address do you get back

Author

Commented:
Ping -a shows:


> ping -a 192.xxx.xxx.114
Server:  [192.xxx.xxx.114]
Address:  192.xxx.xxx.114

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to 192.xxx.xxx.114 timed-out
>

Author

Commented:
When I ping by server name only and not include the FQDN it still responds back with the same IP address.

Author

Commented:
Okay, I lied.  I did find a host record for that server with the wrong IP address.  I swore I looked on multiple occasions, but now suddenly it is there.  All is well with the world now.

Commented:
if the nslookup returns a faulty address then there is a wrong entry in the DNS, delete or correct that entry in the dns server and it should be ok

Do more with

Expert Office
Submit tech questions to Ask the Experts™ at any time to receive solutions, advice, and new ideas from leading industry professionals.

Start 7-Day Free Trial