Lame-servers Info Error Unexpected Rcode Servfail 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
Named Error (unexpected Rcode Refused) Resolving
end of the previous line : "xxx.xxx.xxx.xxx#53" and search this address in unexpected rcode (servfail) from master your named configuration file - it should be located inside the forwarders : Shell forwarders { xxx.xxx.xxx.xxx;
Category Lame-servers {null;};
}; 1 forwarders { 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 error (formerr) resolving this server if it 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! lame server resolving Tweet Category: Servers About Kaven G. System 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 : Change installation and boot video resolution on CentOS/RHEL 7 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 : Change installation and boot video resolution on CentOS/RHEL 7 IOS : Extended VLAN(s) not allowed in current VTP mode 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 Archives Archives Select Month October 2016 September 2016 August 2016 July 2016 June 2016 May 2016 April 2016 March 2016 February 2016 J
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
Rcode Refused Dns
company Business Learn more about hiring developers or posting ads with us Server Fault Questions dns lame server Tags Users Badges Unanswered Ask Question _ Server Fault is a question and answer site for system and network administrators. Join them;
Error (network Unreachable) Resolving
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
"error (unexpected RCODE REFUSED)" mean? Posted by Eric on 14 July 2015, 1:29 am If you're seeing this in the /var/log/syslog on your BIND DNS server: Jul 14 00:56:13 kla-dns-01 named[8255]: http://www.ericshalov.com/2015/07/14/what-does-error-unexpected-rcode-refused-mean/ error (unexpected RCODE REFUSED) resolving '75.1.33.112.in-addr.arpa/PTR/IN': 211.136.17.105#53 ..it means that a client has asked your server to look up a domain name that your server didn't know about, and when https://forums.gentoo.org/viewtopic-t-864023-start-25.html it forwarded the request to it's forwarders, the remote DNS server refused to respond. A packet trace on your DNS server shows exactly what's happening: root@dns1:/# tcpdump -n -s unexpected rcode 1514 -v 'port 53' tcpdump: listening on eth0, link-type EN10MB (Ethernet), capture size 1514 bytes 00:56:09.686771 IP (tos 0x0, ttl 62, id 44942, offset 0, flags [DF], proto UDP (17), length 70) 10.5.11.101.42237 > 10.0.10.10.53: 17985+ PTR? 75.1.33.112.in-addr.arpa. (42) ^… One of your clients sends a request to your DNS server asking for the reverse-IP request (a "PTR" request) lame-servers info error for the domain-name corresponding to IP address 112.33.1.75 (expressed in reverse as "75.1.33.112.in-addr.arpa.") 00:56:09.687284 IP (tos 0x0, ttl 64, id 28584, offset 0, flags [none], proto UDP (17), length 81) 10.0.10.10.6374 > 10.0.0.2.53: 26305+% [1au] PTR? 75.1.33.112.in-addr.arpa. (53) ^… The DNS server forwards the reverse-IP request to it's "upstream" forwarder DNS server, 10.0.0.2. 00:56:12.218438 IP (tos 0x0, ttl 64, id 39251, offset 0, flags [none], proto UDP (17), length 81) 10.0.10.10.27738 > 211.136.20.201.53: 63185% [1au] PTR? 75.1.33.112.in-addr.arpa. (53) ^… After 3 seconds without a reply, the server sends the request to it's next forwarder, 211.136.20.201. 00:56:13.018706 IP (tos 0x0, ttl 64, id 34335, offset 0, flags [none], proto UDP (17), length 81) 10.0.10.10.37801 > 211.136.17.105.53: 55483% [1au] PTR? 75.1.33.112.in-addr.arpa. (53) ^… 800ms later, the server repeats the request to it's forwarder, 211.136.17.105. 00:56:13.251686 IP (tos 0x4, ttl 53, id 48502, offset 0, flags [none], proto UDP (17), length 81) 211.136.17.105.53 > 10.0.10.10.37801: 55483 Refused- 0/0/1 (53) ^ … The "upstream" forwarder DNS responds with the answer it received, REFUSED! Your DNS server then logs this rejecti