slow to open a web page, last too long to 'looking up ...'

[L]

Hi,

I experienced a slow web page openning. When I try to open a web page eg
http://home.aapt.com.au, It starts 'looking up home.aapt.com.au, this lasts
more than 40 seconds then to start 'transfer from home.aapt.com.au. VERY
SLOW.
However, if I got the ip adddress of this, eg
http://203.63.89.59
the 'looking up' lasts less than 2 seconds and start trasfer ...

I guess it may relate to the ISP dns, apart from the ISP side, what else I
can improve this?

Thanks

Yuan

[Rick Stevens]

On Fri, 2007-11-02 at 09:01 +1100, Lux Zhang wrote:
>  Hi,
>  
>  I experienced a slow web page openning. When I try to open a web page
>  eg http://home.aapt.com.au, It starts 'looking up home.aapt.com.au,
>  this lasts more than 40 seconds then to start 'transfer from
>  home.aapt.com.au. VERY SLOW.
>  However, if I got the ip adddress of this, eg
>  http://203.63.89.59
>  the 'looking up' lasts less than 2 seconds and start trasfer ...
>  
>  I guess it may relate to the ISP dns, apart from the ISP side, what
>  else I can improve this? 
Not much.  You should isolate DNS from possible load balancer issues at
the remote site.  Do several "host home.aapt.com.au" or "dig
home.aapt.com.au" commands to see how long the DNS service really takes
to do the resolution.  If the DNS resolution is slow, then I'd file a
complaint with your ISP.

If the resolution is relatively speedy, then there's two additional
possibilities: bad routing from your ISP to aapt or aapt is using some
form of load balancing mechanism that's overburdened or not working
well.  Test the routing with several runs of traceroute.  If you see
routes that take too long, then I'd tell your ISP to check it.  If the
traceroutes look OK, then aapt's load balancer may be having issues.  In
that case, file a report with aapt since the problem's at their end.

----------------------------------------------------------------------
- Rick Stevens, Principal Engineer             rstevens(a)internap.com -
- CDN Systems, Internap, Inc.                http://www.internap.com -
-                                                                    -
-          Consciousness: that annoying time between naps.           -
----------------------------------------------------------------------

[Andy Green]

Somebody in the thread at some point said:
>  Hi,
>  
>  I experienced a slow web page openning. When I try to open a web page eg
>  http://home.aapt.com.au, It starts 'looking up home.aapt.com.au
>  <http://home.aapt.com.au>;, this lasts more than 40 seconds then to start
>  'transfer from home.aapt.com.au <http://home.aapt.com.au>;. VERY SLOW.
>  However, if I got the ip adddress of this, eg
>  http://203.63.89.59 <http://203.63.89.59>
>  the 'looking up' lasts less than 2 seconds and start trasfer ...
>  
>  I guess it may relate to the ISP dns, apart from the ISP side, what else
>  I can improve this? 
You can run your own cacheing DNS server very easily with Fedora.

Just install bind

# yum install bind caching-nameserver
# service named start
# chkconfig named on

Edit /etc/resolv.conf to say to use your own DNS

nameserver 127.0.0.1

...and that's it, you can test with ping

ping home.aapt.com.au

If your normal DNS server is unreliable, this is a great and fast fix.

-Andy

[Craig White]

On Thu, 2007-11-01 at 22:20 +0000, Andy Green wrote:
>  Somebody in the thread at some point said:
>  > Hi,
>  > 
>  > I experienced a slow web page openning. When I try to open a web page eg
>  > http://home.aapt.com.au, It starts 'looking up home.aapt.com.au
>  > <http://home.aapt.com.au>;, this lasts more than 40 seconds then to start
>  > 'transfer from home.aapt.com.au <http://home.aapt.com.au>;. VERY SLOW.
>  > However, if I got the ip adddress of this, eg
>  > http://203.63.89.59 <http://203.63.89.59>
>  > the 'looking up' lasts less than 2 seconds and start trasfer ...
>  > 
>  > I guess it may relate to the ISP dns, apart from the ISP side, what else
>  > I can improve this?
>  
>  You can run your own cacheing DNS server very easily with Fedora.
>  
>  Just install bind
>  
>  # yum install bind caching-nameserver
>  # service named start
>  # chkconfig named on
>  
>  Edit /etc/resolv.conf to say to use your own DNS
>  
>  nameserver 127.0.0.1
>  
>  ...and that's it, you can test with ping
>  
>  ping home.aapt.com.au
>  
>  If your normal DNS server is unreliable, this is a great and fast fix. 
----
unless the problem is ipv6

try turning ipv6 off

system-config-network (select your interface, double click it, uncheck
ipv6, save, restart)

Craig