Bug #11224
closed
dhcpd.conf creation - zone declarations
Added by A S almost 4 years ago.
Updated almost 4 years ago.
Affected Version:
2.4.5-p1
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
- 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)
- Status changed from Pull Request Review to Feedback
- Assignee set to Viktor Gurov
PR has been merged. Thanks!
- % Done changed from 0 to 100
- 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
Also available in: Atom
PDF