Strange DNS problem (Debian)

Torky · 05-12-2004, 07:05 PM

Hello there,

i have Debian Woody running on my server/router for quite a time now, and everything works fine with my win2k machine. Last week i installed Debian Testing/Unstable at my notebook, and nearly everything is running fine .. *nearly* everything. Somehow DNS is "broken".

Here the facts.
if i do a "nslookup hostname" or "host hostname" i get an ip within one second.

but now if i do "ping hostname" its takes between 6 to 10 seconds until the hostname is resolved and the first ping goes out.
Same thing with lynx or firefox or whatever

As you can imagine browsing is a real pain that way.

I tried several DNS Servers, i also set up a DNS at my Router - no change.

some files

/etc/resolv.conf

Code:

search
nameserver 217.5.113.240
nameserver 194.25.2.129

as i said, i tried several other nameservers (those are from t-online now), all reachable and working good on my windows machine. i also tried it without the "search" line.

/etc/host.conf

Code:

order bind,hosts
multi on

/etc/network/interfaces

Code:

auto eth0
iface eth0 inet static
        address 192.168.0.18
        netmask 255.255.255.0
        network 192.168.0.0
        broadcast 192.168.0.255
        gateway 192.168.0.1

192.168.0.1 is my router of course

i don't have any clue what else to do ..

one thing i noticed .. i got freenet.de at first as apt-source, when this hostname was looked up it looked like ipv6 ##:##:##:## style but i don't use ipv6 (afaik ..). i changed the line in /etc/apt/sources.lst and never saw something like ipv6 again.

maybe someone here has an idea?

peacebwitchu · 05-12-2004, 07:20 PM

Have you tried setting the /etc/host.conf order from

order bind,hosts

to

order hosts,bind

Also could you post your

hostname -f

and /etc/hosts file.

Torky · 05-13-2004, 04:19 AM

Code:

torky@wotan:~$ hostname -f
localhost

/etc/hosts

Code:

127.0.0.1       localhost       wotan
192.168.0.18    wotan
192.168.0.1     gilgamesh
192.168.0.17    torky

changing the order of bind,hosts in host.conf didn't have any noticeable effect.

peacebwitchu · 05-13-2004, 08:49 AM

try taking the search string out of /etc/resolv.conf
In the man page for /etc/resolv.conf it states that this can cause timeouts in some situations.

Torky · 05-13-2004, 11:56 AM

Quote:

Originally posted by Torky
as i said, i tried several other nameservers (those are from t-online now), all reachable and working good on my windows machine. i also tried it without the "search" line.

today i tried the laptop in 2 other networks - same effect so it *hast* to do s.th. with that machine, but i still don't have any clue

yichun · 06-21-2004, 07:46 PM

Has your problem solved? I met the same problem. I put a line to prevent ipv6 module from loading in /etc/modules.conf, but when 'lynx url' the lynx still go on to search ipv6 address first. I do not know anyone has solved this. Strangely seems many has no this problem.

Torky · 06-22-2004, 04:02 AM

not really "solved" but since i am using a dns from my university (i still dial in with t-online!) its a lot better, first look needs still about 2s, but after that all dns lookups dont need more time then that.

i noticed that dns is slower again, if i use more then one dns.