dig @ works, dig doesn't

eelgueta · 07-09-2007, 10:52 AM

Hi All,

When I do

Code:

dig @10.0.0.2 microsoft.com

I get this:

Code:

; <<>> DiG 9.3.3rc2 <<>> @10.0.0.2 microsoft.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45745
;; flags: qr rd ra; QUERY: 1, ANSWER: 2, AUTHORITY: 5, ADDITIONAL: 5

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

;; ANSWER SECTION:
...... blah blah

However, if I do

Code:

dig microsfot.com

I get:

Code:

; <<>> DiG 9.3.3rc2 <<>> microsoft.com
;; global options:  printcmd
;; connection timed out; no servers could be reached

My config files are:

Code:

/etc/resolv.conf
10.0.0.2
10.0.0.10
164.77.246.10

/etc/host.conf
order hosts,bind

/etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1    mercurio.mydomain.local mercurio localhost.localdomain localhost

Any ideas?

This is our mail server, and is not sending any mail because of this name resolution problem. So any help, is GREATLY welcomed.

Ed.

acid_kewpie · 07-09-2007, 02:08 PM

have you messed about with /etc/nsswitch.conf? normally there is an entry in there, "hosts files dns" to define how to resolve names.

fur · 07-09-2007, 02:13 PM

Thats strange.

By not including "@10.0.0.2" dig should use the default server in /etc/resolv.conf.

Seeing how the first listed server is 10.0.0.2 it is odd it cant lookup.

The only thing I can think of is if the file permissions on /etc/resolv.conf are too restrictive.

If its not set to,

-rw-r--r--

Then try to "chmod 644 /etc/resolve.conf"

eelgueta · 07-09-2007, 03:45 PM

Thanks acid_kewpie and fur,

I did a

Code:

service NetworkManager start

and the problem is solved (I saw it was turned off). Don't know why. I don't even know what NetworkManager is.

For the record, I haven't messed with /etc/nsswitch.conf. The pertinent line reads:

Code:

hosts:      files dns

Anyway, any idea about what was going on?

Ed.

acid_kewpie · 07-09-2007, 03:48 PM

hmm, no idea off hand what networkmanager would've done there. it will rewrite resolv.conf but if you said what it did there, shouldn't be any different. what does it look like now?

eelgueta · 07-09-2007, 05:25 PM

it looks like before, no change.

fur · 07-09-2007, 06:45 PM

I think it was a file permission problem. If you chmod 600 /etc/resolv.conf you will see the same results. As a user running dig it wont be able to read resolv.conf and just timeout.

I'm not familiar with networkmanager, but acid_kewpie said it will rewrite resolv.conf. My guess is that by starting that service it fixed the permission problem by writing a new file with the proper permissions.