• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 491
  • Last Modified:

Command Line: DHCP / DNS Resolution issues? Not matching results on returns

Hey guys, wanted to seek out some expert opinions on what could be causing this strange return from pinging a number of device/workstations on my network. The issue is as follows.

I want to ping Bobs PC so I open command prompt and type the following:

Ping Bobs-pc

It then returns the address 192.168.1.56

I then attempt to resolve the 192.168.1.56 address

Ping -a 192.168.1.56

It then returns computer name Lindas-pc? with the ip address of 192.168.1.56

What can i do to make sure that the dhcp tables are correct? I've tried flushing dns, registering dns. No luck. A bit puzzling and would like an answer to help me sleep at night.

Searched around and couldnt find a similar article related to my issue.

Thanks!
0
zenki_fc
Asked:
zenki_fc
  • 2
1 Solution
 
iammorrisonCommented:
what are you using for internal DNS? Are either of these machines using a static address? try running arp -a in cmd prompt on a couple of machines and if you find that any of the machines list a different physical address for that IP, you have an IP conflict.
0
 
172pilotSteveCommented:
It's NOT DHCP that has the bad data - It's the reverse dns zone..  In your DNS, you have a "reverse" zone that it looks up the name of the machine by IP address..  You can go in there and safely delete any entries for your machine that are Windows - They will re-enter correct information after their next ipconfig /registerdns, or the next time they boot.

You could set your DHCP server to register the dynamic entries for the clients, rather than letting the clients do it, and you could turn on scavenging on that reverse DNS zone to make it auto-delete stale entries.

Two good things to read:


http://technet.microsoft.com/en-us/library/cc961414.aspx

http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.aspx
0
 
zenki_fcAuthor Commented:
Great!  Thanks guys I will take a look at botj suggestions.  If by chance another oossibke solution comes to mind please do post it here.
0
 
zenki_fcAuthor Commented:
Great reads.

That did the trick, stale entries in DNS. Made some adjustments and everything is good to go.
0

Featured Post

[Webinar] Kill tickets & tabs using PowerShell

Are you tired of cycling through the same browser tabs everyday to close the same repetitive tickets? In this webinar JumpCloud will show how you can leverage RESTful APIs to build your own PowerShell modules to kill tickets & tabs using the PowerShell command Invoke-RestMethod.

  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now