(sorry for the delay in posting this to an old thread...)
Servus!
You wrote:
> Recently mozilla has been really slow resolving some DNS queries. I tracked
> this down to a call to gethostbyname2. For some addresses (e.g.
> 'www.vanguard.com'), gethostbyname2 with AF_INET6 will fail and takes mor
Ollivier Robert wrote:
> According to Terry Lambert:
> > They are trying to be good network citizens by supporting IPv6.
>
> But they're doing it badly. gethostbyname2 (defined by RFC-2133) has been
> obsoleted by RFC-2553 and all applications SHOULD use getaddrinfo(3) or
> getnodebyname(3).
Bot
According to Terry Lambert:
> They are trying to be good network citizens by supporting IPv6.
But they're doing it badly. gethostbyname2 (defined by RFC-2133) has been
obsoleted by RFC-2553 and all applications SHOULD use getaddrinfo(3) or
getnodebyname(3).
--
Ollivier ROBERT -=- FreeBSD: The P
> "Peter" == Peter Haight <[EMAIL PROTECTED]> writes:
Peter> Of course. What's a good thing to tell them? Is the problem
Peter> that their DNS server isn't correctly responding to a query
Peter> with an unknown QTYPE?
The most common error is for the server to return an authorita
>You would do everyone a favour by notifying those sites that don't
>handle IPv6 DNS queries properly. In many (most) cases the sites aren't
>aware that their DNS software is broken. A quick e-mail will often see
>the problem fixed in short order. (bbc.co.uk is a recent example of
>this.)
Of cour
> "Peter" == Peter Haight <[EMAIL PROTECTED]> writes:
Peter> I'm going to try Terry's solution and try and do concurrent
Peter> lookups. Mozilla is already using pthreads, so I should be
Peter> able to just spawn the two requests in separate threads and
Peter> take the one tha
Mike Makonnen wrote:
> On Sun, 2002-05-12 at 14:16, Peter Haight wrote:
> > Hmm. Looking at the FreeBSD resolver code, it doesn't look like there is
> > some convenient way to do this. Maybe something like, try the lookup,
> > but if we don't get any reply in a short timeout, try an A lookup.
>In mozilla's case, it's not the FreeBSD resolver that's trying ipv6 and
>then ipv4. Mozilla does it explicitly by calling gethostbyname2 first
>with AF_INET6, and if that fails with AF_INET. You could just patch it
>to not make the first gethostbyname2 call. From a quick browse of the
>source fro
On Sun, 2002-05-12 at 14:16, Peter Haight wrote:
>
> Hmm. Looking at the FreeBSD resolver code, it doesn't look like there is
> some convenient way to do this. Maybe something like, try the lookup,
> but if we don't get any reply in a short timeout, try an A lookup. If we get
> a reply to th
Peter Haight wrote:
> >www.vanguard.com has a broken DNS implementation.
> >Find out the zone administrator via SOA record or whois and complain.
> >RFC requires the behavour you saw with google.
>
> Ok. The thing is that there are a lot of these sites. Watching the log on
> the other side of my
>www.vanguard.com has a broken DNS implementation.
>Find out the zone administrator via SOA record or whois and complain.
>RFC requires the behavour you saw with google.
Ok. The thing is that there are a lot of these sites. Watching the log on
the other side of my DNS server it looks like it is s
On Sat, May 11, 2002 at 03:53:31PM -0700, Peter Haight wrote:
>
> Recently mozilla has been really slow resolving some DNS queries. I tracked
> this down to a call to gethostbyname2. For some addresses (e.g.
> 'www.vanguard.com'), gethostbyname2 with AF_INET6 will fail and takes more
> than a min
Recently mozilla has been really slow resolving some DNS queries. I tracked
this down to a call to gethostbyname2. For some addresses (e.g.
'www.vanguard.com'), gethostbyname2 with AF_INET6 will fail and takes more
than a minute. I verified this with my own short program that does nothing
but ca
13 matches
Mail list logo
