Delay while application resolves first access to server

[Jane D]

I run XP/SP2. Something has changed on my system

When I launch an application which uses the internet (such as Opera
or Xnews) and start browsing I find that there is a pause of several
seconds when nothing seems to happen. For example, my Opera browser
has a staus message which says:

looking up www.google.com

This is shown for about 3 or 4 seconds, presumably as that domain
name is translated into an IP address. Then suddenly it is all ok
and subsequent websites are looked up very quickly.

This seems to happen on my first use of servers which I have not
visted for a long while. It seems to happen on my newsreader as well
as my browser.

Does anyone have any idea about what is causing it? And how can I
fix it?

 

[Andrew (G0RVM)]

I run XP/SP2. Something has changed on my system

When I launch an application which uses the internet (such as Opera
or Xnews) and start browsing I find that there is a pause of several
seconds when nothing seems to happen. For example, my Opera browser
has a staus message which says:

looking up www.google.com

This is shown for about 3 or 4 seconds, presumably as that domain
name is translated into an IP address. Then suddenly it is all ok
and subsequent websites are looked up very quickly.

This seems to happen on my first use of servers which I have not
visted for a long while. It seems to happen on my newsreader as well
as my browser.

Does anyone have any idea about what is causing it? And how can I
fix it?

Couple of things:

Your ISP will always have more than one DNS server.

a) Do you have them all entered into your system?
b) If they will respond to ping's then try pinging them and note any
significant ping return differences. Perhaps they are having problems with
one of them
c) try rejigging the order in which they are used (if windoze top-to-bottom)

Andrew

 

[Phillip Windell]

Nothing is wrong.
It takes a couple second to resolve,...thousands of the ISP's customers may
be using the DNS,...they may have one or two "down" causing a heavier load
on remaining ones.

Once resolution is made it is cached locally on the machine you did it with
until the cach expires and it has to resolve fresh again.

I see the same thing both here and at home,..some days are better, some
worse,..it is "life".

 

[JS]

Nothing is wrong.
It takes a couple second to resolve,...thousands of the ISP's
customers may be using the DNS,...they may have one or two
"down" causing a heavier load on remaining ones.

Once resolution is made it is cached locally on the machine you
did it with until the cach expires and it has to resolve fresh
again.

I see the same thing both here and at home,..some days are
better, some worse,..it is "life".

I think I had better describe it.

I used to get a consistent and perfectly ok service with the first
doomain name getting resolved pretty quickly.

Now I get nothing but very slow resolution of the first name.
Several seconds. And I get this all the time - day or night.

I think this is more than just normal variation.

 

[SteveB]

There are public DNS servers around you could try.

 

[Malke]

I think I had better describe it.

I used to get a consistent and perfectly ok service with the first
doomain name getting resolved pretty quickly.

Now I get nothing but very slow resolution of the first name.
Several seconds. And I get this all the time - day or night.

I think this is more than just normal variation.

Check with your ISP regarding their DNS servers. If this is a sudden
change (IOW things worked fine once), then either your ISP is having
difficulties with their DNS servers or it would be better for you to
change yours (if you've got specific servers entered manually).

Malke