Contenu | Rechercher | Menus

Annonce

Si vous avez des soucis pour rester connecté, déconnectez-vous puis reconnectez-vous depuis ce lien en cochant la case
Me connecter automatiquement lors de mes prochaines visites.

À propos de l'équipe du forum.

#1 Le 16/03/2014, à 18:17

jean-luc5629

Bind sur serveur kimsufi

Bonjour;
J'espère être dans le bon topic!!!

En vérifiant mes logs (syslog), il est rempli avec ça :

Mar 16 17:30:39 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:30:40 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:30:40 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:31:43 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:31:44 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:31:45 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:31:46 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:32:48 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:32:49 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:32:50 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:32:51 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:34:04 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:34:04 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:34:05 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:34:06 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:35:09 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:35:10 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:35:11 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:35:12 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:36:15 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:36:16 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:36:16 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:36:17 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:37:20 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:37:21 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:37:21 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:37:22 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:38:25 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:38:26 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:38:27 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:38:28 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:39:31 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:39:32 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:39:33 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:39:33 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:40:36 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:40:37 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:40:38 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53
Mar 16 17:40:39 jean-luc named[2063]: error (unexpected RCODE SERVFAIL) resolving '31.30.245.172.in-addr.arpa/PTR/IN': 199.21.112.12#53

Pourtant bind pré-installé chez ovh répond bien, je fais un dig google.com...il me sort tout ce qu'il faut
Si quelqu'un à une explication.
Merci.

Dernière modification par jean-luc5629 (Le 16/03/2014, à 18:17)

Hors ligne

#2 Le 17/03/2014, à 12:20

bruno

Re : Bind sur serveur kimsufi

Bonjour,

Bind échoue à faire la résolution inverse de 172.245.30.31. Est-ce un problème ?

En ligne

#3 Le 17/03/2014, à 17:51

jean-luc5629

Re : Bind sur serveur kimsufi

bruno a écrit :

Bonjour,

Bind échoue à faire la résolution inverse de 172.245.30.31. Est-ce un problème ?

Bonjour;
Non, et visiblement cette ip ne me dit rien.
Sur le site http://www.hcidata.info/host2ip.cgi j'obtiens ça :

Details of 172.245.30.31

IP Address : 172.245.30.31

Location   : Unknown

Host Name  : Unable to contact the host at IP Address 172.245.30.31

Merci.

Hors ligne