As a Node.js maintainer I also ran into this problem. Our solution was
to ignore these fec0:: servers entirely
(https://github.com/piscisaureus/cares/commit/f6cdd7d404d44eb2d6e8866e85ae65
1b89fc769e),
and we've never had any complaints about it. I
think pycares did the same. Placing these
I noticed that acountry.c and ahost.c, two of our demo examples, use
ares_inet_ntop() and ares_inet_pton().
None of these functions are part of our documented public API and I would
like to clean this up.
Anyone who feels strongly enough about this subject to speak up for either
making
We have a customer that is complaining that (somehow) c-ares is getting
configuration information for DNS servers from disabled interfaces. I should
specify the customer is on Windows.
I don't really see how this is possible as the GetAdaptersAddresses and
associated functions are not
Hi all,
Windows tends to report a couple of IPv6 DNS servers that don't actually
exist; they all start with `fec0:0:0:`. It takes a while for c-ares to
figure out that these DNS servers are not responding, so IPv6 lookups end up
taking a long time.
This patch fixes that. We've been
-Oorspronkelijk bericht-
Van: c-ares-boun...@cool.haxx.se [mailto:c-ares-boun...@cool.haxx.se]
Namens Poul Thomas Lomholt
Verzonden: Saturday, February 04, 2012 7:31 AM
Aan: c-ares@cool.haxx.se
Onderwerp: [Patch] Buffer overrun in get_iphlpapi_dns_info() (ares_init.c)
on Windows
On Thu, Oct 20, 2011 at 03:35:33PM -0700, Bert Belder wrote:
Windows always reports some hard-coded IPv6 DNS servers that don't
actually exist. I see three of them, they're all prefixed with
fec0:0:0:. This often doesn't hurt, but it does hurt when these
rogue nameservers end up
Hey,
Windows always reports some hard-coded IPv6 DNS servers that don't actually
exist. I see three of them, they're all prefixed with fec0:0:0:. This
often doesn't hurt, but it does hurt when these rogue nameservers end up at
the top of the server list, because c-ares first tries all of them
