Problème Bind: error (network unreachable) resolving

WRInaute impliqué
Bonjour,

J'ai des soucis DNS sur mon serveur dédié Linux (Bin9). Les logs syslog et dameon sont remplis de:


Jan 27 19:37:41 de929 named[14354]: error (network unreachable) resolving 'B.ROOT-SERVERS.NET/AAAA/IN': 2001:500:2f::f#53
Jan 27 19:37:41 de929 named[10820]: error (network unreachable) resolving 'fb.mail.gandi.net/A/IN': 2001:dc3::35#53
Jan 27 19:37:41 de929 named[10820]: error (network unreachable) resolving 'symailserver.hsbc.co.uk/A/IN': 2001:503:c27::2:30#53
Jan 27 19:37:41 de929 named[10820]: error (network unreachable) resolving 'symailserver.hsbc.co.uk/A/IN': 2001:dc3::35#53
Jan 27 19:37:41 de929 named[10820]: error (network unreachable) resolving 'symailserver.hsbc.co.uk/A/IN': 2001:500:1::803f:235#53
Jan 27 19:37:41 de929 named[14354]: error (network unreachable) resolving 'email-cible.net/MX/IN': 2001:503:c27::2:30#53
Jan 27 19:37:41 de929 named[14354]: error (network unreachable) resolving 'email-cible.net/MX/IN': 2001:500:3::42#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'sfr.fr/MX/IN': 2001:503:c27::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'sfr.fr/MX/IN': 2001:500:3::42#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'mta.numericable.fr/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'a10.altospam.com/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'mx1.free.fr/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'mx.mailbox.orange-business.com/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'smtp-in.sfr.fr/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'ubest1.com/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'mail.promod.fr/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'mx1.premium.jfg-networks.net/A/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'vos-sources.com/MX/IN': 2001:503:ba3e::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'sanofi-aventis.com/MX/IN': 2001:503:c27::2:30#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'promod.fr/MX/IN': 2001:500:3::42#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'D.ROOT-SERVERS.NET/AAAA/IN': 2001:7fd::1#53
Jan 27 19:37:42 de929 named[14354]: error (network unreachable) resolving 'rocketmail.com/MX/IN': 2001:500:3::42#53

Récemment 2 ips ont été attribuées au serveur et l'ip d'origine n'est plus disponible (nullroutée suite à une attaque DDOS). Est ce le problème? Comme réattribuer la nouvelle adresse?

Merci
 
WRInaute passionné
Là je pense que c'est simplement ton bind qui est configuré pour utiliser l'IPv6 sans en avoir:
listen-on-v6 { none;};

Avec ça (named.conf.options) ça devrait le faire.
 
WRInaute impliqué
Bonjour julia41,

Non, c'est bon, on m'a aidé: c'était un problème de routage de la nouvelle ip vers l'ancienne...
 
Discussions similaires
Haut