never-ending loop when trying to resolve a non-ip nameserver in /etc/resolv.conf

[javierwilson]

When dealing with an invalid entry in /etc/resolv.conf (in my case an address ending in comma 8.8.8.8,) in config.rb when parsing /etc/resolv.conf:

1. IPv4.create(n) fails, then
2. IPv6.create(n) fails, then
3. Use Dnsruby to resolve the servers First, try the default resolvers. This of course tries to parse /etc/resolv.conf, going back to 1. creating the loop.

[alexdalitz]

Oops! Thanks for letting me know about this - I’ll make a fix over the next few days when I have some spare time. Thanks!

…

On 10 Nov 2021, at 11:09, javier wilson ***@***.***> wrote: When dealing with an invalid entry in /etc/resolv.conf (in my case an address ending in comma 127.0.0.1,) in config.rb when parsing /etc/resolv.conf: IPv4.create(n) fails, then IPv6.create(n) fails, then Use Dnsruby to resolve the servers First, try the default resolvers. This of course tries to parse /etc/resolv.conf, going back to 1. creating the loop. — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#179>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AB2WFWRGAZDT4QDF2QPS533ULJHHRANCNFSM5HXTPQ4A>. Triage notifications on the go with GitHub Mobile for iOS <https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675> or Android <https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub>.

[alexdalitz]

Just to say sorry I haven't had a chance to look at this yet. I don't think this is a common problem, so it's quite low priority for me. If it's causing you pain, please let me know.