Cannot ping FQDN after changing the server IP

I changed the IP address of a server.   I have another server that needs to connect to it for backups.  When I ping the server that I changed the IP using the FQDN it finds the previous IP and the ping fails.  If I ping the new IP it finds it.

If I ping the same server from another server using the FQDN it finds the correct IP.

I've done ipconfig /flushdns twice.

So from the server that cannot ping the FQDN what is wrong and how do I fix it.
J.R. SitmanIT DirectorAsked:
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

x
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

DamianIT incCommented:
Check the NICs.

Make sure you have static IPs, and perhaps disable any other NICs that you're not using to make sure the server hasn't decided to 'adopt' another NIC.

Query your DNS server, using NSLOOKUP to test the resolution to the other servers etc.
1
J.R. SitmanIT DirectorAuthor Commented:
Thank you I'll test it as soon as I can
0
Discover the Answer to Productive IT

Discover app within WatchGuard's Wi-Fi Cloud helps you optimize W-Fi user experience with the most complete set of visibility, troubleshooting, and network health features. Quickly pinpointing network problems will lead to more happy users and most importantly, productive IT.

timgreen7077Exchange EngineerCommented:
it could be you need to wait for DNS replication. It generally replicates in about 15 - 60 minutes. if this issue persists then make sure that there are not static entries in DNS for that server. if there are static entries you will need to re-ip that A RECORD with the new IP
0
Shaun VermaakTechnical Specialist IVCommented:
Did you run
ipconfig /registerdns

Open in new window

from this server?
0
David SankovskySenior SysAdminCommented:
For starters, make sure that you have the right DNS server - it hsould be the Domain internal one, not google or other public ones.
If you do, check if the problematic server has a static resolution in the hosts file - might've stayed there from debugs and was forgotten about.
0
J.R. SitmanIT DirectorAuthor Commented:
It has been about 12 hours since I made the change
Both servers have static IP's and only 1
Both have the correct DNS servers
I verified from the DNS server that the old IP was not there
I ran ipconfig /registerdns and I will check logs later for errors.
I ran NSlookup.  However, there are errors see below.  172.16.1.14 is a DC, DNS server.  172.16.1.37 is the new IP of the server that cannot be reached via FQDN from 172.16.1.42.  172.16.1.42 is the server that needs to reach 172.16.1.37 via FQDN.
 



Microsoft Windows [Version 6.3.9600]
(c) 2013 Microsoft Corporation. All rights reserved.

C:\Users\Administrator.LASPCA>nslookup
Default Server:  spcala292.laspca.corp
Address:  172.16.1.14

> ipconfig /registerdns
Unrecognized command: ipconfig /registerdns
> ipconfig ?
Unrecognized command: ipconfig ?
> ipconfig
Server:  spcala292.laspca.corp
Address:  172.16.1.14

*** spcala292.laspca.corp can't find ipconfig: Non-existent domain
> ipconfig /all
Unrecognized command: ipconfig /all
> exit

C:\Users\Administrator.LASPCA>ipconfig /all

Windows IP Configuration

   Host Name . . . . . . . . . . . . : RPS_VM
   Primary Dns Suffix  . . . . . . . : laspca.corp
   Node Type . . . . . . . . . . . . : Hybrid
   IP Routing Enabled. . . . . . . . : No
   WINS Proxy Enabled. . . . . . . . : No
   DNS Suffix Search List. . . . . . : laspca.corp

Ethernet adapter Ethernet 2:

   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft Hyper-V Network Adapter
   Physical Address. . . . . . . . . : 00-15-5D-01-0B-07
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes
   IPv4 Address. . . . . . . . . . . : 172.16.1.37(Preferred)
   Subnet Mask . . . . . . . . . . . : 255.255.0.0
   Default Gateway . . . . . . . . . : 172.16.1.6
   DNS Servers . . . . . . . . . . . : 172.16.1.14
                                       172.16.1.9
   NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter isatap.{FF9434FC-1627-4418-8D68-D81B70A85A70}:

   Media State . . . . . . . . . . . : Media disconnected
   Connection-specific DNS Suffix  . :
   Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2
   Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
   DHCP Enabled. . . . . . . . . . . : No
   Autoconfiguration Enabled . . . . : Yes

C:\Users\Administrator.LASPCA>nslookup
Default Server:  spcala292.laspca.corp
Address:  172.16.1.14

> server 172.16.1.37
Default Server:  RPS_VM.laspca.corp
Address:  172.16.1.37

> server 172.16.1.42
Default Server:  [172.16.1.42]
Address:  172.16.1.42

> set q-mx
> laspca.corp
Server:  [172.16.1.42]
Address:  172.16.1.42

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to [172.16.1.42] timed-out
> server 172.16.1.37
DNS request timed out.
    timeout was 2 seconds.
Default Server:  [172.16.1.37]
Address:  172.16.1.37

> set q-mx
> laspca.corp
Server:  [172.16.1.37]
Address:  172.16.1.37

*** [172.16.1.37] can't find laspca.corp: No response from server
> laspca.corp
0
J.R. SitmanIT DirectorAuthor Commented:
I just found that the old server was listed on one of the DNS servers, but not the other.  I deleted it.  Hopefully, that will fix the problem.
0
J.R. SitmanIT DirectorAuthor Commented:
just wanted to make sure that it is clear, I can ping the FQDN from all servers except one.
0
J.R. SitmanIT DirectorAuthor Commented:
here is the latest Nslookup.

Microsoft Windows [Version 10.0.14393]
(c) 2016 Microsoft Corporation. All rights reserved.

C:\Users\jsitman>ping rps_vm

Pinging rps_vm [172.16.1.96] with 32 bytes of data:
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.

Ping statistics for 172.16.1.96:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\jsitman>ping rps_vm

Pinging rps_vm [172.16.1.96] with 32 bytes of data:
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.

Ping statistics for 172.16.1.96:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\jsitman>nslookup
Default Server:  SPCALA292.laspca.corp
Address:  172.16.1.14

> server 172.16.1.37
Default Server:  RPS_VM.laspca.corp
Address:  172.16.1.37

> exit

C:\Users\jsitman>ping rps_vm

Pinging rps_vm [172.16.1.96] with 32 bytes of data:
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.
Reply from 172.16.1.42: Destination host unreachable.


Ping statistics for 172.16.1.96:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

C:\Users\jsitman>nslookup
Default Server:  SPCALA292.laspca.corp
Address:  172.16.1.14

> server rps_vm
Default Server:  rps_vm.laspca.corp
Address:  172.16.1.37

>
0
Shaun VermaakTechnical Specialist IVCommented:
Where are you pinging FQDN in #a42488118? RPS_VM.laspca.corp is FQDN and RPS_VM is the NetBIOS name.
Do you have correct suffixes added?
0
J.R. SitmanIT DirectorAuthor Commented:
if I ping rps_vm.laspca.corp or rps_vm from Udpserver (172.16.1.42) both pings return "destination host unreachable"
0
atlas_shudderedSr. Network EngineerCommented:
ipconfig /flushdns on the affected server?
0
Shaun VermaakTechnical Specialist IVCommented:
I've done ipconfig /flushdns twice.
In OPs question
0
David SankovskySenior SysAdminCommented:
Have you checked the host file in the affected server?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Ashok DewanFreelancerCommented:
Best way to flush dns and check host file and open the wireshark to capture the packets to know who is resolving the name into IP 172.16.1.96 i.e. Pinging rps_vm [172.16.1.96] with 32 bytes of data:.
Wireshark is great tool.

Look for DNS packets.

'A' is for A record, you can choose 'any'  instead of A.

DO NSLOOKUP LIKE BELOW
C:\WINDOWS\system32>nslookup
Default Server:  UnKnown
Address:  192.168.2.41

> set type=A
> google.com
Server:  UnKnown
Address:  192.168.2.41

Non-authoritative answer:
Name:    google.com
Address:  216.58.196.206

> australia.com
Server:  UnKnown
Address:  192.168.2.41

Non-authoritative answer:
Name:    australia.com
Address:  40.126.229.53

>


IN YOUR NSLOOKUP, SERVER command is focusing it on a different DNS server i.e. 172.16.1.37 RPS_VM which is not a DNS server may be right?.
https://technet.microsoft.com/en-us/library/cc940085.aspx
0
J.R. SitmanIT DirectorAuthor Commented:
Made the change in the Host file and that fixed it.  Before I close this, is there an explanation why this would happen?
0
David SankovskySenior SysAdminCommented:
Host file precedes any DNS lookup
So even if the DNS was correct, if the host file pointed to the wrong address, the computer would go to the wrong one.

<As a side note, I should point out that on Linux machines the DNS resolution order can be changed so that the host file be used only afterthe DNS failed, I assume it can also be done on windows, but I do not know how>
0
Ashok DewanFreelancerCommented:
1) system first check itself
2) then it check  DNS cache.
3) then it check to host file.
4) at the end it ask to DNS server on  network.
0
J.R. SitmanIT DirectorAuthor Commented:
Editing the Host file fixed the problem.   Is that file needed or can it be deleted?
0
David SankovskySenior SysAdminCommented:
Deleting it is useless as the system will recreate it.
Just don't edit it unless you have to.
0
J.R. SitmanIT DirectorAuthor Commented:
thanks
0
J.R. SitmanIT DirectorAuthor Commented:
thank you
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
DNS

From novice to tech pro — start learning today.