Skip Menu |
 

This queue is for tickets about the AnyEvent CPAN distribution.

Report information
The Basics
Id: 62003
Status: resolved
Priority: 0/
Queue: AnyEvent

People
Owner: Nobody in particular
Requestors: isaacson [...] cpan.org
Cc:
AdminCc:

Bug Information
Severity: Critical
Broken in: 5.271
Fixed in: (no value)



Subject: AnyEvent::DNS parses nameserver lines too strictly
MIME-Version: 1.0
Content-Type: text/plain; charset="UTF-8"
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 907
Download (untitled) / with headers
text/plain 907b
AnyEvent::DNS's parsing of nameserver lines in /etc/resolv.conf is stricter than glibc's. In my environment the generation process adds the hostname as a "comment": nameserver 1.2.3.4 ; foo I'm not sure if this is documented anywhere as supported, but it works because glibc (in res_init) will take everything after the "nameserver " and pass it to inet_aton; inet_aton happily ignores anything after the address, so inet_aton("1.2.3.4 ; foo") returns the properly packed address. The specific workaround for this is probably to relax this regex in AnyEvent/DNS.pm: old: if (/^\s*nameserver\s+(\S+)\s*$/i) { new: if (/^\s*nameserver\s+(\S+)/i) { Also, glibc recognizes ";" as a valid comment character, in addition to "#", so another option would be to do the same: old: s/#.*$//; # not quite legal, but many people insist new: s/[#;].*$//; # not quite legal, but many people insist
MIME-Version: 1.0
X-Mailer: MIME-tools 5.427 (Entity 5.427)
Content-Disposition: inline
Content-Type: text/plain; charset="UTF-8"
Message-ID: <rt-3.8.HEAD-29961-1286653805-1070.62003-0-0 [...] rt.cpan.org>
Content-Transfer-Encoding: binary
X-RT-Original-Encoding: utf-8
Content-Length: 107
Download (untitled) / with headers
text/plain 107b
The owner indicated by e-mail that this will be resolved in the next release. Closing ticket upon request.


This service is sponsored and maintained by Best Practical Solutions and runs on Perl.org infrastructure.

Please report any issues with rt.cpan.org to rt-cpan-admin@bestpractical.com.