provider DNS response slow after DHCP IP renewal
Hello. I have a networking issue. Sometimes, because I am switching from one comupter to another to connect to the net, my provider doesn't assign my IP address through DHCP. I go to the other computer (Windows), release the IP and restart the network on mine (SuSE8.2). I do get an IP address but the DNS is then VERY slow to respond. I think that a reboot solves this issue each time but I presume that it means there is another way to solve it. Any hint knowing that I don't have the possibility to build/buy a router? TIA! Patrick
On Sun, May 16, 2004 at 05:57:47PM +0200, Patriiiiiiiiiick wrote:
Hello.
I have a networking issue. Sometimes, because I am switching from one comupter to another to connect to the net, my provider doesn't assign my IP address through DHCP. I go to the other computer (Windows), release the IP and restart the network on mine (SuSE8.2). I do get an IP address but the DNS is then VERY slow to respond. I think that a reboot solves this issue each time but I presume that it means there is another way to solve it.
Any hint knowing that I don't have the possibility to build/buy a router?
Use 'tethereal -n -i ppp0 port 53' to find out what is going on on the wire, you'll see DNS queries and responses, and then see which servers are queried. Your resolv.conf is probably not updated, but I'm not sure because I don't fully understand your setup. You can try whether DHCLIENT_RELEASE_BEFORE_QUIT=yes in /etc/sysconfig/network/dhcp and 'rcnetwork restart' helps. Peter
poeml@cmdline.net wrote:
On Sun, May 16, 2004 at 05:57:47PM +0200, Patriiiiiiiiiick wrote:
I have a networking issue. Sometimes, because I am switching from one comupter to another to connect to the net, my provider doesn't assign my IP address through DHCP. I go to the other computer (Windows), release the IP and restart the network on mine (SuSE8.2). I do get an IP address but the DNS is then VERY slow to respond. I think that a reboot solves this issue each time but I presume that it means there is another way to solve it.
Any hint knowing that I don't have the possibility to build/buy a router?
Use 'tethereal -n -i ppp0 port 53'
I've begun by installing ethereal and ran it after a network restart. While at the usage, it seemed I had the same slowlyness, I don't know if the behaviour on the net was the same as when I had that issue. At least, it seems it got fixed from itself a few seconds after this atempt. I'll use this the next time I encounter this issue. Here is the output for illustration: 0.000000 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org 0.164316 152.158.16.48 -> 213.214.32.2 DNS Standard query response 0.181393 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org.coditel.net 0.206041 152.158.16.48 -> 213.214.32.2 DNS Standard query response, No such name 0.206778 213.214.32.2 -> 152.158.16.48 DNS Standard query A www.netfilter.org 0.293273 152.158.16.48 -> 213.214.32.2 DNS Standard query response A 213.95.27.115 0.294301 213.214.32.2 -> 152.158.16.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 5.295754 213.214.32.2 -> 152.158.2.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 8.305753 213.214.32.2 -> 152.158.36.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 14.317034 213.214.32.2 -> 152.158.16.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 19.325676 213.214.32.2 -> 152.158.2.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 22.335689 213.214.32.2 -> 152.158.36.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 29.488064 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org 29.531440 152.158.16.48 -> 213.214.32.2 DNS Standard query response 29.531898 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org.coditel.net 29.572968 152.158.16.48 -> 213.214.32.2 DNS Standard query response, No such name 40.745234 152.158.16.48 -> 213.214.32.2 DNS Standard query response, Server failure 40.745360 152.158.16.48 -> 213.214.32.2 DNS Standard query response, Server failure 45.500650 152.158.2.48 -> 213.214.32.2 DNS Standard query response, Server failure 45.501187 152.158.2.48 -> 213.214.32.2 DNS Standard query response, Server failure 48.500901 152.158.36.48 -> 213.214.32.2 DNS Standard query response, Server failure 48.501237 152.158.36.48 -> 213.214.32.2 DNS Standard query response, Server failure
Your resolv.conf is probably not updated
Yes, it is.
You can try whether DHCLIENT_RELEASE_BEFORE_QUIT=yes in
It was set.
/etc/sysconfig/network/dhcp and 'rcnetwork restart' helps.
Is this the same as '/etc/init.d/network restart'? Thank you already for your help! Patrick
On Tue, May 25, 2004 at 11:03:21PM +0200, Patriiiiiiiiiick wrote:
poeml@cmdline.net wrote:
On Sun, May 16, 2004 at 05:57:47PM +0200, Patriiiiiiiiiick wrote:
I have a networking issue. Sometimes, because I am switching from one comupter to another to connect to the net, my provider doesn't assign my IP address through DHCP. I go to the other computer (Windows), release the IP and restart the network on mine (SuSE8.2). I do get an IP address but the DNS is then VERY slow to respond. I think that a reboot solves this issue each time but I presume that it means there is another way to solve it.
Any hint knowing that I don't have the possibility to build/buy a router?
Use 'tethereal -n -i ppp0 port 53'
I've begun by installing ethereal and ran it after a network restart. While at the usage, it seemed I had the same slowlyness, I don't know if the behaviour on the net was the same as when I had that issue. At least, it seems it got fixed from itself a few seconds after this atempt. I'll use this the next time I encounter this issue. Here is the output for illustration:
0.000000 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org 0.164316 152.158.16.48 -> 213.214.32.2 DNS Standard query response 0.181393 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org.coditel.net 0.206041 152.158.16.48 -> 213.214.32.2 DNS Standard query response, No such name 0.206778 213.214.32.2 -> 152.158.16.48 DNS Standard query A www.netfilter.org 0.293273 152.158.16.48 -> 213.214.32.2 DNS Standard query response A 213.95.27.115 0.294301 213.214.32.2 -> 152.158.16.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 5.295754 213.214.32.2 -> 152.158.2.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 8.305753 213.214.32.2 -> 152.158.36.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 14.317034 213.214.32.2 -> 152.158.16.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 19.325676 213.214.32.2 -> 152.158.2.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 22.335689 213.214.32.2 -> 152.158.36.48 DNS Standard query PTR 115.27.95.213.in-addr.arpa 29.488064 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org 29.531440 152.158.16.48 -> 213.214.32.2 DNS Standard query response 29.531898 213.214.32.2 -> 152.158.16.48 DNS Standard query AAAA www.netfilter.org.coditel.net 29.572968 152.158.16.48 -> 213.214.32.2 DNS Standard query response, No such name 40.745234 152.158.16.48 -> 213.214.32.2 DNS Standard query response, Server failure 40.745360 152.158.16.48 -> 213.214.32.2 DNS Standard query response, Server failure 45.500650 152.158.2.48 -> 213.214.32.2 DNS Standard query response, Server failure 45.501187 152.158.2.48 -> 213.214.32.2 DNS Standard query response, Server failure 48.500901 152.158.36.48 -> 213.214.32.2 DNS Standard query response, Server failure 48.501237 152.158.36.48 -> 213.214.32.2 DNS Standard query response, Server failure
152.158.2.48 is simply extremely slow, before it finally replies. The best fix is probably to report it to the ISP, add other nameservers, or avoid the slow one altogether. Look at the forwarders setting in named.conf. Or, use 'forward first' instead of 'forward only' in named.conf, so your nameserver can do it as well if the forwarders fail. A big ISP here in Germany currently has similar problems with one or some of their nameservers.
Your resolv.conf is probably not updated
Yes, it is.
You can try whether DHCLIENT_RELEASE_BEFORE_QUIT=yes in
It was set.
/etc/sysconfig/network/dhcp and 'rcnetwork restart' helps.
Is this the same as '/etc/init.d/network restart'?
It is. Peter
participants (2)
-
Patriiiiiiiiiick
-
poeml@cmdline.net