Unable to resolve Domain from external machines.

Found these wonderful forums yesterday and have been digging through the archives since. I haven't been able to find anyone with the same problem, so I figured I'd post my problem and see if anyone can help.

I've got a RH9 bind 9.2.1 machine which is supposed to be the primary nameserver for neomassage.com (ns1.massagebuilder.com)

On that machine I can resolve the DNS just fine as shown below:
> test.neomassage.com
Server: 127.0.0.1
Address: 127.0.0.1#53

Name: test.neomassage.com
Address: 66.207.163.82

However every other machine i tried it from gets the
;; connection timed out; no servers could be reached
message

I did a netstat -an | grep 53 and got the following :

tcp 0 0 66.207.163.82:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:53 0.0.0.0:* LISTEN
tcp 0 0 127.0.0.1:953 0.0.0.0:* LISTEN
udp 0 0 0.0.0.0:53 0.0.0.0:*
udp 0 0 66.207.163.82:53 0.0.0.0:*
udp 0 0 127.0.0.1:53 0.0.0.0:*

The machine is co-located at a datacenter plugged directly into our ethernet drop, so it should be accessible...

Did I miss something? Any suggestions would be greatly appreciated.

ns1.massagebuilder.com (66.207.163.82)
ns2.massagebuilder.com (66.207.163.83)

You told your registrar those are your name servers. The ...83 IP times out and the 82 IP reports that the server is not running. I suggest that you reregister the ns2.massagebuilder.com to use the ...82 IP so that timeouts don't occur.

Yeah the 83 machine suffered from massive raid failure last week and is out on sick leave.
I'll give the renumbering of ns2 to 82 a go and see what happens .

So am I reading your response right and the 82 server is reporting that the 83 isnt running and that's causing requests to 82 timeout?

No, that was only half the problem. You need to get the dns server running again on the 82. Here's a link to make remote testing convenient:

http://www.dollardns.net/cgi-bin/dn...&lr=4&submit=DS

There are several possabilities as to why I got this message.

1) The dns server is not running
2) The router forwarded the request to the wrong server
3) A firewall somewhere blocked the port and sent back a "port unreachable" icmp message. This is somewhat unlikely as firewalls usually don't respond at all - resulting in a timeout.