DHCP DDNS not updating reverse zone ipv6

vgauthier

Hi,

Most of my clients are dual-stack IPv4/IPv6. I have bind installed as the DNS resolver. The dhcp servers (both IPv4 and IPv6) are configured to add reverse dynamic DNS records. However, the reverse IPv4 zone is updated correctly, but the reverse IPv6 zone is not, and the DNS server didn't trigger any warming in the logs regarding a possible misconfiguration.

Any ideas where the problem might be coming from?

best
Vincent

Gertjan

@vgauthier said in DHCP DDNS not updating reverse zone ipv6:

However, the reverse IPv4 zone is updated correctly, but the reverse IPv6 zone is not, and the DNS server didn't trigger any warming in the logs regarding a possible misconfiguration.

The updates happen on the Master DNS server of the zone.
Typically that is not 'bind on pfSEnse' but bind running somewhere on the internet, on you master (zone) domain name server.

I see these :

11-Jul-2023 07:12:35.370 update-security: client @0x7ff2741f96e0 82.127.26.108#53445/key update: signer "secretkey" approved
11-Jul-2023 07:12:35.370 update: client @0x7ff2741f96e0 82.127.26.108#53445/key update: updating zone 'bhf.net/IN': deleting rrset at 'DROITE.bhf.net' TXT
11-Jul-2023 07:12:35.370 update: client @0x7ff2741f96e0 82.127.26.108#53445/key update: updating zone 'bhf.net/IN': adding an RR at 'DROITE.bhf.net' TXT "022e96e6eb8ee0bc2cb98b30c15a77e7ed"
11-Jul-2023 07:12:35.370 update: client @0x7ff2741f96e0 82.127.26.108#53445/key update: updating zone 'bhf.net/IN': deleting rrset at 'DROITE.bhf.net' AAAA
11-Jul-2023 07:12:35.370 update: client @0x7ff2741f96e0 82.127.26.108#53445/key update: updating zone 'bhf.net/IN': adding an RR at 'DROITE.bhf.net' AAAA 2a01:dead:907:beef::a0
11-Jul-2023 07:12:35.392 update-security: client @0x7ff2741f96e0 82.127.26.108#53445/key update: signer "secretkey" approved

with :

vgauthier

Hello @Gertjan, thanks for your answers.

I finally solved my problem, my issue was that the reverse DNS zone needs to be exactly in the same range as the one defined in the DHCP server.

In my previous configuration:
My Bind DNS reverse a zone for all my subnets like: 2001:xxxx:xxxx:xxxxx/60
Each interface in my DHCP server configuration were define a subnet like: 2001:xxxx:xxxx:xxxxx/64

Now I have defined a reverse zone of each of my /64 subnets in my DNS Bind server and this solves my problem.