means I can't redefine the _defaults function, as it gets re-defined each time AnyEvent::DNS calls it.

Can you explain that? From what I see in AnyEvent::DNS, it is only using Net::DNS::Resolve here:

   require Net::DNS::Resolver;
   my $r = Net::DNS::Resolver->new;

   $r->nameservers
      or die;

   for my $s ($r->nameservers) {
      if (my $ipn = AnyEvent::Socket::parse_address ($s)) {
         push @{ $self->{server} }, $ipn;
      }
   }
   $self->{search} = [$r->searchlist];
[download]

and $r goes out of scope after that. There should not be any problem monkey-patching functions inside of Net::DNS::Resolver, or even AnyEvent::DNS. But you don't need to monkey-patch it if you know your resolvers, because:

AnyEvent::DNS::resolver

This function creates and returns a resolver that is ready to use and
should mimic the default resolver for your system as good as possible.
It is used by AnyEvent itself as well.

It only ever creates one resolver and returns this one on subsequent
calls
- see $AnyEvent::DNS::RESOLVER, below, for details.

Unless you have special needs, prefer this function over creating your
own resolver object.

The resolver is created with the following parameters:

 untaint          enabled
 max_outstanding  $ENV{PERL_ANYEVENT_MAX_OUTSTANDING_DNS} (default 10)

os_config will be used for OS-specific configuration, unless
$ENV{PERL_ANYEVENT_RESOLV_CONF} is specified, in which case that file
gets parsed.

$AnyEvent::DNS::RESOLVER

This variable stores the default resolver returned by
AnyEvent::DNS::resolver, or undef when the default resolver hasn't
been instantiated yet.

One can provide a custom resolver (e.g. one with caching
functionality) by storing it in this variable, causing all
subsequent resolves done via AnyEvent::DNS::resolver to be done
via the custom one.
[download]

So it appears you have lots of options to customize this.

Meanwhile, AnyEvent::DNS doesn't use Net::DNS::Resolver for DNS lookups, it only uses it to dig the nameserver list and search path out of the Windows registry. Are you sure that your program is hanging in the place that you think it's hanging?

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.