On 23 Jul 2006, in the Usenet newsgroup comp.os.linux.networking, in article
<(E-Mail Removed) .com>, michanux wrote:
>You answered to 'no resolving'
Yes, and please either use the news server from your ISP, or learn how
to use google to 'reply' to a thread. You're making it very difficult
for anyone to help you be creating new threads rather than replying to
the replies. See Michael Heiming's "A new reader?" thread posted twice a
week to comp.os.linux.misc among other groups;. Specifically, see the
section "Google Groups users please read - Howto reply properly"
http://groups.google.com/support/bin...y?answer=14213
Also, please don't direct articles at an individual - I'm a network admin,
not a programmer.
>>Try using 'strace' to see where things are barfing. Try
>I don't find an importent missing file:
I don't see anything obvious either. Looking back through the articles
you've posted (much more difficult because of the new threads, rather than
appending to a single thread), in your first post you showed that nslookup
had no problem resolving the hostname. Try running an strace on the nslookup
and see how it differs from this.
Second, what exactly is in /etc/resolv.conf file? Asking my name servers
about 'michael.zuhause.de' returns a NXDOMAIN, so I'm assuming you are
asking ONLY the name server that is authoritative for that address, and
not asking the name servers from your ISP. You must remember that the
resolver code believes the first answer it receives, even if that answer
is "I don't know". Thus, if the resolver asks your ISP because that one
is responding faster and the ISP replies 'NXDOMAIN', then the resolver's
job is done. It will NOT try another name server hoping to get an answer.
Old guy