System failed to register host (A or AAAA) resource records (RRs)

AudiAddict · Sep 9, 2014, 6:35 AM

My windows clients are showing error messages in their event viewers which I cannot seem to resolve:

The system failed to register host (A or AAAA) resource records (RRs) for network adapter
with settings:

Adapter Name : {577B4B52-6CE3-41BA-9DAC-A167E5FAEFDA}
Host Name : mypc
Primary Domain Suffix : home.local
DNS server list :
192.168.2.1
Sent update to server :
IP Address(es) :
192.168.2.100

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.

You can manually retry DNS registration of the network adapter and its settings by typing 'ipconfig /registerdns' at the command prompt. If problems still persist, contact your DNS server or network systems administrator.

These clients are using DHCP from Pfsense and dns lookup is working perfectly. In other words, I can browse the internet (external dns for my provider) and ping local clients by hostname without requiring home.local domain name.

This is my ipconfig from the client (192.168.2.1 is my pfsense IP, which is also DNS and DHCP server).

Connection-specific DNS Suffix . : home.local
Description . . . . . . . . . . . : ASUS USB-N53 802.11a/b/g/n Network Adapte

Physical Address. . . . . . . . . : 08-60-6E-CA-86-2E
DHCP Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Link-local IPv6 Address . . . . . : fe80::a090:2794:f4d2:bb78%6(Preferred)
IPv4 Address. . . . . . . . . . . : 192.168.2.100(Preferred)
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Lease Obtained. . . . . . . . . . : dinsdag 9 september 2014 08:10:17
Lease Expires . . . . . . . . . . : dinsdag 9 september 2014 10:10:17
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DHCPv6 IAID . . . . . . . . . . . : 67657838
DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-1B-9D-E1-84-08-60-6E-CA-86-2E

DNS Servers . . . . . . . . . . . : 192.168.2.1
NetBIOS over Tcpip. . . . . . . . : Enabled

I can resolve these error messages by disabling this registere dns windows feature in the network adapter settings, but I don't see why pfsense is not letting them register? I have " Enable registration of DHCP client names in DNS" enabled in the dhcp server setting. Anybody know how to resolve this?

meruem · Oct 26, 2017, 6:57 PM

Did you ever try this?

Below is language from pfsense domain config area

Do not use '.local' as the final part of the domain (TLD), The '.local' domain is widely used by mDNS (including Avahi and Apple OS X's Bonjour/Rendezvous/Airprint/Airplay), and some Windows systems and networked devices. These will not network correctly if the router uses '.local'. Alternatives such as '.local.lan' or '.mylocal' are safe.