>On the server (via SSH or console) use the +trace argument to dig, and >then look for lines starting with ';;':
>postmstr@smtp:~$ dig +trace example.com.multi.uribl.com | grep ';;' >;; global options: +cmd >;; Received 913 bytes from 127.0.0.1#53(127.0.0.1) in 8 ms >;; Received 760 bytes from 199.7.91.13#53(d.root-servers.net) in 48 ms >;; Received 707 bytes from 192.54.112.30#53(h.gtld-servers.net) in 124 ms >;; Received 553 bytes from 54.149.125.143#53(o.icudp.com) in 74 ms >;; Received 206 bytes from 52.68.34.21#53(gg.uribl.com) in 147 ms >So you can see that my mail server is querying its local DNS resolver, >which is querying the root servers and then working its way down to the >appropriate uribl.com server. In your case your actual IPs will be >different, but the pattern should still hold. dig +trace always does a full root server lookup so it's not showing the same path that the /etc/resolv.conf will take. He will have to run a regular query and see if he gets back 127.0.0.1. If so, then the current resolv.conf path is still being blocked. >-- >Dave Pooser >Cat-Herder-in-Chief, Pooserville.com
