On 03/18/2012 03:40 PM, Kevin A. McGrail wrote:
Which ports should I open to ensure it works not only port 53 udp and
tcp ?
I'm assuming dig -t txt 2.3.3.updates.spamassassin.org @ns.erols.com
doesn't work for you either.
http://systembash.com/content/dns-server-firewall-open-ports/
Has a good list of ports but it's basically 53 tcp/udp and every
single upper port because of the back channel. If your firewall
automatically recognizes and opens back channels, you might be ok.
My FW is a Watchguard Firebox III/700 and ALL is open for OUTGOING, then
I don't think this could be caused by this...
But I cannot find why this answers always:
[root@myserver ~]# dig -t txt 2.3.3.updates.spamassassin.org
; <<>> DiG 9.3.6-P1-RedHat-9.3.6-20.P1.el5 <<>> -t txt
2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
I use my own Bind9 DNS server which is running OK for a long time ago...
And the 2 forwarders on this server are the 2 DNSes of my ISP what could
be wrong ?
Do you know if I could try to use public DNS as forwarders ?
If yes, which ones ?
--
(°- Bernard Lheureux Gestionnaire des MailingLists ML, TechML, LinuxML
//\ http://www.bbsoft4.org/Mailinglists.htm ** MailTo:r...@bbsoft4.org
v_/_ http://www.bbsoft4.org/<<<<<< *>>>>>> http://www.portalinux.org/
