Bug 15907 - nslookup fails with IPv6 name server in resolv.conf the has a comment
Summary: nslookup fails with IPv6 name server in resolv.conf the has a comment
Status: NEW
Alias: None
Product: Busybox
Classification: Unclassified
Component: Networking (show other bugs)
Version: 1.35.x
Hardware: All Linux
: P5 normal
Target Milestone: ---
Assignee: unassigned
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-01-04 20:28 UTC by Oscar
Modified: 2024-01-04 20:28 UTC (History)
1 user (show)

See Also:
Host:
Target:
Build:

Attachments
packet capture. 3 frames. 1 & 2 are what should be, 3 is nslookup (880 bytes, application/octet-stream)
2024-01-04 20:28 UTC, Oscar 		Details
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Oscar 2024-01-04 20:28:33 UTC 
Created attachment 9691 [details]
packet capture.  3 frames. 1 & 2 are what should be, 3 is nslookup

the nslookup client seems to not parse the resolv.conf entry correctly when the name server entry has a # comment in the string 
for example: nameserver 2001:1868:209:fff7:2185:39d8:332c:3eed # vlan1

When you try to perform nslookup google.com  for example,  the DNS lookup frame will contain a Queries entry for the name server instead of the string "google.com"

2001:1868:209:fff7:2185:39d8:332c:3eed # vlan1.scar.scarnet.com: type AAAA, class IN