DNS resolving problems

[Patrick von der Hagen]

Jason Vas Dias wrote:
  [...]
> 2. Please quantify the problem - send us the /tmp/tcpdump.dns.log created by:
>   # tcpdump -vvv -ttt -nl -s 8192 -i any port domain >/tmp/tcpdump.dns.log 2>&1 &
>   # host a.name.that.takes.a.long.time.to.resolve
>   # pkill tcpdump
I have the same problem like Stelian, but since I changed my provider 
recently, I didn't suspect Rawhide. However, when following your steps, 
I get this:
[root at localhost ~]# host www.union-invest.de
www.union-invest.de has address 193.24.35.212
;; connection timed out; no servers could be reached
;; connection timed out; no servers could be reached

The IPv4-address is returned without delay, but then it takes several 
seconds for other requests to timeout. I won't post my tcpdump.dns.log 
here, since it seems to be very similar to the one already posted by 
Stelian.


> 
> NOTE: previous response to this issue:
>   On Wednesday 15 February 2006 13:53, John Reiser <jreiser at bitwagon.com> wrote:
>>  Is the code waiting for timeout of non-existent IP6 routing?
>>  If so, then disable IP6.
>   This problem has been fixed for a long time in BIND, and should not be 
>   a problem with glibc resolver - do you have any resolv.conf options settings ?
Hah. John's suggestion was very valuable, because after removing my 
IPv6-adresses ("ifconfig lo del ::1/128",...) I get
[root at localhost ~]# host www.union-invest.de
www.union-invest.de has address 193.24.35.212
[root at localhost ~]#

No timeouts and a very good response-time. :-) I had two IPv6-addresses 
and two timeouts first and after removing both IPv6-adresses both 
timeouts disappeard.

[root at localhost ~]# cat /etc/resolv.conf
# generated by NetworkManager, do not edit!

search hek.uni-karlsruhe.de


nameserver 62.72.64.237
nameserver 62.72.64.241

-- 
CU,
    Patrick.