Bug #8054
closed
DHCP server accepts trailing dot in domain names, DNS resolver adds another and breaks
100%
Description
If you add a trailing dot on the domain name in the "domain name" and "domain search list", this is accepted. The DNS Resolver retrieves this domain name from a lease and adds a dot: the configuration file ends up with 2 trailing dots and unbound fails to parse its config file.
I believe adding the trailing dot in the domain name of the dhcp server is allowed but the DNS resolver should detect this trailing dot and not add a second one.
Updated by Jove Too almost 7 years ago
To be clear: this happened with a static lease.
Updated by Viktor Gurov over 4 years ago
This is true only for the DHCP static mapping "domain name" or the System / General / Domain, but not for the "domain search list".
Updated by Jim Pingle over 4 years ago
- Status changed from New to Pull Request Review
- Target version set to 2.5.0
Updated by Renato Botelho over 4 years ago
- Status changed from Pull Request Review to Feedback
- Assignee set to Renato Botelho
- % Done changed from 0 to 100
PR has been merged. Thanks!
Updated by Viktor Gurov over 4 years ago
- Status changed from Feedback to Resolved
works as expected on 2.5.0.a.20200403.1936
Updated by Jim Pingle over 4 years ago
- Status changed from Resolved to Feedback
- Target version changed from 2.5.0 to 2.4.5-p1
Updated by Jim Pingle over 4 years ago
- Status changed from Feedback to Resolved
The trailing dot is no longer allowed in input on the fields in question which would result in an error.