[SOLVED] dig not returning any results

[molossus]

my fedora 18 install came with bind and bind utils already,
when i query for example
host -t ns google.com
it shows me google nameservers, but when i try dig google.com and also dig for ns or mx i always get the same result no matter what option i give to dig. it always returns the address of my router.
why does host works but not dig?
am i missing something like modifying something so dig commands can work, or does the dig command only works on centos and rhel , server distros only or what?

[george_toolan]

Is your name server working correctly? Dig should be working out of the box at least it does with Fedora 16.

Try the google name server instead:

dig @8.8.8.8 google.com MX

[Smit-Tay]

Do you mean that your router is indicated in the ANSWER section or in the information at the bottom of the output, like this ?

;; Query time: 36 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Mar 7 17:36:15 2013
;; MSG SIZE rcvd: 175

[molossus]

Originally Posted by Smit-Tay

Do you mean that your router is indicated in the ANSWER section or in the information at the bottom of the output, like this ?

;; Query time: 36 msec
;; SERVER: 192.168.1.1#53(192.168.1.1)
;; WHEN: Thu Mar 7 17:36:15 2013
;; MSG SIZE rcvd: 175

yes doesnt matter what i try to get from dig, it just return the address of my router in the response
host command works fine i can get ns and mx results.
could it be my isp? or firewall that prevents dig from working properly?

[Smit-Tay]

I think dig is simply a utility to let you perform any number of DNS queries that would normally be done on your behalf by other apps like a browser or MTA. It should always work.

Have you modified resolve.conf ?

Have you thoroughly read the man page.

[george_toolan]

Btw it's /etc/resolv.conf

To rule out any problems with your isp's name server or your router's dodgy name server/proxy just use a different name server.

[Smit-Tay]

Originally Posted by george_toolan

Btw it's /etc/resolv.conf

Indeed. My mistake. I accidentally applied a human language spelling to a file I am uncomfortably familiar with.

[molossus]

Found the solution, the problem is my isp , which is att uverse router

normally dig google.com should return A records , but in my case it didnt ,

the fix is to use +noedns

dig +noedns google.com

and it works perfectly

[Smit-Tay]

Sounds like you have a mis-configured router or firewall.

The EDNS protocol should be fairly transparent, unless your router or firewall is trying to second guess the conversation. It may be that one or the other sees the unusual size of the EDNS UDP packet and decides it something malicious, and so discards it. That's not really supposed to happen, obviously.