So I don't know what this means.....

Today I booted up and when it had finished, I tried to log on to t'internet, and it wouldn't connect.

Windows went into it's usual diagnosis routine and told me "DNS server unavailable". Now this is what I don't know, is this a problem with my 'puter, or my router, or is it something external to my house which I have no control over? i.e. the telephone exchange, or the internet itself?

I switched the machine off along with the router and let it be for a few minutes, then booted up again and everything was back to normal and here I am. So what was the problem ?

TIA

This happens from time to time and it's usually just down to the router needing a reboot. If it's been on for a long time without a reboot, this does happen occasionally. I used to have a LinkSys router that was great most of the time but every now and then I'd get the same thing and a reboot sorted it.

It can sometimes be the PC too, if it's also not been rebooted for a long time. Generally a reboot of both (router first, then PC) will resolve the issue. If it starts happening a lot then might be worth contacting your ISP...but unless it starts to happen frequently I would worry about it.

Edited 4 January, 201313 yr by slicendice

Thank You, Most Helpful

DNS allows you to visit briskoda using www.brikskoda.net - Without it you would need to know the IP address.

It can ALSO be caused by a line fault not clearing correctly; I have this issue - I know it is not router or PC based because I tried three different routers and all 4 computers had the same problem; my ISP now know where the fault lies, but BT wont change the equipment unless it completely dies.

You could manually point the DNS to google 8.8.8.8 and see how it responds?

Can pm some details if your unsure.

You could manually point the DNS to google 8.8.8.8 and see how it responds?

Can pm some details if your unsure.

Yes please, just so I can tie it down to where the fault is.

I find the DNS error Windows gives from troubleshooting to be a complete red herring as each time I've seen it the problem has been the ADSL line is completely down. It is easy to check though, you can use a different DNS server or hold the windows button and press R, type cmd in the box and in the black window that comes up type ping 8.8.8.8 or similar which should show the following:

C:\Users\JN>ping 8.8.8.8

Pinging 8.8.8.8 with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=59ms TTL=48

Reply from 8.8.8.8: bytes=32 time=58ms TTL=48

Reply from 8.8.8.8: bytes=32 time=59ms TTL=48

Reply from 8.8.8.8: bytes=32 time=57ms TTL=48

Ping statistics for 8.8.8.8:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 57ms, Maximum = 59ms, Average = 58ms

If you get that then you may well have a DNS issue but if you just get request timed out four times then it's unlikely to be DNS. If you get successful pings you can add the -a to try and resolve the ip address, if it fails it will show the same as before which would likely be a DNS issue but if it succeeds then DNS is at least partially working and will show this:

C:\Users\JN>ping -a 8.8.8.8

Pinging google-public-dns-a.google.com [8.8.8.8] with 32 bytes of data:

Reply from 8.8.8.8: bytes=32 time=58ms TTL=48

Reply from 8.8.8.8: bytes=32 time=57ms TTL=48

Reply from 8.8.8.8: bytes=32 time=59ms TTL=48

Reply from 8.8.8.8: bytes=32 time=57ms TTL=48

Ping statistics for 8.8.8.8:

Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Approximate round trip times in milli-seconds:

Minimum = 57ms, Maximum = 59ms, Average = 57ms

John

Can sometimes be a problem with your supplier too.

If a wireless reboot fixed it then chances are your wireless router is just throwing a hissy fit, they seem to do that sometimes.