Check /etc/hosts first

[NotBugger]

The default (and IMHO unexpected) behavior of AnyEvent::Socket is to resolve hostnames through /etc/hosts only if the DNS lookup fails. If you think of /etc/hosts as a user-defined DNS cache, it makes sense that AnyEvent::CacheDNS should override the default behavior and first check /etc/hosts, then the cache, then a DNS lookup.

Relevant thread: http://www.mail-archive.com/anyevent@lists.schmorp.de/msg00040.html

[potyl]

I agree that AnyEvent::Socket's resolution strategy is really annoying. The module behaves completely differently from all the programs that use networking because they all look into /etc/hosts. This is really nasty.

I don't think that fixing this in my module is the right thing. My module is just a DNS cache. Someone should write a real linux/unix resolver that would behave as all the other networking tools behave.

[dex4er]

Please check https://github.com/dex4er/perl-AnyEvent-DNS-EtcHosts

It modifies AnyEvent::Socket behavior and should be complementary to AnyEvent::DNS::Cache.