On Thu, Jul 31, 2003 at 09:10:42AM -0600, Aaron Siegel wrote:
> Hello Robert
> I  have been using FreeBSD 5.1 RELEASE and Konqueror without any noticeable 
> problems with speed or name resolution.   The problem I have are related to 
> browser issue: not haveing support for shockwave, scripting problems, and 
> poorly develop sites that do not work well with the KHTML and Mozilla 
> engines. The site you referenced does load slowly for me, but I think is do 
> to the site and it is defiantly not a result of the operating system or KDE. 
> The webpage  does load some files form ad.ca.doubleclick.net see code below.
> <TD width="468" height="60" valign="middle">
> <SCRIPT language="JavaScript1.1" 
> SRC="http://ad.ca.doubleclick.net/N3081/adj/ccn.com/van/indexbanner;loc=theTop;sz=468x60;stile=1;dcopt=ist;kw=van;ord=9?";></SCRIPT><NOSCRIPT><a
> TARGET="_top" 
> HREF="http://ad.ca.doubleclick.net/N3081/jump/ccn.com/van/indexbanner;loc=theTop;sz=468x60;stile=1;kw=van;ord=9?";><IMG
> NAME="i_banner" ALIGN="TOP" BORDER="0" VSPACE="0" HSPACE="0" WIDTH="468" 
> HEIGHT="60" 
> SRC="http://ad.ca.doubleclick.net/N3081/ad/ccn.com/van/indexbanner;loc=theTop;sz=468x60;stile=1;kw=van;ord=9?";></a></NOSCRIPT></TD></TR>
> On Thursday 31 July 2003 07:41 am, Robert Froese wrote:
> > Hello,
> >
> > I'm a new FreeBSD user with a performance issue.  I've installed 5.1R and
> > KDE. I've also installed Phoenix from the ports collection. When I'm using
> > Konqueror or Phoenix to browse certain web sites they take forever to load.
> >
> > It appears the problem is associated with resolving domain names.  While I
> > wait (minutes!) for a problematic page to load, Phoenix will report in the
> > notices bar at the bottom "Resolving host ...".  There's no CPU or network
> > bottleneck and the problem is reproducable in either browser with the same
> > web sites.  It seems also to relate to situations where one web page calls
> > another for part of the content (e.g., www.vancouversun.com tries to load
> > from ad.ca.doubleclick.net).
> >
> > If I open up a shell window and ask FreeBSD to resolve the same domain
> > names with "host" they resolve instantly.  So the problem has something to
> > do with the way the package for KDE talks with BSD.
> >
> > Any advice would be greatly appreciated!

Here's why it's so slow:

    % dig ad.ca.doubleclick.net IN AAAA
    ; <<>> DiG 8.3 <<>> ad.ca.doubleclick.net IN AAAA 
    ;; res options: init recurs defnam dnsrch
    ;; res_nsend to server default -- Operation timed out

Here's how it should have responded:

    % dig www.bbc.com IN AAAA
    ; <<>> DiG 8.3 <<>> www.bbc.com IN AAAA 
    ;; res options: init recurs defnam dnsrch
    ;; got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 2
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
    ;;      www.bbc.com, type = AAAA, class = IN
    ;; Total query time: 141 msec
    ;; FROM: happy-idiot-talk.infracaninophile.co.uk to SERVER: default --
    ;; WHEN: Thu Jul 31 16:37:51 2003
    ;; MSG SIZE  sent: 29  rcvd: 29

There's absolutely nothing wrong with your systems.  The problem is
with the doubleclick.net DNS servers which incorrectly fail to respond
at all to queries for resource record types they don't know about.
That means you have to sit and wait until the request times out, which
takes something like 30s.  The bbc.com web servers do the right thing,
which is to send a negative response, and all in under 150 ms as you
can see.

Now, the RFC defining the AAAA resource record was published nearly 10
years ago, so there is really absolutely no excuse for doubleclick.net
to be running anything so broken.  However, if you're running a
webserver using the Mozilla engine, the simple response is to
right-click on the advert and select "block images from this server".

Note that there will be no problem resolving those names using host(1)
as that does an A lookup (IPv4) by default. Try:

    % host -t aaaa ad.ca.doubleclick.net

At this point you're maybe asking what a AAAA record is and why your
web browser should be trying to look one up.  The answer is that AAAA
is the IPv6 equivalent of an A record: ie. it returns the IPv6 IP
number corresponding to the hostname.  The reason that Mozilla is
doing an IPv6 lookup is that that is what the standards say to do
nowadays: see getaddrinfo(3), RFC 2553 and


(You may need to register in order to see that web page).



PS. The irony of it all is that AAAA resource records are themselves
probably going to be phased out in favour of the A6 resource type in
the not to distant future, which does essentially the same job, but
has various other advantages beyond the scope of this e-mail to go
into.  See http://www.faqs.org/rfcs/rfc2874.html if you're interested.

Dr Matthew J Seaman MA, D.Phil.                       26 The Paddocks
                                                      Savill Way
PGP: http://www.infracaninophile.co.uk/pgpkey         Marlow
Tel: +44 1628 476614                                  Bucks., SL7 1TH UK

Attachment: pgp00000.pgp
Description: PGP signature

Reply via email to