Bind9 Error Unexpected Rcode Refused Resolving
Contents |
Bind logs? named[xxxxxx]: unexpected RCODE (REFUSED) resolving ‘xx.xx.xx.xx.in-addr.arpa/PTR/IN': xxx.xxx.xxx.xxx#53 This is probably because you have a forwarder in your named.conf that refuse your requests. Simply look at the end of the named error unexpected rcode refused resolving previous line : "xxx.xxx.xxx.xxx#53" and search this address in your named
Lame Servers Info Error Unexpected Rcode Refused Resolving
configuration file - it should be located inside the forwarders : Shell forwarders { xxx.xxx.xxx.xxx; }; 1 forwarders
Error Unexpected Rcode Servfail Resolving
{ xxx.xxx.xxx.xxx; }; You need to remove or comment this host to get rid of the error in log or allow your host to query this server if it
Lame Server Resolving
belongs to you! Tip : To make sure the remote DNS server you are trying to query is refusing your request, you can try to DIG a host like this replacing the domain and IP to meet your situation : Shell dig domain.tld @xxx.xxx.xxx.xxx 1 dig domain.tld @xxx.xxx.xxx.xxx Be Sociable, Share! Tweet Category: Servers About Kaven G. System rcode refused dns Engineer / Network Administrator View all posts by Kaven G. → Post navigation ← Bind : Transfer of ‘domain.tld' from xx.xx.xx.xx#53 failed receiving responses permission denied Linux : Error running command require /proc could not read procfs → ITechLounge.netLinux : Port forwarding with IPtables Search for: Categories Downloads ITechLounge Mac Multimedia Networking Operating Systems PC Security Servers Storage Virtualization Web Tools.ITechLounge.net |-> BandwidthTest |-> GetMyIP |-> NS Lookup |-> Ping |-> TraceRoute |-> Whois Recent Posts Linux : Port forwarding with IPtables Mac : Unable to negotiate with x.x.x.x port 22: no matching key exchange method found. Their offer: diffie-hellman-group1-sha1 Windows : How to enable the Administrator account in Windows Home Edition Linux : How to setup client/server NFS on SuSE Office : How to remove the first three characters of each lines in a Word document? Archives Archives Select Month September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 January 2016 December 2015 November 2015 October 2015 September 2015 August 2015 July 2015 June 2015
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the error (formerr) resolving company Business Learn more about hiring developers or posting ads with us Server Fault Questions category lame-servers {null;}; Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them; unexpected rcode (servfail) from master it only takes a minute: Sign up Here's how it works: Anybody can ask a question Anybody can answer The best answers are voted up and rise to the top unexpected RCODE REFUSED - eating up log http://www.itechlounge.net/2011/12/bind-unexpected-rcode-refused-resolving-xx-xx-xx-xx-in-addr-arpaptrin/ files up vote 1 down vote favorite 1 I have a website which I host myself, and I use bind9 as my DNS server (host my own nameservers etc.). I am having a problem with traffic bandwidth, and my syslog is full of the following type of issue: error (unexpected RCODE REFUSED) resolving 'target-express.com/AAAA/IN': 193.95.142.60#53 error (unexpected RCODE REFUSED) resolving 'target-express.com/A/IN': 2001:7c8:3:2::5#53 In today's syslog, there are 144258 instances of this, all related to http://serverfault.com/questions/672566/unexpected-rcode-refused-eating-up-log-files target-express.com. My questions are: is there anything I can do firewall-wise or bind config to stop this? Why would my bind setup be trying to resolve target-express.com (it's not my domain, nothing to do with me). I have checked my forwarders in named.conf, and none of them match the IPs showing in the logs (they are all basically different IPs, not just 193.95.142.60). My iptables reads: Chain INPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere REJECT all -- anywhere loopback/8 reject-with icmp-port-unreachable ACCEPT all -- anywhere anywhere state RELATED,ESTABLISHED ACCEPT tcp -- anywhere anywhere tcp dpt:http ACCEPT tcp -- anywhere anywhere tcp dpt:https ACCEPT tcp -- anywhere anywhere state NEW tcp dpt:ssh ACCEPT udp -- anywhere anywhere udp dpt:domain ACCEPT tcp -- anywhere anywhere tcp dpt:domain ACCEPT icmp -- anywhere anywhere icmp echo-request LOG all -- anywhere anywhere limit: avg 5/min burst 5 LOG level debug prefix "iptables denied: " REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain FORWARD (policy ACCEPT) target prot opt source destination REJECT all -- anywhere anywhere reject-with icmp-port-unreachable Chain OUTPUT (policy ACCEPT) target prot opt source destination ACCEPT all -- anywhere anywhere UPDATE: I've tried the following now in named.conf.options to block recursion. allow-transfer {"none";}; allow-recursion {"none";}; recursion no; Once I did this, I am now seeing the following in sy
] [ subject ] [ author ] There's more: both ns1.netbcp.com and ns2.netbcp.net don't respond to queries about nbc.com and ns1.netbcp.com doesn't respond over TCP. Frank From: bind-users-bounces+frnkblk=iname.com https://lists.isc.org/pipermail/bind-users/2012-October/088831.html at lists.isc.org [mailto:bind-users-bounces+frnkblk=iname.com at lists.isc.org] On Behalf Of Kevin Darcy Sent: Friday, October https://www.howtoforge.com/community/threads/named-logs-rcode-refuse.12920/ 12, 2012 12:48 PM Cc: bind-users at lists.isc.org Subject: Re: error (unexpected RCODE REFUSED) resolving OK, so your nbc.com/A resolving error doesn't really have anything to do with the nameservers you included in your original post. It does appear, however, that ns2.netbcp.net (205.173.93.213) is refusing requests generally for the nbc.com domain: unexpected rcode $ dig nbc.com +buf=4096 +norec @ns2.netbcp.net ; <<>> DiG 9.4.3-P3 <<>> nbc.com +buf=4096 +norec @ns2.netbcp.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 1019 ;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;nbc.com. IN A ;; Query time: 30 msec ;; SERVER: error unexpected rcode 205.173.93.213#53(205.173.93.213) ;; WHEN: Fri Oct 12 13:44:56 2012 ;; MSG SIZE rcvd: 36 ns1.netbcp.com appears to be doing the same thing. Not known whether this is something temporary (performing maintenance?), or something permanent (provider's contract lapsed, but customer never updated delegations). In any case, you have enough working authoritative nameservers for the domain, so it'll continue to resolve for you... - Kevin On 10/12/2012 1:35 PM, James Tingler wrote: I don't think that I am. I only define internal forwarders for internal zones as needed. For my root hint, standard configuration: Named.conf zone "." { type hint; file "named.ca"; Named.ca: ; <<>> DiG 9.5.0b2 <<>> +bufsize=1200 +norec NS . @a.root-servers.net ;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 34420 ;; flags: qr aa; QUERY: 1, ANSWER: 13, AUTHORITY: 0, ADDITIONAL: 20 ;; OPT PSEUDOSECTION: ; EDNS: version: 0, flags:; udp: 4096 ;; QUESTION SECTION: ;. IN NS ;; ANSWER SECTION: . 518400 IN NS M.ROOT-SERVERS.NET. . 518400 IN NS A.ROOT-SERVERS.NET. . 518400 IN NS B.ROOT-SERVERS.NET. . 518400 IN NS C.ROOT-SERVERS.NET. . 518400 IN NS D.ROOT-SERVERS.NET. . 518400 IN NS E.ROOT-SERVERS.NET. . 518400 IN NS F.ROOT-SERVERS
knows something about this entries in named logs. what's that? May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53 May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53 May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53 May 23 04:00:03 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53 May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53 May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53 May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.236.201#53 May 23 04:00:04 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving '101.192.124.74.in-addr.arpa/PTR/IN': 205.134.237.222#53 May 23 04:01:08 ns24815 named[6784]: unexpected RCODE (REFUSED) resolving 'dns2.xm.fj.cn/A/IN': 202.101.103.55#53 lots of this entries ... lyndros, May 25, 2007 #1 till Super Moderator Staff Member ISPConfig Developer Did you configure any forwarding nameserver that do not accept your queries? http://groups.google.com/group/comp...read/thread/ae7ff42f8de6add5/41dec870376e7667 till, May 25, 2007 #2 lyndros New Member till said: Did you configure any forwarding nameserver that do not accept your queries? http://groups.google.com/group/comp...read/thread/ae7ff42f8de6add5/41dec870376e7667Click to expand... no forwarders in my named.conf ... i tried to setup allow recursion for ns1 & ns2... but with the same result any idea? thks in advanced lyndros, May 25, 2007 #3 falko Super Moderator ISPConfig Developer What's in your named.conf? falko, May 26, 2007 #4 lyndros New Member falko said: What's in your named.conf?Click to expand... here we go: o