DHCP server doesn't update the DNS except if you tell it to for clients that don't support that functionality.
The client updates the DNS, but you probably have your DNS set for secured updates only, and as such your workgroup members are unable to establish the necessary secured connection to the DNS server to effect the update. You could set a reservation in your DHCP server, and then manually create the corresponding A record. Cheers Ken -----Original Message----- From: N Parr [mailto:npar...@mortonind.com] Sent: Thursday, 20 January 2011 11:25 PM To: NT System Admin Issues Subject: Resolving host names of non-domain members I have a few workstations that can't be domain members, mostly because the are running controls for equipment and are locked down by the vendor. I've been able to rename their workgroup to match our domain so I don't have a bunch of stray workgroups in my network neighborhood. Anyway, some of my clients/servers that need to get to shares for backups/etc can't resolve them by host name. They are all set to DHCP and show up in my Leases as hostname. instead of hostname.domain.local. And the ones that are like that don't show up in DNS. Any idea why I can resolve them from some clients and not others? I'm assuming it has something to do with the DHCP server not properly updating DNS because they aren't a domain member. Only way I can figure around it is to set static IP's and either connect by IP or set an A Record. Thanks Niles ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to listmana...@lyris.sunbeltsoftware.com with the body: unsubscribe ntsysadmin
