Error Unexpected Rcode Refused Resolving A In
Contents |
"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]: error (unexpected RCODE named error unexpected rcode refused 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
Lame Servers Error Unexpected Rcode Refused
to look up a domain name that your server didn't know about, and when it forwarded the request error unexpected rcode servfail 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 1514 -v 'port 53' tcpdump: listening error 901 unexpected rcode 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) for the domain-name corresponding to IP address 112.33.1.75 (expressed in
Error (formerr) Resolving
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 rejection to syslog: Jul 14 00:56:13 kla-dns-01 named[8255]: error (unexpected RCODE REFUSED) resolving '75.1.33.112.in-addr.arpa/PTR/IN': 211.136.17.105#53 ^… The log says tha
Start here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss lame server resolving the workings and policies of this site About Us Learn more about rcode refused dns Stack Overflow the 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; it only takes a minute: Sign up http://www.ericshalov.com/2015/07/14/what-does-error-unexpected-rcode-refused-mean/ 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 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.). http://serverfault.com/questions/672566/unexpected-rcode-refused-eating-up-log-files 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 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
comentario Si mantenemos algun servidor DNS interno, puede que si nos vamos a mirar los logs de sistema, por ejemplo el daemon.log nos encontremos con alguno de estos errores producido desde el named: named[...]: unexpected RCODE (REFUSED) resolving '..':ipaddr#53 named[...]: https://rubenlacasa.es/2014/04/09/errores-en-bind-unexpected-rcode-refused-resolving/ unexpected RCODE (SERVFAIL) resolving '...': ipaddr#53 El primer error es debido a que https://lists.isc.org/pipermail/bind-users/2012-October/088831.html el servidor que estamos usando como forwarders en el fichero named.conf.options nos esta denegando las solicitudes por algun motivo, en mi caso estos errores me los estan devolviendo los servidores DNS de google tanto el 8.8.8.8 y el 8.8.4.4, luego el siguiente error es por que el servidor no contesta a nuestra petición. En ambos casos unexpected rcode la solución mas sencilla es eliminar esos servidores y configurar otros nuevos como forwarders. http://www.itechlounge.net/2011/12/bind-unexpected-rcode-refused-resolving-xx-xx-xx-xx-in-addr-arpaptrin/ Compartir:Comparte en Facebook (Se abre en una ventana nueva)Haz clic para compartir en Twitter (Se abre en una ventana nueva)Haz clic para compartir en Pinterest (Se abre en una ventana nueva)Haz clic para compartir en Pocket (Se abre en una ventana nueva)Haz clic aquí para compartir en LinkedIn (Se abre en una ventana nueva)Haz error unexpected rcode clic para compartir en Google+ (Se abre en una ventana nueva)Haz clic para compartir en Reddit (Se abre en una ventana nueva)MásClick to email (Se abre en una ventana nueva)Haz clic para imprimir (Se abre en una ventana nueva)Me gusta:Me gusta Cargando... Relacionado BindDNSRCODETecnología Navegador de artículos Entrada anteriorFunción para eliminar los espacios no deseados dentro de un textoPróximo entradaCrea libros de programación y ejercicios con GitBook Deja un comentario Cancelar respuesta Introduce aquí tu comentario... Introduce tus datos o haz clic en un icono para iniciar sesión: Correo electrónico (necesario) (La dirección no se hará pública) Nombre (necesario) Web Estás comentando usando tu cuenta de WordPress.com. (Cerrarsesión/Cambiar) Estás comentando usando tu cuenta de Twitter. (Cerrarsesión/Cambiar) Estás comentando usando tu cuenta de Facebook. (Cerrarsesión/Cambiar) Estás comentando usando tu cuenta de Google+. (Cerrarsesión/Cambiar) Cancelar Conectando a %s Notificarme los nuevos comentarios por correo electrónico. Follow rubenlacasa.es on WordPress.com Entradas recientes Detección de Genero con Gender API o Genderize.io SQL Server en Linux Uso de array_map para codificar los valores de un Array Comprobar si existe un elemento en un Array con jQuery Marcar multiples mensajes como no deseados Entradas mas vistas Como ver los tamaños de ficheros en KB, MB, GB - Linux Tips Selecc
] [ 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 at lists.isc.org [mailto:bind-users-bounces+frnkblk=iname.com at lists.isc.org] On Behalf Of Kevin Darcy Sent: Friday, October 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: $ 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: 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.NET. . 518400 IN NS G.ROOT-SERVERS.NET. . 518400 IN NS H.ROOT-SERVERS.NET. . 518400 IN NS I.ROOT-SERVERS.NET. . 518400 IN NS J.ROOT-SERVERS.NET. . 518400 IN NS K.ROOT-SERVERS.NET. . 518400 IN NS L.ROOT-SERVERS.NET. ;; ADDITIONAL SECT