"Robert" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) oups.com...
> Adrian wrote:
>> Robert wrote:
>> > No - what do I have to do?
>>
>> For a start, learn to quote. Then people will get a clue of what you're
>> replying to.
>
> F*cking Google groups...let's start again:
>
> Me: Do I have a DNS problem
>
> ABC: Maybe. Have you tried doing an nslookup to see what the dns server
> is doing?
>
> Me: No - what do I have to do?
>
> --
> Robert
>
From a command prompt the syntax is
nslookup domain name
examples
nslookup
www.bbc.co.uk
nslookup
www.google.com
The response should look something like this
Server: UnKnown
Address: 192.168.4.200
Non-authoritative answer:
Name:
www.l.google.com
Addresses: 66.249.93.99, 66.249.93.104
Aliases:
www.google.com
if you get
Server: UnKnown
Address: 192.168.4.200
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
for google or the BBC then you have a connection problem. If it takes a
while to return a ip address from your nslookup then that indicates a slow
dns server (and high latency).
From the symptoms you posted it does sound like a DNS lookup issue. You may
find that your ISP has alternative DNS server's you can use or alternatively
you could try a DNS server belonging to another ISP (I think this will
work).
Good luck
Andy