Doing 'dig +trace' shows two NS records for the domain, but if you query those domains, there is no response. The reason it is failing is the NS servers for '' are not properly setup. Most certainly your server is trying to resolve '' and it is failing. To get rid of the above, I added: additional-from-cache no Once I did this, I am now seeing the following in syslog: Mar 4 00:02:21 mail named: client 127.0.0.1#42139: query (cache) '24.124.41./PTR/IN' denied I've tried the following now in to block recursion. REJECT all - anywhere anywhere reject-with icmp-port-unreachable LOG all - anywhere anywhere limit: avg 5/min burst 5 LOG level debug prefix "iptables denied: " REJECT all - anywhere loopback/8 reject-with icmp-port-unreachableĪCCEPT all - anywhere anywhere state RELATED,ESTABLISHEDĪCCEPT tcp - anywhere anywhere tcp dpt:httpĪCCEPT tcp - anywhere anywhere tcp dpt:httpsĪCCEPT tcp - anywhere anywhere state NEW tcp dpt:sshĪCCEPT udp - anywhere anywhere udp dpt:domainĪCCEPT tcp - anywhere anywhere tcp dpt:domainĪCCEPT icmp - anywhere anywhere icmp echo-request My iptables reads: Chain INPUT (policy ACCEPT) I have checked my forwarders in nf, and none of them match the IPs showing in the logs (they are all basically different IPs, not just 193.95.142.60). Why would my bind setup be trying to resolve (it's not my domain, nothing to do with me).is there anything I can do firewall-wise or bind config to stop this?.In today's syslog, there are 144258 instances of this, all related to.
UNEXPECTED RCODE REFUSED RESOLVING FULL
I am having a problem with traffic bandwidth, and my syslog is full of the following type of issue: error (unexpected RCODE REFUSED) resolving '/AAAA/IN': 193.95.142.60#53Įrror (unexpected RCODE REFUSED) resolving '/A/IN': 2001:7c8:3:2::5#53 I have a website which I host myself, and I use bind9 as my DNS server (host my own nameservers etc.).
0 kommentar(er)
