A. Khattri wrote:
> 1. Can you ping that name server?
Yes.
> 2. What is /etc/nsswitch.conf
Via another post, I'm guessing you're looking for the 'hosts' line, which is
'hosts: files dns'
> 3. Check you dont have a firewall blocking UDP 53.
Not sure how to test that. But read on...
> If you have bind-tools installed, you can run queries directly and see
> what the server sends back. Im testing that name server from one of my
> servers in New York - it works fine from here:
>
> # dig @168.95.1.1 www.utk.edu
Man, you guys are the best! (All of you who posted.) I installed
bind-tools, and the same command gave me:
[EMAIL PROTECTED] gabriel $ dig @216.81.40.41 www.utk.edu
;; reply from unexpected source: 206.169.213.252#53, expected
216.81.40.41#53
;; reply from unexpected source: 209.246.139.252#53, expected
216.81.40.41#53
;; reply from unexpected source: 206.169.213.252#53, expected
216.81.40.41#53
;; reply from unexpected source: 209.246.139.252#53, expected
216.81.40.41#53
; <<>> DiG 9.2.5 <<>> @216.81.40.41 www.utk.edu
; (1 server found)
;; global options: printcmd
;; connection timed out; no servers could be reached
[EMAIL PROTECTED] gabriel $
So I think to myself... let's try 206.169.213.252 and 209.246.139.252.
Looks like a firewall trying to be the DNS. So I added them to the top
of /etc/resolv.conf, and the problem cleared right up.
You guys are great!
For posterity, here's the working /etc/resolv.conf:
nameserver 206.169.213.252
nameserver 209.246.139.252
nameserver 168.95.1.1
Peace,
Gabriel
--
G a b r i e l M . B e d d i n g f i e l d
--
[email protected] mailing list
