Bug #11224
closeddhcpd.conf creation - zone declarations
100%
Description
ARPA zones lack a trailing period. Currently
zone 16.172.in-addr.arpa {
Should be:
zone 16.172.in-addr.arpa. {
ARPA DDNS updates do not appear to be functioning as a result of the trailing period not being present.
services.inc : line 1282
Updated by Viktor Gurov over 3 years ago
Note that the zone declarations have to correspond to authority records in your name server - in the above example, there must be an SOA record for "example.org." and for "17.10.10.in-addr.arpa.". For example, if there were a subdomain "foo.example.org" with no separate SOA, you could not write a zone declaration for "foo.example.org." Also keep in mind that zone names in your DHCP configuration should end in a "."; this is the preferred syntax. If you do not end your zone name in a ".", the DHCP server will figure it out. Also note that in the DHCP configuration, zone names are not encapsulated in quotes where there are in the DNS configuration.
fix:
https://gitlab.netgate.com/pfSense/pfSense/-/merge_requests/90
Updated by Jim Pingle over 3 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
If you do not end your zone name in a ".", the DHCP server will figure it out.
The quoted text seems to suggest it's optional, but recommended. Are we certain adding the trailing '.' fixes the problem stated in the description?
It's good to do either way, but if there is another issue separate from this, it would need its own Redmine entry (After diagnosing it on the forum and so on)
Updated by Renato Botelho over 3 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
Updated by Viktor Gurov over 3 years ago
- % Done changed from 0 to 100
Applied in changeset e733f5b2d0d35b68746efe8035af1688dfdd0103.
Updated by Viktor Gurov over 3 years ago
- Status changed from Feedback to Resolved
/var/dhcpd/etc/dhcpd.conf:
zone topdhcp.int. { primary 192.168.88.89; secondary 192.168.88.81; key "topkey1"; } zone 88.168.192.in-addr.arpa. { primary 192.168.88.89; secondary 192.168.88.81; key "topkey1"; }
works as expected
2.5.0.a.20210201.2350