Ah ok, that's probably part of what I missed. I suppose that 203.42.34.54 is the IP address you tried to access, right?
I wonder - did you keep getting "connection refused" when the server listened on the TCP port and the only problem was the firewall?
For security's sake, I'd recommand blocking TCP access to your BIND
from anyone but your designated secondaries. Otherwise you open
this sensitive server for DOS attacks and all sorts of hazards, and they are not
necessary for anyone else.
Cheers,
--Amos
Voytek wrote:
Amos
it looks I sorted some more of it, by, enabling TCP not just UDP:
# netstat -tanp | grep :53 tcp 0 0 203.42.34.54:53 0.0.0.0:* LISTEN 27791/named
but, the prob was I was blocking port 53
-- SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/ Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
