Local system fails to register address with DNS server

[vrapp]

In the event log of Windows 10:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:
Adapter Name : {717B8CC1-EAC4-48C6-AFC0-4007E873E62C}
Host Name : <MY COMPUTER NAME>
Primary Domain Suffix : myhome.com
DNS server list :
192.168.1.1
Sent update to server : <?>
IP Address(es) :
192.168.1.205

The reason the system could not register these RRs was because the DNS server failed the update request. The most likely cause of this is that the authoritative DNS server required to process this update request has a lock in place on the zone, probably because a zone transfer is in progress.

The network card is configured with all default settings, obtaining the address and Primary Domain Suffix from DHCP on the router, and has the option "register this connection's address in DNS" enabled, which is the default setting. Since the DNS server at 192.168.1.1 is the router, does it mean that something is not working as expected?

 

[bennor]

What router are you using, what firmware is it running?
Does the router system log indicate any errors?

 

[RMerlin]

DNS registration is something related to Windows domain controlers running an actual DNS server, not to simple routers. These routers don't run a DNS server, just a caching resolver (dnsmasq).

 

[ColinTaylor]

In the event log of Windows 10:



The network card is configured with all default settings, obtaining the address and Primary Domain Suffix from DHCP on the router, and has the option "register this connection's address in DNS" enabled, which is the default setting. Since the DNS server at 192.168.1.1 is the router, does it mean that something is not working as expected?

You see this error because you have specified a Primary DNS Suffix for your PC's computer name. You should leave this blank so that your PC will obtain the DNS suffix from the router using DHCP option 15 instead of trying to use option 81.

 

[vrapp]

DNS registration is something related to Windows domain controlers running an actual DNS server, not to simple routers. These routers don't run a DNS server, just a caching resolver (dnsmasq).

Curious... If it does not run DNS server, how does it resolve local names?

C:\Users\UserA>nslookup
Default Server: RT-AC68P-40D0.myhome.com
Address: 192.168.1.1

> composhae
Server: RT-AC68P-40D0.myhome.com
Address: 192.168.1.1

Name: composhae.myhome.com
Address: 192.168.1.237

> printer
Server: RT-AC68P-40D0.myhome.com
Address: 192.168.1.1

Name: printer.myhome.com
Address: 192.168.1.42

What router are you using, what firmware is it running

RT-AC68P, 386.14

You see this error because you have specified a Primary DNS Suffix for your PC's computer name. You should leave this blank so that your PC will obtain the DNS suffix from the router using DHCP option 15 instead of trying to use option 81.

Thanks, that solved it!

 

[RMerlin]

Curious... If it does not run DNS server, how does it resolve local names?

As I said, dnsmasq is a caching resolver. It merely reads entries from the local hosts file and from its own internal lease list. That`s just a fraction of what an actual DNS server like bind or unbound do.