[PATCH]networking: Allow dot at the end of the domain name in dhcp response

Balaji Punnuru balaji.punnuru at gmail.com
Wed Feb 3 20:40:15 UTC 2016


When a dhcp server responds with a domain name that ends with a ".",
domain name validation is failing which leads to populating domain bad in
resolv.conf

Domain name ending with . is a valid syntax according RFC-1034.

The Patch fixes the domain name validation which ends with "."
The test results are as follows:

1. if DNS server returns with domain name "foo.test.com." , resolv.conf
gets populated with "domain foo.test.com."

2. if DNS server returns with domain name "foo.test.com" , resolv.conf gets
populated with "domain foo.test.com"

Without this Patch:
1. if DNS server returns with domain name "foo.test.com." , resolv.conf
gets populated with "domain bad <http://foo.test.com>"

2. if DNS server returns with domain name "foo.test.com" , resolv.conf gets
populated with "domain foo.test.com"
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20160203/473c4b03/attachment-0001.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: 0001-networking-Fixed-issue-with-domain-name-validation-i.patch
Type: text/x-patch
Size: 1798 bytes
Desc: not available
URL: <http://lists.busybox.net/pipermail/busybox/attachments/20160203/473c4b03/attachment-0001.bin>


More information about the busybox mailing list