This is the mail archive of the
libc-help@sourceware.org
mailing list for the glibc project.
Re: Question about getaddrinfo taking 20 seconds
- From: Yann Droneaud <yann at droneaud dot fr>
- To: Eugen Dedu <Eugen dot Dedu at pu-pm dot univ-fcomte dot fr>
- Cc: libc-help at sourceware dot org
- Date: Mon, 16 Jul 2012 20:07:19 +0200
- Subject: Re: Question about getaddrinfo taking 20 seconds
- References: <5003F292.1090909@pu-pm.univ-fcomte.fr>
Hi,
Le lundi 16 juillet 2012 Ã 12:53 +0200, Eugen Dedu a Ãcrit :
>
> I have a dns-related question. The following program shows here 20
> seconds, which means that getaddrinfo with AI_CANONNAME takes 20
> seconds. Is it normal?
[...]
> const char *name = "stun.ekiga.net";
[...]
Request with dig "stun.ekiga.net" A, returns:
stun.ekiga.net. 2385 IN CNAME stun.voipbuster.com.
stun.voipbuster.com. 516 IN A 77.72.169.158
stun.voipbuster.com. 516 IN A 77.72.169.156
stun.voipbuster.com. 516 IN A 77.72.169.154
stun.voipbuster.com. 516 IN A 77.72.169.152
When trying a retrieve reverse PTR records for
77.72.169.158, 77.72.169.156, 77.72.169.154, 77.72.169.152
with dig -x, I'm getting either "SERVFAIL" or timeout errors.
So, the latencies are probably related to the reverse PTR which seems to
be misconfigured.
In fact, according to some DNS server/resolver log, the exact error is:
Jul 16 20:01:45 quoi named[6493]: error (unexpected RCODE REFUSED)
resolving '152.169.72.77.in-addr.arpa/PTR/IN': 77.72.174.217#53
Jul 16 20:01:45 quoi named[6493]: error (host unreachable) resolving
'152.169.72.77.in-addr.arpa/PTR/IN': 77.72.175.217#53
Regards.
--
Yann Droneaud