Re: One computer only on home net having DNS lookup trouble

Davide Bianchi wrote:
On 2006-12-30, Ron House <rhouse@xxxxxxxxxxxxxxxx> wrote:

$ host google.com


how about using dig ?

Good idea. $ dig google.com

The bad machine:

; <<>> DiG 9.3.2 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47376
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 30 IN A 64.233.167.99
google.com. 30 IN A 64.233.187.99
google.com. 30 IN A 72.14.207.99

;; Query time: 2 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Dec 30 19:38:01 2006
;; MSG SIZE rcvd: 76


A good machine:

; <<>> DiG 9.2.4 <<>> google.com
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 1530
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 4, ADDITIONAL: 4

;; QUESTION SECTION:
;google.com. IN A

;; ANSWER SECTION:
google.com. 272 IN A 72.14.207.99
google.com. 272 IN A 64.233.187.99
google.com. 272 IN A 64.233.167.99

;; AUTHORITY SECTION:
google.com. 155118 IN NS ns1.google.com.
google.com. 155118 IN NS ns4.google.com.
google.com. 155118 IN NS ns2.google.com.
google.com. 155118 IN NS ns3.google.com.

;; ADDITIONAL SECTION:
ns1.google.com. 67524 IN A 216.239.32.10
ns2.google.com. 239898 IN A 216.239.34.10
ns3.google.com. 239898 IN A 216.239.36.10
ns4.google.com. 239898 IN A 216.239.38.10

;; Query time: 59 msec
;; SERVER: 192.168.2.1#53(192.168.2.1)
;; WHEN: Sat Dec 30 19:33:58 2006
;; MSG SIZE rcvd: 212



what's in /etc/resolv.conf ?

The bad machine (kubuntu):

domain gemmie
nameserver 192.168.2.1

A good machine (plain debian):

# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
search Gemmie
nameserver 192.168.2.1


what's in /etc/nsswitch.conf ?

Both machines:

passwd: compat
group: compat
shadow: compat

hosts: files dns
networks: files

protocols: db files
services: db files
ethers: db files
rpc: db files

netgroup: nis



;; Warning: Message parser reports malformed message packet.
;; connection timed out; no servers could be reached


Did you checked if the firewall is allowing DNS resolution?

It must be, because the box is allowing all other machines to do DNS. (Unless there is some subtlety I don't understand - quite possible!)


Davide

Thanks for the suggestions Davide.

Ron House
.

Relevant Pages