On 17/03/2022 15:37, Patrick Bervoets via Pdns-users wrote:
ddns-domainname "psc-elsene.be";
ddns-rev-domainname "in-addr.arpa.";
zone psc-elsene.be { primary 127.0.0.53; key dhcpdupdate; }
zone 103.103.10.in-addr.arpa. { primary 127.0.0.53; key dhcpdupdate; }
...
set ddns-client-fqdn = "vpc2102.PSC-ELSENE.BE";
set ddns-rev-name = "12.103.103.10.in-addr.arpa.";
In the above places you have trailing dots on "arpa" but not on "be".
That might not be the issue, but it is worth checking.
domainmetadata
|id |domain_id|kind |content |
|---|---------|--------------------|---------------|
|5 |10 |TSIG-ALLOW-DNSUPDATE|dhcpdupdate |
|7 |15 |TSIG-ALLOW-DNSUPDATE|dhcpdupdate |
|9 |10 |ALLOW-DNSUPDATE-FROM|127.0.0.0/8 |
|10 |15 |ALLOW-DNSUPDATE-FROM|127.0.0.1 |
|13 |10 |ALLOW-DNSUPDATE-FROM|10.103.103.0/24|
These aren't consistent, but since zone 15 is working, zone 10 should be
OK. In any case, you can use tcpdump to check what is the source address
of the DDNS update packets (and should also decode their contents)
tcpdump -ilo -s0 -nnv port 53
_______________________________________________
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
https://mailman.powerdns.com/mailman/listinfo/pdns-users
