problem with DNS resolving on Debian sarge 3.1

Mr. Asdf · 10-17-2005, 01:07 PM

Hi... I'm having a problem with my connection (PPPoE) on a fresh Debian 3.1 sarge installation.
Just after boot time everything is OK, I can access any working site including this one.
but after some time (a few hours probably) there seems to be a problem with DNS resolving - It just doesn't work, and I have to access site by their IP, and even then It works very slowly (tried to post here in this way and the site worked very slowly).
Till now I was using CRUX 2.1, and with the rp-pppoe package, everything worked ok - I did `pppoe-setup` or whatever that was, then `pppoe-start` and it worked without any problems.
now, in Debian there seems to be some implementation of rp-pppoe (I think...), but it isn't quite the same. I did the configuration with pppoeconf, and chose all the default answers.
I haven't really dealt with networking problems so far, so I'm quite clewless.
here's my /etc/resolv.conf :

Code:

nameserver 212.150.49.10
nameserver 206.49.94.234
search

The two IP's are my ISP's Primary and Secondary DNS Servers, respectively. I told pppoeconf to fetch the DNS Servers' IPs automatically.

any suggestions?

TIA.

Mara · 10-17-2005, 04:48 PM

Do you have anything interesting in /var/log/messages?

Also, if you're using pppoe and get DNSes automatically, backup your /etc/resolv.conf, clean it and run ppoe. It should get a number of servers (one or two). Doesn't it work better or not at all?

Mr. Asdf · 10-18-2005, 09:33 AM

Ok, It just happend again now, and I've noticed that if I `cat /etc/resolv.conf` just after it happens, this is what I get:

Code:

search
nameserver 10.0.0.138

I guess something overwrites the file - I don't know what.
Here's what I get when I `plog`after I try to reconnect with `pon` after it happens:

Code:

# plog
Oct 18 15:58:43 localhost pppd[3890]: Unable to complete PPPoE Discovery
Oct 18 15:59:03 localhost pppd[3906]: Plugin rp-pppoe.so loaded.
Oct 18 15:59:03 localhost pppd[3907]: pppd 2.4.3 started by iq, uid 1000
Oct 18 15:59:48 localhost pppd[3907]: Timeout waiting for PADS packets
Oct 18 15:59:48 localhost pppd[3907]: Unable to complete PPPoE Discovery
Oct 18 16:00:03 localhost pppd[3890]: Timeout waiting for PADS packets
Oct 18 16:00:03 localhost pppd[3890]: Unable to complete PPPoE Discovery
Oct 18 16:00:26 localhost pppd[3927]: Plugin rp-pppoe.so loaded.
Oct 18 16:00:26 localhost pppd[3929]: pppd 2.4.3 started by iq, uid 1000

After I copy my backup resolve file /etc/resolv.conf.bak back to /etc/resolv.conf, everything is fine after I `pon`, and `plog` shows:

Code:

# plog
Oct 18 16:01:36 localhost pppd[4003]: Couldn't increase MTU to 1500
Oct 18 16:01:36 localhost pppd[4003]: Couldn't increase MRU to 1500
Oct 18 16:01:36 localhost pppd[4003]: PAP authentication succeeded
Oct 18 16:01:36 localhost pppd[4003]: peer from calling number 00:02:3B:00:79:DA authorized
Oct 18 16:01:36 localhost pppd[4003]: replacing old default route to eth0 [10.0.0.138]
Oct 18 16:01:36 localhost pppd[4003]: Cannot determine ethernet address for proxy ARP
Oct 18 16:01:36 localhost pppd[4003]: local  IP address 85.65.64.154
Oct 18 16:01:36 localhost pppd[4003]: remote IP address 212.29.206.131
Oct 18 16:01:36 localhost pppd[4003]: primary   DNS address 212.150.49.10
Oct 18 16:01:36 localhost pppd[4003]: secondary DNS address 206.49.94.234

Any ideas of how can I prevent this overwriting?

edit: after the writing of this post it happend once again, which means a few minutes after the last time, so the gap between them isn't as long as it was before...

Mr. Asdf · 10-19-2005, 04:51 AM

anyone??

Mara · 10-20-2005, 04:17 PM

Please look into your /etc/pppd/options. What do you have inside? If it's a long version with many comments, please copy only not commented lines (it's rare to have more than 10).

Mr. Asdf · 10-21-2005, 06:34 AM

sorry, I haven't noticed your reply, here's my /etc/ppp/options file w/o comments:

asyncmap 0
auth
crtscts
lock
hide-password
modem
proxyarp
lcp-echo-interval 30
lcp-echo-failure 4
noipx

Mara · 10-22-2005, 06:12 PM

Comment out proxyarp option. It may be related to the message you get: Cannot determine ethernet address for proxy ARP I don't guarantee that it will help, but it's worth trying.