#Refused unexpected rcode resolving verification#

October 3 8:05:46 ns1 named : error (RCODE REFUSED unexpected)resolving '97.Not sure if it has any fancy time based rules, but will check.

If I turn off the dnscache zimbra server, I can successfully issue the dig command that queries the txt DKIM entry for the domain that is failing when dnscache is enabled. On the command line, I'm trying to issue dig commands and most of the time they are successful, but for one particular domain, they always fail.

#Refused unexpected rcode resolving verification#

Some of my DKIM verification queries are failing in Spamassassin due to DNS timeout. Hi guys, I am having something very similar, which I highlighted in this viewtopic.php?f=15&t=66112 seperate zimbra forum thread. The problem was RESOLVED, thanks everybody so much! SPAM was denied by DNS Blocklist and DCC, Razor + Pyzor score count again and SPF module works as a gate keeper. I disabled this rule for 24h till now, everything come back like before.

With 'dns: bad dns reply' this clue drives me to check the queries to DNS but when i manually queried, it's seem OK.įinally, i found that some queries are good, some queries are bad because the firewall block UDP due to a Outbound UDP Flood rule. With 'Operation not permitted' i think it's related permission but zmfixperms don't think like this, everything is good. Many many errors related Host not found or Domain cannnot lookup although i change DNS master anymore. I was upset for 3 days from this issue raises, SA includes DCC, DNS Blocklist and Razor, Pyzor seem cannot connect to get data, so the system immediately was attacked by SPAM, even the SPF module also doesnot work when it always said that: Gmail has no correct SPF record. I saw one last week with 20+ NS records and they connected repeatedly before our dynamic ipset rules put them in timeout for 4 hr. Our noc has a swatch monitor up watching for syslog patterns and it will turn red when these errors are displayed because we track errors with red on the monitor. Sep 21 17:41:08 mail amavis: (08919-02) SA info: dns: bad dns reply: bgread: recv() failed: Connection refused at /opt/zimbra/common/lib/perl5/Mail/SpamAssassin/DnsResolver.pm line 743.Ĭode: Select all Sep 21 05:54:30 relay10 named: error (unexpected RCODE REFUSED) resolving '18.-addr.arpa/PTR/IN': 211.139.178.48#53 Sep 21 17:41:05 mail amavis: (08919-02) SA info: dns: bad dns reply: bgread: recv() failed: Connection refused at /opt/zimbra/common/lib/perl5/Mail/SpamAssassin/DnsResolver.pm line 743. Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Operation not permitted, no more alternatives Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Connection refused, failing over to :53 Sep 21 17:41:05 mail amavis: (08919-02) _WARN: dns: sendto() to :53 failed: Operation not permitted, failing over to :53