There has been posted a similar issue here:
https://social.technet.microsoft.com/Forums/office/en-US/bcf9dff8-dbc2-48de-85ad-0101ae3159cd/dhcp-server-log-reporting-dns-update-failed?forum=winserverNIS
We had a printer in zoneA (172.16.240.0/24) on the evening of 23th of February. You can see the device being renamed from NPI54B55D to PRZHS002. The printer has been moved to zoneB (172.16.248.0/24) the next morning. It was plugged in at 07:30 o'clock.
Problem now is, the A entry on the DNS server seems to hop between the two IP's 172.16.240.110 and 172.16.248.239. Some clients could resolve the printer, and some couldn't. Just depended on when they tried to resolve the record.
Log from the day the printer was setup in zoneA
18,02/23/16,10:18:47,Expired,172.16.240.110,,,,0,6,,,,,,,,,0
30,02/23/16,13:18:50,DNS Update Request,172.16.240.110,NBINF013.merbag.local,,,0,6,,,,,,,,,0
31,02/23/16,14:18:50,DNS Update Failed,172.16.240.110,NBINF013.merbag.local,,,0,6,,,,,,,,,2
30,02/23/16,14:18:50,DNS Update Request,172.16.240.110,NBINF013.merbag.local,,,0,6,,,,,,,,,0
17,02/23/16,14:18:50,DNS record not deleted,172.16.240.110,,,,0,6,,,,,,,,,0
30,02/23/16,16:23:30,DNS Update Request,172.16.240.110,NPI54B55D.merbag.local,,,0,6,,,,,,,,,0
10,02/23/16,16:23:30,Assign,172.16.240.110,NPI54B55D.merbag.local,FC3FDB54B55D,,1440707597,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x2B4D66673D48503B5479703D556E6B6E6F776E3B4D6F643D556E6B6E6F776E3B5365723D556E6B6E6F776E3B,+Mfg=HP;Typ=Unknown;Mod=Unknown;Ser=Unknown;,,0
30,02/23/16,16:23:30,DNS Update Request,172.16.240.110,NPI54B55D.merbag.local,,,0,6,,,,,,,,,0
11,02/23/16,16:23:30,Renew,172.16.240.110,NPI54B55D.merbag.local,FC3FDB54B55D,,1440707597,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x2B4D66673D48503B5479703D556E6B6E6F776E3B4D6F643D556E6B6E6F776E3B5365723D556E6B6E6F776E3B,+Mfg=HP;Typ=Unknown;Mod=Unknown;Ser=Unknown;,,0
31,02/23/16,16:23:30,DNS Update Failed,172.16.240.110,NPI54B55D.merbag.local,,,0,6,,,,,,,,,9005
30,02/23/16,16:59:20,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
11,02/23/16,16:59:20,Renew,172.16.240.110,PRZHS002.merbag.local,FC3FDB54B55D,,3889591309,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x424D66673D48503B5479703D4D46503B4D6F643D485020436F6C6F72204C617365724A657420466C6F77204D4650204D3638303B5365723D4A5044564A32473039463B,BMfg=HP;Typ=MFP;Mod=HP
Color LaserJet Flow MFP M680;Ser=JPDVJ2G09F;,,0
31,02/23/16,16:59:20,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,2
30,02/23/16,16:59:20,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
11,02/23/16,16:59:20,Renew,172.16.240.110,PRZHS002.merbag.local,FC3FDB54B55D,,3889591309,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x424D66673D48503B5479703D4D46503B4D6F643D485020436F6C6F72204C617365724A657420466C6F77204D4650204D3638303B5365723D4A5044564A32473039463B,BMfg=HP;Typ=MFP;Mod=HP
Color LaserJet Flow MFP M680;Ser=JPDVJ2G09F;,,0
32,02/23/16,16:59:20,DNS Update Successful,172.16.240.110,NPI54B55D.merbag.local,,,0,6,,,,,,,,,0
31,02/23/16,16:59:20,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/23/16,17:18:52,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/23/16,17:18:54,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
Log from the day the printer was delivered to zoneB
30,02/24/16,00:00:34,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,00:00:35,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,00:18:57,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,00:18:58,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,01:18:58,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,01:18:59,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,02:18:58,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,02:19:00,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,03:18:59,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,03:19:00,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,04:19:00,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,04:19:01,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,05:19:00,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,05:19:02,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,06:19:01,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,06:19:02,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,07:19:02,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,07:19:04,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,07:30:19,DNS Update Request,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
10,02/24/16,07:30:19,Assign,172.16.248.239,PRZHS002.merbag.local,FC3FDB54B55D,,588674061,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x424D66673D48503B5479703D4D46503B4D6F643D485020436F6C6F72204C617365724A657420466C6F77204D4650204D3638303B5365723D4A5044564A32473039463B,BMfg=HP;Typ=MFP;Mod=HP
Color LaserJet Flow MFP M680;Ser=JPDVJ2G09F;,,0
32,02/24/16,07:30:19,DNS Update Successful,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
30,02/24/16,08:19:02,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,08:19:05,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,08:26:09,DNS Update Request,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
11,02/24/16,08:26:09,Renew,172.16.248.239,PRZHS002.merbag.local,FC3FDB54B55D,,588674061,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x424D66673D48503B5479703D4D46503B4D6F643D485020436F6C6F72204C617365724A657420466C6F77204D4650204D3638303B5365723D4A5044564A32473039463B,BMfg=HP;Typ=MFP;Mod=HP
Color LaserJet Flow MFP M680;Ser=JPDVJ2G09F;,,0
32,02/24/16,08:26:09,DNS Update Successful,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
30,02/24/16,09:19:03,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,09:19:05,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,10:19:04,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,10:19:06,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,10:21:26,DNS Update Request,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
11,02/24/16,10:21:26,Renew,172.16.248.239,PRZHS002.merbag.local,FC3FDB54B55D,,588674061,0,,,,0x4865776C6574742D5061636B617264204A6574446972656374,Hewlett-Packard JetDirect,0x424D66673D48503B5479703D4D46503B4D6F643D485020436F6C6F72204C617365724A657420466C6F77204D4650204D3638303B5365723D4A5044564A32473039463B,BMfg=HP;Typ=MFP;Mod=HP
Color LaserJet Flow MFP M680;Ser=JPDVJ2G09F;,,0
32,02/24/16,10:21:26,DNS Update Successful,172.16.248.239,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
30,02/24/16,11:19:04,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,11:19:06,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,12:19:05,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,12:19:07,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
30,02/24/16,13:19:06,DNS Update Request,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,0
31,02/24/16,13:19:08,DNS Update Failed,172.16.240.110,PRZHS002.merbag.local,,,0,6,,,,,,,,,9005
When we had a look into it, the DNS server had an A record resolving PRZHS002 to 172.16.240.110 and a pointer record in the reverse lookup zone, resolving 172.16.248.239 to PRZHS002.merbag.local
My question now is: why is the DHCP server still trying to update the old record stored in zoneA if the printer has been moved to zoneB already? The DHCP Server seems to update every hour 19min.
And the bonus question of course is: Why are so many DNS updates failing on the DHCP Server? We do see lots of them in the DHCP log, not only for this device.
Some information about our environment:
We don't have debug logging enabled on the DNS server. But we can see DNS related records in the security log. But everytime we see a "DNS Update Failed" message on the DHCP server, there is nothing related to that in the DNS log. It is like the
request from the DHCP server cant even reach the DNS server.
DHCP lease time ist 4 days. All servers are 2012 R2. We have increased the value of DynamicDNSQueueLength already.
We use an AD service account to add entries to DNS. This account has been added to the DNSUpdateProxy group. Only secure updates in DNS are allowed.
DHCP is setup to always dynamically update DNS records. It discards A and PTR records when leases are deleted. There is no problem with the AD service account, because only some updates do fail.
The DHCP server has no failover or cluster or anything. It works on its own and is the owner of all entries in DNS. Best practice analyzer on DHCP server only complains about a zone we have disabled because it is for testing purposes.