Hostname ping returns wrong IP

Setup:
2 x Server 2003 DC's
Server 2003 Application Server

We have a server that came out of the rack and ended up on the workbench.  It is still up and in use in a degraded mode. (1 array went down)  When it was plugged into the network both the onboard and the pci gigabit cards were plugged in, but only the gigabit should have been.  The gigabit card is static, the onboard 10/100 is DHCP.  The 2nd cable into the DCHP nic was removed, but we are now running into DNS resolution issues to that server's hostname.  If I ping it by hostname, I get the DHCP address.  I tried rebooting the server, checked all the settings in the DNS/Wins portion of the gigabit tcp/ip, ipconfig /release, ipconfig /flushdns (on client, not on dc yet) nslookup hostname.  Any help is appreciated.
LVL 2
patmoliAsked:
Who is Participating?
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.

gnarCommented:
First, I'm check the DNS zones and make sure there aren't any records sitting around, then clear the  DNS cache on the DNS servers yet.  After that, flush the local DNS cache again and try the ping.  

If that still doesn't work, verify there isn't a hosts file entry, WINS entry, etc., that might be providing that old address.
0
patmoliAuthor Commented:
There is a wrong entry in the Forward Lookup Zone.  Delete it?  What is the best way to clear the dns cache?
0
ryansotoCommented:
There is no issue with deleting the wrong record in the forward lookup zone.  I assume there is the correct record as well...
After you delete it then have the client renew the IP and see if the new record is created in DNS
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

DCenaculoCommented:
If you ping by hostname and it replays with the IP address from the DHCP it's because that IP address was given to someone else. I say this because you wrote: "The 2nd cable into the DCHP nic was removed".

Run this command if you want to know who has the IP now: nbtstat -a ip address.

Go to your DNS server, sort records by name and see if there are more then one record for the same name. If there are more then one entrie for that server name delete them. Verify if it has only one record and if the IP is the corerct, the one from the static configuration.

-Clear all entries in WINS for that server name.
-On the server run the command: nbtstat -RR
-Go to some workstation, and run the command: ipconfig /flushdns
-Ping the server's name, and I think it will be fine.

If you need more help, please feel free to ask for it :)
0
DCenaculoCommented:
If your nic is statically configured you must create manually a record in DNS.
0
gnarCommented:
Yeah, patmoli.  If there's a bad, old record, just delete it.

And to clear the cache on other DNS servers, just right-click the server in the DNS MMC and choose "Clear Cache."  
0
DCenaculoCommented:
If you are not using DHCP anymore on that server, don't delete it. Edit it and put the wright IP address :)
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
patmoliAuthor Commented:
too late... already deleted it.  There was no correct entry.  What now?
0
DCenaculoCommented:
create a new one :) Need help on that ? Just right-click you zone name and create a new host record. If you need help on that please feel free to ask :) You really have to create it :)
0
patmoliAuthor Commented:
I have 2 dc's here.  Will the entry replicate or shout I create a new entry on both?
0
DCenaculoCommented:
Sometimes you must click the zone first to select it and only after thar you can rigth-click it and choose the option New Host :)
0
DCenaculoCommented:
It will replicate automatically :)
0
gnarCommented:
If it's an active directory integrated zone, it'll replicate on it's own soon enough.  You can always reload the zone on the other DC/DNS server sooner if you're impatient.  
0
DCenaculoCommented:
If that server is a DC, I suggest you to run ipconfig /registerdns and then dcdiag /fix.
0
DCenaculoCommented:
A domain controller registers a lot of things besides its IP address in DNS, so client workstations can use its services (SRV records in DNS).

If you nedd more help, plesa feel free to ask :)
0
patmoliAuthor Commented:
Ok, here's where I'm at.  I recreated the record on the DC's with the correct IP.  Left it for a bit, then pinged.  Was the wrong IP again. The server in question is NOT a DC, just a member server in the domain.  Comments?
0
ryansotoCommented:
From the machine you pinged from (client machine)
start run cmd
ipconfig /flushdns

Now try and ping
0
patmoliAuthor Commented:
It changed the record on the DNS back to the old IP

I'm confused.  Just cleared the DNS Cache on the DC's, same problem.  Flush DNS ond it's ok.  Am I missing something here?
0
gnarCommented:
Possibly the serial numbers are out of joint on the two DNS servers for that zone...  if you removed the record from server A that had a lower serial number than server B, server B's zone file (with the old record) might override it.

Could just remove it manually from both servers first, then recreate it after.
0
patmoliAuthor Commented:
I out of here to take care of the kids.  Will continue this at home.  You guys around for a bit?
0
patmoliAuthor Commented:
It seems that after about 30 minutes, the DNS record changes to reflect the DHCP address again.  I need to fix this.
0
gnarCommented:
Could the DHCP server be freaking out and reregistering it with DNS?  Maybe look for an active DHCP lease for that machine and delete it?
0
patmoliAuthor Commented:
No leases for that IP, sequential IP on either side is there, but not that one.  This is really weird
0
gnarCommented:
Ok, we're going to need a chicken, some duct tape, and tears from a virgin...

Or at least maybe delete those records again, enable debug logging on the DNS server, then see what they look like after the records are recreated.

You can enable debug logging by right-clicking the server in the DNS MMC, going to Properties, and checking Log packets for debugging on the Debug Logging tab.  The log file's location can be specified at the bottom of the screen.

0
patmoliAuthor Commented:
done, will wait a bit and review.
0
patmoliAuthor Commented:
Of course as soon as I turn on the logging, it smartens up!  Will update again in a bit.
0
patmoliAuthor Commented:
Thanks!  Seems to be ok now.
0
patmoliAuthor Commented:
While this problem was a bit finicky, I tried just about everything on this topic and it seemed to work.  What I did end up doing was going into the DHCP server hosting on the the 2nd DC and killing the new DHCP session that has that IP...  not sure which solution/combo solution was the final answer here, but to anyone else having a problem like this, the answer is in here!  Thanks for the help guys!
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.