Hello,

I'm using a 2008R2 Domain controller for DHCP and DNS. The DNS zone is AD integrated. Printers that are obtaining IP addresses through DHCP are not getting their names registered in DNS. XP and Win7 workstations are.

DHCP has only one zone. Its options point to the DC's IP for DNS and have the correct FQDN for their suffix.

DHCP DNS tab has Enable DNS dynamic... checked and Always dynamically update DNS A and PTR records selected. Discar A and PTR... is checked as is Dynamically update DNS A and PTR records for DHCP clients that do not request...

DNS has Dynamic Updates set to Nonsecure and Secure.

Printers are obtaining addresses when their restarted but not being registered in DNS. Their names do not exist in DNS but show up in DHCP.

No events are being logged in the DNS log on the server.

Printers can be pinged by their NETBIOS name but not FQDN.

Help, please.

 

check your printers ip address configuration,

and make sure you have DNS server setup on them 

Hi drossarndt,

In DHCP scope properties, DNS tab, you'll also need to check the box for "Dynamically update DNS A and PTR records for DHCP clients that do not request updates (for example, clients running Windows NT 4.0)."

If your zone is set to Secure Only, it would prevent printers that are not AD aware from registering (Secure Only uses Kerberos to authenticate), as well as if the DNS suffix for the zone can not be set (many printes are this way).

I would also suggest to enable Scavenging, and configure DHCP to own all records it registers so it properly updates any IP changes (whether for the printers, workstations, laptops, etc). This way DHCP will control and register everything. Here's more info in my blog.

DHCP, Dynamic DNS Updates, Scavenging, static entries & timestamps, and the DnsProxyUpdate Group (How to remove duplicate DNS host records)
Published by acefekay on Aug 20, 2009 at 10:36 AM 
http://msmvps.com/blogs/acefekay/archive/2009/08/20/dhcp-dynamic-dns-updates-scavenging-static-entries-amp-timestamps-and-the-dnsproxyupdate-group.aspx

Regards,
Ace

Hi,

 

If there is any update on this issue, please feel free to let us know.

 

We are looking forward to your reply.

So, we are running Win2K8 R2 SP1 and using DHCP for printers and the records are not updating DNS.  We are AD Integrated Zones and running Secure only.  Do I need to create static entries from my printers or is there a change I need to make so they will register?  The checkbos mentioned above is checked on the DHCP servers.  Would creating a Workstaion Object in AD with the printer name solve the problem?

Dave

Can you specify which check box you have checked?

Note: If using DHCP with credentials, and Option 081 tab in DHCP properties (that's the DNS tab), then DHCP will register for all clients. Otherwise, if set to Secure Only, then that means the DHCP client must be authorized before it can register. Matter of fact it uses Kerberos. If the printers do not have the ability to use Kerberos, then you either havee to manually create static entries, or configure DHCP to use credentials or add the DHCP server account to the DnsUpdateProxy group.

This is a Windows 2000 DHCP server so using Credentials is not an option available.  The check box is the "Enable updates for DNS clients that do not support Dynamic updates".

I am thinking the best solution might be to migrate the printers from the older Win2K print server to a new Win2k8 R2 SP1 cluster via a Win2K3 server.

Dave

I don't have a Windows 2000 installation to double check if it was available or not. I don't remember. And besides selecting, "Enable updates for DNS clients that do not support Dynamic updates," you would also select to Always dynamically uipdate DNS A and PTR records" (disregard the name protection selection):

Currently I have a similar problem. After turning on the printer it obtains an IP address from the DHCP server.The DHCP server registers the printer in the DNS. However, after the renewal of the lease, the DHCP server deletes the DNS entry. The result is that the printer name can not be resolved.

Current configuration:

• Domaincontroller is DNS and DHCP server
• "Enable DNS dynamic updates according to the settings below" is enabled
• "Allways dynamically update DNS A and PTR records" is enabled
• "Discard A and PTR records when lease is deleted" is enabled
• "Dynamically update DNS A and PTR records for DHCP client that do not request updates ..." is enabled

Any ideas?

Thanks for your support.

                

Same problem here...

We mainly have DNS dynamic update problems with HP printers...

Everything suggested above is being implemented.

I recently had a similar problem with an old Dell 5100cn printer after we made some network IP scheme changes.  It received DHCP info, but it's name and address didn't get dynamically registered with DNS.  The DHCP server options for DNS registration that are suggested in another reply in this thread were grayed out on our DHCP server.  But, the note about some old printers not having the option to enter the domain name in their TCP/IP configuration got me thinking....

I browsed to the webpage of the printer itself (by IP Address, of course) and in the basic network settings, I changed the printer name from "printername" to "printername.our_domain.name" - for example "printer1.contoso.com" instead of just "printer1".  Then, I deleted the DHCP record for that printer and rebooted the printer.  As soon as it came back online it had an IP address and had a record in DNS.  That solved it for me with this particular printer model.  Other (newer) printer models we have are working fine with DNS registrations without needing this workaround.

• Edited by Jeff A1 5 hours 31 minutes ago