Re: One computer only on home net having DNS lookup trouble
- From: ibuprofin@xxxxxxxxxxxxxxxxxxxxxx (Moe Trin)
- Date: Sat, 30 Dec 2006 15:30:25 -0600
On Sat, 30 Dec 2006, in the Usenet newsgroup comp.os.linux.networking, in
article <en5cd5$200$1@xxxxxxxxxxxxxxxxxxxxxx>, Ron House wrote:
Good idea. $ dig google.com
The bad machine:
is returning data, but you seem to be running into cache problems. The
bad system didn't show 'AUTHORITY' or 'ADDITIONAL' records. Try this
instead. Query somehost.name.com on one system, then as quickly as
practical (seconds), repeat the query on the other, AND THEN AGAIN on
the first - and compare those last two. This more smells of a packet
corruption, and I'd suggest looking at the outputs of a packet sniffer
to detect this. As you can go to the sites by IP address, this would
suggest a UDP problem, rather than IP or packet level - but off the top
of my head I have no idea what might be the actual cause.
As for the problem of which interface gets brought up by default, that's
a configuration error thanks to the helpful installer guessing wrong.
Clicking on something says GUI - and I don't bother administering my
systems that way. You may see the source of the problem in your
/etc/network/interfaces file.
what's in /etc/resolv.conf ?
The bad machine (kubuntu):
domain gemmie
A good machine (plain debian):
search Gemmie
man 5 resolver 'domain' and 'search' are not very useful. If you
were to be using multicast DNS (I doubt you are), this would lay you open
to some really nasty hacks. An example of such a service is 'avahi'
Old guy
.
- References:
- One computer only on home net having DNS lookup trouble
- From: Ron House
- Re: One computer only on home net having DNS lookup trouble
- From: Ron House
- One computer only on home net having DNS lookup trouble
- Prev by Date: Re: One computer only on home net having DNS lookup trouble
- Next by Date: Re: 30 second delay before ping command will succeed
- Previous by thread: Re: One computer only on home net having DNS lookup trouble
- Next by thread: threading issue : SIGPIPE => SIG_IGN (writing to closed socket)
- Index(es):
Relevant Pages
|