Den 2012-03-18 14:44, Bernard Lheureux skrev:
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
dig +trace 2.2.3.updates.spamassassin
18.3.2012 17:24, Bernard Lheureux kirjoitti:
> 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 ?
Try
On 03/18/2012 04:24 PM, Bernard Lheureux wrote:
I found why, that was related to my firewall, now everything is OK...
I simply had to disable the outgoing rules for DNS-OUT, because OUT is
allowed from all, and now all is OK
Thanks a lot to all of you !
On 03/18/2012 03:40 PM, Kevin A. McG
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
On 03/18/2012 02:59 PM, Kevin A. McGrail wrote:
Could this be related to a firewall rule that should be blocking it
?
Which ports should I open to ensure it works not only port 53 udp
and tcp ?
I get ; <<>
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
It means DNS is not working correctly for you.
Here's an old ISP in my areas's DN
On 3/18/12 9:44 AM, Bernard Lheureux wrote:
I get ; <<>> DiG 9.2.4 <<>> -t txt 2.3.3.updates.spamassassin.org
;; global options: printcmd
;; connection timed out; no servers could be reached
But the DNS resolution works correctly, what does that mean ?
it means the DNS resolution isn't working
On 03/18/2012 02:33 PM, Kevin A. McGrail wrote:
On 3/18/2012 9:30 AM, Bernard Lheureux wrote:
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to
work anymore since I've upgraded from 3.1.3 this seems to be related
to a DNS problem, but I can't find what I need to adapt to fix it
On 3/18/2012 9:30 AM, Bernard Lheureux wrote:
On a CentOS 4.9-x86 box I user for years, sa-update doesnt want to
work anymore since I've upgraded from 3.1.3 this seems to be related
to a DNS problem, but I can't find what I need to adapt to fix it,
could you help me ?
Definitely sounds like D
