Sudden connection trouble on suse
 

After weeks of trouble free operation on suse 10.0 I suddenly can't connect to the internet.
I have a BT Voyager modem using the eciadsl driver.
After doing eciadsl-start as normal it goes through the connection process but there are a couple of authentication failed messages but it eventually (apparently) connects.
I have noticed that the dns servers it displays while connecting are different to the ones I've been using and when I try to browse the net or anything nothing happens.
I've looked through some of the config files and the username and password are correct but the one thing I've noticed is that the nameservers in /etc/ppp/resolv.conf are the same as the ones displayed during connection.
I've tried changing them back to the normal ones in resolv.conf but it still won't connect and afterwards these unknown nameservers are back in resolv.conf, even after making it read only.
When I boot debian and fedora, they are connecting as normal, the connection messages are showing the normal dns servers and resolv.conf has the normal nameservers.
I've tried putting the dns servers into firefox address bar and one just doesn't connect and the other takes me here - http://www.ignite.com/uk/

This problem has happened over night, suse was connecting fine yesterday and I didn't do any upgrades or anything that could have caused changes, the last thing I did was check my email.

Its possible that these dns entries are being put into resolv.conf as part of the DHCP process during the start up of the router.

- Compare the configs for eciadsl-start from your debian and suse setups and see if there are any diffences.
- Check with BT as to what are the correct DNS addresses (For the problem to suddenly appear its possible that BT are tinkering with stuff).

Well I sort of think I know what's up. I haven't been able to access my isp's web page for a day or 2 but it's back up now and there is mention of the problem and the description is spot on, may connect but not be able to browse or anything and it also mention's the connection settings may be redirected to bt (the second dns address typed into google goes to bt now).
At the moment suse still isn't connecting but fedora and debian still are so it's strange but I'll keep tabs on the website and see if it goes back to normal, as I expect it will.