Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, April 1, 2020 9:45 AM
We have a strange issue where we have some printers which are a part of the same subnet and DHCP scope, and nonetheless some of the printers have a DNS record created, and other don't.
This seems to be unrelated to a specific model of a printer as well.
Any ideas/tips where to check to further understand why DNS records are not being created?
All replies (3)
Thursday, April 2, 2020 5:18 AM âś…Answered
Hi ,
Have you checked 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)." ?
In the DHCP management console, in the properties of the IPv4 in the DNS tab, be sure to have these settings:
- Enable DNS dynamic update DNS records only if requested by the DHCP clients
- Always dynamically update DNS records
- Discard A and PTR records when lease is deleted
- Dynamically update DNS records for DHCP clients that do not request updates
Configure DHCP Credentials and add the DHCP server to the Active Directory, Built-In DnsUpdateProxy security group.
If your zone is set to Secure Only and the printers do not have the ability to use Kerberos, it would prevent printers that are not AD aware from registering.
You might also choose non secure to do a test.
Please understand, I am not familiar with printers since our DNS forum mainly focus on windows OS. If the above steps still not work, could you please force a registerdns with Ipconfig or reboot the printer and then check if they could register DNS record?
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, April 7, 2020 2:20 AM
Hi ,
Just want to confirm the current situations.
Please feel free to let us know if you need further assistance.
Best Regards,
Candy
Please remember to mark the replies as an answers if they help.
If you have feedback for TechNet Subscriber Support, contact [email protected]
Tuesday, April 7, 2020 4:14 AM
We had already enabled that setting, but it worked for some printers and not for others. That's why we tried to figure out what's going on. In the end we realized that there is no reason to register each printer in DNS since anyhow users connect to the print sever to connect to the printers, so we will just disable all DNS registration entirely.
Thanks