Error (unexpected RCODE SERVFAIL) resolving

  • Autor Autor sulator
  • Fecha de inicio Fecha de inicio
S

sulator

Beta
¡Usuario con pocos negocios! ¡Utiliza siempre saldo de Forobeta!
Hola Betas,

editando el fichero log messages veo estos mensajes:

PHP: 
Feb  8 03:26:33 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '130.8.118.194.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  8 03:26:33 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '130.8.118.194.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  8 03:26:33 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'ENIAC.CABLE.NET.CO/AAAA/IN': 200.14.207.210#53
Feb  8 03:26:33 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'ENIAC.CABLE.NET.CO/A/IN': 200.14.207.210#53
Feb  8 03:26:34 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '228.77.165.83.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  8 03:26:34 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '228.77.165.83.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  8 03:26:35 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '190.12.225.77.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  8 03:26:35 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '190.12.225.77.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  8 03:26:36 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'CASTOR.ENTELCHILE.NET/A/IN': 200.31.96.18#53
Feb  8 03:26:37 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving 'DNS4.COTEA.COM.AR/A/IN': 186.148.120.2#53
Feb  8 03:26:37 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving 'DNS3.COTEA.COM.AR/AAAA/IN': 186.148.120.2#53
Feb  8 03:26:37 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving 'DNS3.COTEA.COM.AR/A/IN': 186.148.120.2#53
Feb  8 03:26:37 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving 'DNS4.COTEA.COM.AR/AAAA/IN': 186.148.120.2#53
Feb  8 03:26:38 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'jerry.upf.es/A/IN': 130.206.1.3#53
Feb  8 03:26:38 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'tom.upf.es/A/IN': 130.206.1.3#53
Feb  8 03:26:38 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'jerry.upf.es/AAAA/IN': 130.206.1.3#53
Feb  8 03:26:38 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving 'tom.upf.es/AAAA/IN': 130.206.1.3#53
Feb  8 03:26:39 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '168.107.27.77.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  8 03:26:40 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '34.220.227.77.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  8 03:26:40 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '195.4.130.79.in-addr.arpa/PTR/IN': 2001:67c:e0::5#53
Feb  8 03:26:40 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '166.234.60.181.in-addr.arpa/PTR/IN': 200.118.2.18#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '10.215.9.87.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '10.215.9.87.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '87.50.143.213.in-addr.arpa/PTR/IN': 85.62.233.129#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '86.50.143.213.in-addr.arpa/PTR/IN': 85.62.233.129#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '87.50.143.213.in-addr.arpa/PTR/IN': 85.62.229.137#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '86.50.143.213.in-addr.arpa/PTR/IN': 85.62.229.137#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE SERVFAIL) resolving '117.101.141.190.in-addr.arpa/PTR/IN': 200.75.200.3#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '87.50.143.213.in-addr.arpa/PTR/IN': 85.62.229.137#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '86.50.143.213.in-addr.arpa/PTR/IN': 85.62.229.137#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '87.50.143.213.in-addr.arpa/PTR/IN': 85.62.233.129#53
Feb  8 03:26:41 dedicado named[19105]: error (unexpected RCODE REFUSED) resolving '86.50.143.213.in-addr.arpa/PTR/IN': 85.62.233.129#53

Que significado tiene estos errores? por favor, alguien puede ayudarme gracias

saludos
 
Yo tambien buscando lo vi, en su día pero tampoco que diga mucha cosa como solucionarlo.
 
Hola sulator,

El error que le aparece dice que el DNS reverso o PTR no esta resolviendo. Lo mas seguro es que esta mal hecho los registros del DNS de los dominios que menciona. Tambien veo record A y AAAA que tambien son DNS. Intente revisar bien si estan apuntando a la IP correcta en el registrar de esos dominios.
 

Hola Julie, gracias por tu respuesta he estado revisando todo el tema dns y no encuentro el problema veo que esta todo normal.

Por cierto, hoy vuelven más mensajes prácticamente casi a la misma hora, puede ser algún tipo de ataque??? no se que puede ser más.


PHP: 
Feb  9 03:29:52 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '251.229.255.223.in-addr.arpa/PTR/IN': 180.214.233.96#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.59.41#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 198.41.222.173#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.58.51#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3b29#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::c629:dead#53
Feb  9 03:33:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3a33#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3b29#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 198.41.222.173#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.58.51#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.59.41#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::c629:dead#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3a33#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '195.89.249.218.in-addr.arpa/PTR/IN': 211.147.6.4#53
Feb  9 03:33:04 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '195.89.249.218.in-addr.arpa/PTR/IN': 211.147.6.3#53
Feb  9 03:33:05 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '195.89.249.218.in-addr.arpa/PTR/IN': 211.147.6.4#53
Feb  9 03:33:06 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '195.89.249.218.in-addr.arpa/PTR/IN': 211.147.6.3#53
Feb  9 03:33:07 dedicado named[883]: error (connection refused) resolving '254.0-255.16.28.8.in-addr.arpa/PTR/IN': 8.21.6.193#53
Feb  9 03:38:22 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '7.140.18.79.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:22 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '7.140.18.79.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  9 03:38:26 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '167.111.166.194.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:26 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '167.111.166.194.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  9 03:38:28 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '154.139.165.83.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '154.139.165.83.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '213.241.85.188.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '213.241.85.188.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '7.188.229.77.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '7.188.229.77.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '231.179.25.46.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb  9 03:38:29 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '242.112.0.192.in-addr.arpa/PTR/IN': 198.181.117.5#53
 

Rstos mensajes si los ves en el mail.log o cualquier log de el mail es normal asi que no te asustes compadre... Como te dijeron eso es que no rienen record PTR asi quw ni les hagas caso
 
Hola maxpaynecu,

Efectivamente PTR no las tengo asignada, lo curioso es que hoy también me aparecen nuevos registros prácticamente a la misma hora como todos los días. que raro, no?
de todas formas hay alguna manera de parar estos mensajes anularlos, en alguna configuración de la red? gracias

PHP: 
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 198.41.222.173#53
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3a33#53
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.59.41#53
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.58.51#53
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::c629:dead#53
Feb 10 03:40:01 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3b29#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '44.12.57.213.in-addr.arpa/PTR/IN': 193.0.9.5#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '44.12.57.213.in-addr.arpa/PTR/IN': 193.0.9.6#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.58.51#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::c629:dead#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 173.245.59.41#53
Feb 10 03:40:02 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3a33#53
Feb 10 03:40:03 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 198.41.222.173#53
Feb 10 03:40:03 dedicado named[883]: error (unexpected RCODE REFUSED) resolving '75.188.243.162.in-addr.arpa/PTR/IN': 2400:cb00:2049:1::adf5:3b29#53
Feb 10 03:40:03 dedicado named[883]: error (unexpected RCODE SERVFAIL) resolving '28.110.232.128.in-addr.arpa/PTR/IN': 2001:67c:e0::6#53
 

amigo el PTR no los asigna el dueno del servidor sino el ISP de donde provienen esas IP te lo digo por experiencia propia ...

eso lo que significa es cuando algun correo llega a tu server o algun clientre intenta conectarse tu servidor va a hacer la comprobacion de PTR y como no la encuentra pues da ese error los registros PTR si te fijas en google veras que no es mayor cosa asi que siga trabajando y olvidese de esos logs que si vieras el de mi server te quedas 😕😕😕
 
Hola sulator,

No se preocupe por los mensaje que esta viendo, solo son por el PTR o reverse DNS, si no estan asignados pues no hay de que preocuparse, solo es como advertencia.
 
Ok perfecto no le tomare cuenta a dichos mensajes, gracias por las respuestas 😉
 
Hay que estar conectado o registrado para responder aquí.
Menú
Acceder
Registro