Computers with multiple DNS entries = Problem

Follow

Jared

• October 07, 2013 17:56

I have some laptops that are connecting up to the network both through their wireless connection and through their wired connection when docked.  This results in two entries in DNS for the same computer.  I will very frequently see the wireless iP (10.x.5.x) in inventory when they are docked (should be a 10.x.1.x IP).  This causes problems with deployments all the time.

I try bouncing the DNS Client service on the inventory/deploy server and that seems to help a little, but it always seems to go right back to the same problem.  In order to get deploy to work right with my laptop, I have to go and actually delete the records out of DNS so that there is only one per endpoint.

Is there a solution to this (either on your end or mine) that we can work on implementing?

4

• 

  SelfMan

  • October 08, 2013 01:29

  I have the same problem sometimes and I already reported this a long time ago.

  0

  Comment actions Permalink
• 

  Marco Hofmann

  • October 22, 2013 22:29

  Same problem here with servers, that answer through different names due to DNS CNAME entries. Will there be a fix?

  0

  Comment actions Permalink
• 

  Kevin Jackson

  • April 01, 2014 10:53

  i get the same too with a good proportion of the devices on my network.

  Pretty frustrating really.

  0

  Comment actions Permalink
• 

  Jeff Longley

  • January 08, 2015 15:00

  That's more a DNS issue than a PDQ issue - have a read of this:
  
  http://blogs.technet.com/b/askpfe/archive/2011/06/03/how-dns-scavenging-and-the-dhcp-lease-duration-relate.aspx

   

  0

  Comment actions Permalink
• 

  Marco Hofmann

  • January 08, 2015 16:53

  Yes, that is one poissbile solution, I know this and similar articles.

  But there is also the case, that a server simply has more than one name. 

  0

  Comment actions Permalink
• 

  Jeff Longley

  • January 09, 2015 08:23

  You could change the collection to ignore your wireless IP range; However, when the server deploys, it's going to use DNS to locate the machine, NOT the record it has in the database.

  0

  Comment actions Permalink
• 

  Steve Young

  • October 10, 2019 18:18

  I know this is an old post - but this is exactly my issue.  I am trying out Inventory and it works great, except for my laptops that connect both wirelessly and wired.  The scans fail when DNS on the server has not updated to the 'live' ip address.  I hope there is an answer since I don't see many other posts about this.

  Thanks.

  0

  Comment actions Permalink

Please sign in to leave a comment.