bt dns server woes

[sulky_uk]

so there i was having a nice time surfing yesterday morning and her indoors wanted to go shopping, so i switched the comp into standby and went out. on return i could only load selected pages, after a while trying to work it i finaly phoned the help desk from bt. unfortunatly the help desk has been moved to another country so they r a bit hard to get the point across to. I tried to explain that it wasnt my computer or routers i had also tried to connect using my lappy and sons comp using two differant routers, but they werent very helpful.

came on the server last night (eventually) and most of the lads on the team said that is a dns issue, so rather than clear off i played a couple of games (which were good) and then went to google.

found a couple of bt dns server adresses but they failed to work so i sat looking at ask and google till two am (i could only look at google after a router restart and then ask after another restart) so i gave up.

got up at 9 this morning and guess what??

the fecker works all websites, no page not found, nothing, bt you feckers it better work for tomorrow  :ranting2:

thx for the help. if anyone knows of any bt dns adresses could you pm them to me as i dont think that info should be posted

thx guys

[Rabbi Bob]

Did you try a solid reboot after coming back from standby?  Standby has a habit of dropping some things on the way back in.  Sometimes #>ipconfig /flushdns from the command line is enough to jumpstart the dns on the client.

p.s.  A good test if you're on broadband and have a residential router:  most routers have a test page and you can ping/traceroute from the router out.  If you don't have more than one PC in the house, this is a great way to see if the issue is the PC or your connection, or atleast take the impetus away from the PC.

[sulky_uk]

Originally posted by Rabbi Bob@Dec 30 2005, 11:18 AM
Did you try a solid reboot after coming back from standby? Standby has a habit of dropping some things on the way back in. Sometimes #>ipconfig /flushdns from the command line is enough to jumpstart the dns on the client.

[post=107438]Quoted post[/post]

[/b]

yeah tried absoluly everything icluding resetting the netsh int ip reset resetlog.txt

thx for the advice.

[BlastUK]

don't use bt dns servers then, borrow somebody elses, i used another isp's dns servers before because mine kept screwing up

heres mine at the moment

Primary DNS   62.24.128.5
Secondary DNS   62.24.128.69

[Liberator]

These are the servers I have locked into my router as I used to have problems with the ones supplied by DHCP on BT.

194.74.65.68
194.72.9.34
217.32.105.91
194.72.6.57
217.35.209.190

They are still BT ones, but they have so far been stable. Not sure if the router roundrobins or just goes for the first one.

[Benny]

Have some more

158.43.240.3 and 4

the first IP addresses I ever memorised....

[sulky_uk]

cheers guys its all running stable at the mo but im gonna write those isp's down :biggrin: