Logwatch, named

Le
Nicolas Roudninski
--=_02f75e93c1ed1f4f1942371923ee510a
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8



Bonjour,

Je loue depuis quelques années un serveur kimsufi chez
OVH. Ce serveur me sert de serveur imap et smtp, de sauvegarde et de
blog.

Je me pose quelques questions quant aux logs générés par
logwatch. Depuis longtemps j'ai ces logs (Cf. plus bas).

Quelqu'un
pourrait-il m'expliquer ce qu'ils signifient ? Est-ce grave, dangereux ?


Cordialement,

Named Begin


**Unmatched Entries**
connection refused
resolving '100.75.195.82.sa-accredit.habeas.com/A/IN': 94.76.206.138#53:
3 Time(s)
success resolving '100.64/26.75.195.82.in-addr.arpa/PTR' (in
'64/26.75.195.82.in-addr.arpa'?) after reducing the advertised EDNS UDP
packet size to 512 octets: 2 Time(s)
success resolving
'100.75.195.82.dnsbl.sorbs.net/A' (in 'dnsbl.sorbs.net'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving '125.242.12.80.zen.spamhaus.org/A' (in 'zen.spamhaus.org'?)
after disabling EDNS: 1 Time(s)
success resolving
'137.208.74.193.sbl.spamhaus.org/TXT' (in 'sbl.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'154.216.134.83.zen.spamhaus.org/A' (in 'zen.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'175.82.125.74.zen.spamhaus.org/A' (in 'zen.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'217.80.83.210.sbl.spamhaus.org/TXT' (in 'sbl.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'239.59.191.119.sbl.spamhaus.org/TXT' (in 'sbl.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'251.61.186.213.in-addr.arpa/PTR' (in '61.186.213.in-addr.arpa'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)

success resolving '28.71.74.193.zen.spamhaus.org/A' (in
'zen.spamhaus.org'?) after disabling EDNS: 1 Time(s)
success resolving
'53.208.74.193.sbl.spamhaus.org/TXT' (in 'sbl.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'53.224.204.213.sbl.spamhaus.org/TXT' (in 'sbl.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'89.180.16.90.zen.spamhaus.org/A' (in 'zen.spamhaus.org'?) after
disabling EDNS: 1 Time(s)
success resolving
'auth21.ns.gin.ntt.net/AAAA' (in 'ntt.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'auth22.ns.gin.ntt.net/A' (in 'ntt.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'auth24.ns.gin.ntt.net/A' (in 'ntt.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'auth25.ns.gin.ntt.net/A' (in 'ntt.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'auth25.ns.gin.ntt.net/AAAA' (in 'ntt.net'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'battlestar.sorbs.net/AAAA' (in 'sorbs.net'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'c.nic.fr/A' (in 'nic.fr'?) after reducing the advertised EDNS
UDP packet size to 512 octets: 1 Time(s)
success resolving
'comcast.net/NS' (in 'comcast.net'?) after reducing the advertised EDNS
UDP packet size to 512 octets: 1 Time(s)
success resolving
'd.nic.fr/AAAA' (in 'nic.fr'?) after reducing the advertised EDNS UDP
packet size to 512 octets: 1 Time(s)
success resolving
'dns10.ovh.net/AAAA' (in 'ovh.net'?) after disabling EDNS: 1 Time(s)

success resolving 'dns11.ovh.net/A' (in 'ovh.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'f.ext.nic.fr/A' (in 'nic.fr'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'g.ext.nic.fr/A' (in 'nic.fr'?) after reducing the advertised EDNS UDP
packet size to 512 octets: 1 Time(s)
success resolving
'g.ext.nic.fr/AAAA' (in 'nic.fr'?) after reducing the advertised EDNS
UDP packet size to 512 octets: 1 Time(s)
success resolving
'ns-gmx.ui-dns.biz/AAAA' (in 'ui-dns.biz'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns.dns-oarc.net/AAAA' (in 'dns-oarc.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns.pobox.fi/A' (in 'pobox.fi'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'ns1.ams1.afilias-nst.info/AAAA' (in 'afilias-nst.info'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns1.hkg1.afilias-nst.info/A' (in 'afilias-nst.info'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)

success resolving 'ns1.hkg1.afilias-nst.info/AAAA' (in
'afilias-nst.info'?) after reducing the advertised EDNS UDP packet size
to 512 octets: 1 Time(s)
success resolving
'ns1.mia1.afilias-nst.info/AAAA' (in 'afilias-nst.info'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns1.surfnet.nl/A' (in 'surfnet.nl'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns1.surfnet.nl/AAAA' (in 'surfnet.nl'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns1.yyz1.afilias-nst.info/A' (in 'afilias-nst.info'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 2 Time(s)

success resolving 'ns10.ovh.net/A' (in 'ovh.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns2.bogurentod.com.ua/A' (in 'bogurentod.com.ua'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)

success resolving 'ns2.prosupersite.ru/AAAA' (in 'prosupersite.ru'?)
after reducing the advertised EDNS UDP packet size to 512 octets: 1
Time(s)
success resolving 'ns2.surfnet.nl/A' (in 'surfnet.nl'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)

success resolving 'ns2.surfnet.nl/AAAA' (in 'surfnet.nl'?) after
reducing the advertised EDNS UDP packet size to 512 octets: 2 Time(s)

success resolving 'ns20.ja.net/A' (in 'ja.net'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns3.bogurentod.com.ua/A' (in 'bogurentod.com.ua'?) after
disabling EDNS: 1 Time(s)
success resolving
'ns3.bogurentod.com.ua/AAAA' (in 'bogurentod.com.ua'?) after reducing
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success
resolving 'ns3.surfnet.nl/A' (in 'surfnet.nl'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 2 Time(s)
success
resolving 'ns4.nic.nl/AAAA' (in 'nl'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'ns5.facebook.com/A' (in 'facebook.com'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'ns5.sorbs.net/A' (in 'sorbs.net'?) after reducing the advertised EDNS
UDP packet size to 512 octets: 1 Time(s)
success resolving
'ns6.sorbs.net/AAAA' (in 'sorbs.net'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'nsa.schlund.de/AAAA' (in 'schlund.de'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'ord.sns-pb.isc.org/A' (in 'isc.org'?) after reducing the advertised
EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving
'screc.fr/NS' (in 'screc.fr'?) after disabling EDNS: 1 Time(s)
success
resolving 'tracker.t411.me/A' (in 't411.me'?) after reducing the
advertised EDNS UDP packet size to 512 octets: 4 Time(s)


- Named End -

--
Nicolas
Roudninski
nicolas@tycho.fr

S'il vous plaît, évitez de m'envoyer des
pièces jointes au format Word ou PowerPoint.
Voir
http://www.gnu.org/philosophy/no-word-attachments.fr.html

--=_02f75e93c1ed1f4f1942371923ee510a
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN">
<html><body>
<p>Bonjour,</p>
<p>Je loue depuis quelques ann&eacute;es un serveur kimsufi chez OVH. Ce se=
rveur me sert de serveur imap et smtp, de sauvegarde et de blog.</p>
<p>Je me pose quelques questions quant aux logs g&eacute;n&eacute;r&eacute;=
s par logwatch. Depuis longtemps j'ai ces logs (Cf. plus bas).</p>
<p>Quelqu'un pourrait-il m'expliquer ce qu'ils signifient ? Est-ce grave, d=
angereux ?</p>
<p>&nbsp;</p>
<p>Cordialement,</p>
<div>
<pre>&nbsp;</pre>
<pre>&nbsp;</pre>
<pre> Named Begin


**Unmatched Entries**
connection refused resolving '100.75.195.82.sa-accredit.habeas.com/A/IN=
': 94.76.206.138#53: 3 Time(s)
success resolving '100.64/26.75.195.82.in-addr.arpa/PTR' (in '64/26.75=
.195.82.in-addr.arpa'?) after reducing the advertised EDNS UDP packet siz=
e to 512 octets: 2 Time(s)
success resolving '100.75.195.82.dnsbl.sorbs.net/A' (in 'dnsbl.sorbs.ne=
t'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Ti=
me(s)
success resolving '125.242.12.80.zen.spamhaus.org/A' (in 'zen.spamhaus=
.org'?) after disabling EDNS: 1 Time(s)
success resolving '137.208.74.193.sbl.spamhaus.org/TXT' (in 'sbl.spamha=
us.org'?) after disabling EDNS: 1 Time(s)
success resolving '154.216.134.83.zen.spamhaus.org/A' (in 'zen.spamhaus=
.org'?) after disabling EDNS: 1 Time(s)
success resolving '175.82.125.74.zen.spamhaus.org/A' (in 'zen.spamhaus=
.org'?) after disabling EDNS: 1 Time(s)
success resolving '217.80.83.210.sbl.spamhaus.org/TXT' (in 'sbl.spamhau=
s.org'?) after disabling EDNS: 1 Time(s)
success resolving '239.59.191.119.sbl.spamhaus.org/TXT' (in 'sbl.spamha=
us.org'?) after disabling EDNS: 1 Time(s)
success resolving '251.61.186.213.in-addr.arpa/PTR' (in '61.186.213.in-=
addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octe=
ts: 1 Time(s)
success resolving '28.71.74.193.zen.spamhaus.org/A' (in 'zen.spamhaus=
.org'?) after disabling EDNS: 1 Time(s)
success resolving '53.208.74.193.sbl.spamhaus.org/TXT' (in 'sbl.spamhau=
s.org'?) after disabling EDNS: 1 Time(s)
success resolving '53.224.204.213.sbl.spamhaus.org/TXT' (in 'sbl.spamha=
us.org'?) after disabling EDNS: 1 Time(s)
success resolving '89.180.16.90.zen.spamhaus.org/A' (in 'zen.spamhaus=
.org'?) after disabling EDNS: 1 Time(s)
success resolving 'auth21.ns.gin.ntt.net/AAAA' (in 'ntt.net'?) after re=
ducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'auth22.ns.gin.ntt.net/A' (in 'ntt.net'?) after reduc=
ing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'auth24.ns.gin.ntt.net/A' (in 'ntt.net'?) after reduc=
ing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'auth25.ns.gin.ntt.net/A' (in 'ntt.net'?) after reduc=
ing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'auth25.ns.gin.ntt.net/AAAA' (in 'ntt.net'?) after re=
ducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'battlestar.sorbs.net/AAAA' (in 'sorbs.net'?) after r=
educing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'c.nic.fr/A' (in 'nic.fr'?) after reducing the advert=
ised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'comcast.net/NS' (in 'comcast.net'?) after reducing t=
he advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'd.nic.fr/AAAA' (in 'nic.fr'?) after reducing the adv=
ertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'dns10.ovh.net/AAAA' (in 'ovh.net'?) after disabling =
EDNS: 1 Time(s)
success resolving 'dns11.ovh.net/A' (in 'ovh.net'?) after reducing the =
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'f.ext.nic.fr/A' (in 'nic.fr'?) after reducing the ad=
vertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'g.ext.nic.fr/A' (in 'nic.fr'?) after reducing the ad=
vertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'g.ext.nic.fr/AAAA' (in 'nic.fr'?) after reducing the=
advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns-gmx.ui-dns.biz/AAAA' (in 'ui-dns.biz'?) after red=
ucing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns.dns-oarc.net/AAAA' (in 'dns-oarc.net'?) after red=
ucing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns.pobox.fi/A' (in 'pobox.fi'?) after reducing the a=
dvertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns1.ams1.afilias-nst.info/AAAA' (in 'afilias-nst.inf=
o'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Ti=
me(s)
success resolving 'ns1.hkg1.afilias-nst.info/A' (in 'afilias-nst.info'?=
) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(=
s)
success resolving 'ns1.hkg1.afilias-nst.info/AAAA' (in 'afilias-nst.inf=
o'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Ti=
me(s)
success resolving 'ns1.mia1.afilias-nst.info/AAAA' (in 'afilias-nst.inf=
o'?) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Ti=
me(s)
success resolving 'ns1.surfnet.nl/A' (in 'surfnet.nl'?) after reducing =
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns1.surfnet.nl/AAAA' (in 'surfnet.nl'?) after reduci=
ng the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns1.yyz1.afilias-nst.info/A' (in 'afilias-nst.info'?=
) after reducing the advertised EDNS UDP packet size to 512 octets: 2 Time(=
s)
success resolving 'ns10.ovh.net/A' (in 'ovh.net'?) after reducing the a=
dvertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns2.bogurentod.com.ua/A' (in 'bogurentod.com.ua'?) a=
fter reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns2.prosupersite.ru/AAAA' (in 'prosupersite.ru'?) af=
ter reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns2.surfnet.nl/A' (in 'surfnet.nl'?) after reducing =
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns2.surfnet.nl/AAAA' (in 'surfnet.nl'?) after reduci=
ng the advertised EDNS UDP packet size to 512 octets: 2 Time(s)
success resolving 'ns20.ja.net/A' (in 'ja.net'?) after reducing the adv=
ertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns3.bogurentod.com.ua/A' (in 'bogurentod.com.ua'?) a=
fter disabling EDNS: 1 Time(s)
success resolving 'ns3.bogurentod.com.ua/AAAA' (in 'bogurentod.com.ua'?=
) after reducing the advertised EDNS UDP packet size to 512 octets: 1 Time(=
s)
success resolving 'ns3.surfnet.nl/A' (in 'surfnet.nl'?) after reducing =
the advertised EDNS UDP packet size to 512 octets: 2 Time(s)
success resolving 'ns4.nic.nl/AAAA' (in 'nl'?) after reducing the adver=
tised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns5.facebook.com/A' (in 'facebook.com'?) after reduc=
ing the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns5.sorbs.net/A' (in 'sorbs.net'?) after reducing th=
e advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ns6.sorbs.net/AAAA' (in 'sorbs.net'?) after reducing=
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'nsa.schlund.de/AAAA' (in 'schlund.de'?) after reduci=
ng the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'ord.sns-pb.isc.org/A' (in 'isc.org'?) after reducing=
the advertised EDNS UDP packet size to 512 octets: 1 Time(s)
success resolving 'screc.fr/NS' (in 'screc.fr'?) after disabling EDNS: =
1 Time(s)
success resolving 'tracker.t411.me/A' (in 't411.me'?) after reducing th=
e advertised EDNS UDP packet size to 512 octets: 4 Time(s)

- Named End - </pre>
<pre>&nbsp;</pre>
<pre>--
Nicolas Roudninski
nicolas@tycho.fr

S'il vous pla&icirc;t, &eacute;vitez de m'envoyer des pi&egrave;ces jointes=
au format Word ou PowerPoint.
Voir http://www.gnu.org/philosophy/no-word-attachments.fr.html</pre>
</div>
</body></html>

--=_02f75e93c1ed1f4f1942371923ee510a--

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers debian-user-french-REQUEST@lists.debian.org
En cas de soucis, contactez EN ANGLAIS listmaster@lists.debian.org
Archive: http://lists.debian.org/aac047a484d7601f21b2e3147ab601bc@tycho.fr
Vidéos High-Tech et Jeu Vidéo
Téléchargements
Vos réponses
Gagnez chaque mois un abonnement Premium avec GNT : Inscrivez-vous !
Trier par : date / pertinence
jacques
Le #23905931
Le 26/10/2011 12:29, Nicolas Roudninski a écrit :
Bonjour,

Je loue depuis quelques années un serveur kimsufi chez OVH. Ce serveur
me sert de serveur imap et smtp, de sauvegarde et de blog.

Je me pose quelques questions quant aux logs générés par logwatch.
Depuis longtemps j'ai ces logs (Cf. plus bas).

Quelqu'un pourrait-il m'expliquer ce qu'ils signifient ? Est-ce grave,
dangereux ?



Pas dangereux.

Ces messages sont dûs à des serveurs distants mal configurés ou des
routeurs qui filtrent un peu fort sur le chemin. En tous cas aucune
action de correction possible de ta part.


Si tu as accès à named.conf tu peux placer

category lame-servers { null; };
category resolver { null; };
category edns-disabled { null; };
category query-errors { null; };

dans la section logging

connection refused resolving '100.75.195.82.sa-accredit.habeas.com/A/IN': 94.76.206.138#53: 3 Time(s)
success resolving '100.64/26.75.195.82.in-addr.arpa/PTR' (in '64/26.75.195.82.in-addr.arpa'?) after reducing the advertised EDNS UDP packet size to 512 octets: 2 Time(s)




J.

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: http://lists.debian.org/
Nicolas Roudninski
Le #23906121
--=_8afcfc318ade150f1bd29dca30a92d3c
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8



Le 26.10.2011 13:53, jacques a écrit :

Le 26/10/2011 12:29,


Nicolas Roudninski a écrit :

Bonjour, Je loue depuis quelques




années un serveur kimsufi chez OVH. Ce serveur me sert de serveur imap
et smtp, de sauvegarde et de blog. Je me pose quelques questions quant
aux logs générés par logwatch. Depuis longtemps j'ai ces logs (Cf. plus
bas). Quelqu'un pourrait-il m'expliquer ce qu'ils signifient ? Est-ce
grave, dangereux ?

Pas dangereux.

Ces messages sont dûs à des


serveurs distants mal configurés ou des
routeurs qui filtrent un peu


fort sur le chemin. En tous cas aucune
action de correction possible


de ta part.

Si tu as accès à named.conf tu peux placer




category lame-servers { null; };
category resolver { null; };



category edns-disabled { null; };
category query-errors { null; };


dans la section logging

connection refused resolving




'100.75.195.82.sa-accredit.habeas.com/A/IN': 94.76.206.138#53: 3 Time(s)
success resolving '100.64/26.75.195.82.in-addr.arpa/PTR' (in
'64/26.75.195.82.in-addr.arpa'?) after reducing the advertised EDNS UDP
packet size to 512 octets: 2 Time(s)

J.



Merci pour la réponse
rapide et rassurante.

Par named.conf tu entends /etc/bind/named.conf ?
(je n'ai que ça) Dedans il n'y a pas de section logging...

--
Nicolas
Roudninski


S'il vous plaît, évitez de m'envoyer des
pièces jointes au format Word ou PowerPoint.
Voir
http://www.gnu.org/philosophy/no-word-attachments.fr.html

--=_8afcfc318ade150f1bd29dca30a92d3c
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><body>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2p x solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignore d --><!-- meta ignored -->
<pre>Le 26/10/2011 12:29, Nicolas Roudninski a &eacute;crit :</pre>
<pre>Pas dangereux.

Ces messages sont d&ucirc;s &agrave; des serveurs distants mal configur&eac ute;s ou des
routeurs qui filtrent un peu fort sur le chemin. En tous cas aucune
action de correction possible de ta part.


Si tu as acc&egrave;s &agrave; named.conf tu peux placer

category lame-servers { null; };
category resolver { null; };
category edns-disabled { null; };
category query-errors { null; };

dans la section logging</pre>
<pre>
J.
</pre>
</blockquote>
<p>&nbsp;</p>
<div>
<pre>--
Nicolas Roudninski


S'il vous pla&icirc;t, &eacute;vitez de m'envoyer des pi&egrave;ces jointes au format Word ou PowerPoint.
Voir http://www.gnu.org/philosophy/no-word-attachments.fr.html</pre>
</div>
</body></html>

--=_8afcfc318ade150f1bd29dca30a92d3c--

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: http://lists.debian.org/
jacques
Le #23906181
Le 26/10/2011 14:43, Nicolas Roudninski a écrit :
Le 26.10.2011 13:53, jacques a écrit :

Le 26/10/2011 12:29, Nicolas Roudninski aécrit :
Bonjour, Je loue depuis quelques années un serveur kimsufi chez OVH.
Ce serveur me sert de serveur imap et smtp, de sauvegarde et de blog.
Je me pose quelques questions quant aux logs générés par logwatch.
Depuis longtemps j'ai ces logs (Cf. plus bas). Quelqu'un pourrait-il
m'expliquer ce qu'ils signifient ? Est-ce grave, dangereux ?


Pas dangereux.

Ces messages sont dûsà des serveurs distants mal configurés ou des
routeurs qui filtrent un peu fort sur le chemin. En tous cas aucune
action de correction possible de ta part.


Si tu as accèsà named.conf tu peux placer

category lame-servers { null; };
category resolver { null; };
category edns-disabled { null; };
category query-errors { null; };

dans la section logging
connection refused resolving
'100.75.195.82.sa-accredit.habeas.com/A/IN': 94.76.206.138#53: 3
Time(s) success resolving '100.64/26.75.195.82.in-addr.arpa/PTR' (in
'64/26.75.195.82.in-addr.arpa'?) after reducing the advertised EDNS
UDP packet size to 512 octets: 2 Time(s)


J.



Merci pour la réponse rapide et rassurante.

Par named.conf tu entends /etc/bind/named.conf ?



Oui,

(je n'ai que ça) Dedans
il n'y a pas de section logging...




logging {
category lame-servers { null; };
category resolver { null; };
category edns-disabled { null; };
category query-errors { null; };
};

Je pense que sa place ds le fichier importe peu ;
ici elle est placée avant les sections de zones.


J.

--
Pour passer au message suivant appuyez sur #

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: http://lists.debian.org/
Nicolas Roudninski
Le #23906391
--=_42d137a8252b8e3d0e8cbae6c5e6a280
Content-Transfer-Encoding: 8bit
Content-Type: text/plain; charset=UTF-8



Le 26.10.2011 15:25, jacques a écrit :

Le 26/10/2011 14:43,


Nicolas Roudninski a écrit :

Le 26.10.2011 13:53, jacques a écrit




:

Le 26/10/2011 12:29, Nicolas Roudninski aécrit :










Bonjour, Je loue depuis quelques années un serveur kimsufi chez OVH. Ce
serveur me sert de serveur imap et smtp, de sauvegarde et de blog. Je me
pose quelques questions quant aux logs générés par logwatch. Depuis
longtemps j'ai ces logs (Cf. plus bas). Quelqu'un pourrait-il
m'expliquer ce qu'ils signifient ? Est-ce grave, dangereux ?
Pas






dangereux. Ces messages sont dûsà des serveurs distants mal configurés
ou des routeurs qui filtrent un peu fort sur le chemin. En tous cas
aucune action de correction possible de ta part. Si tu as accèsà
named.conf tu peux placer category lame-servers { null; }; category
resolver { null; }; category edns-disabled { null; }; category
query-errors { null; }; dans la section logging

connection








refused resolving '100.75.195.82.sa-accredit.habeas.com/A/IN':
94.76.206.138#53: 3 Time(s) success resolving
'100.64/26.75.195.82.in-addr.arpa/PTR' (in
'64/26.75.195.82.in-addr.arpa'?) after reducing the advertised EDNS UDP
packet size to 512 octets: 2 Time(s)
J.


Merci pour la réponse




rapide et rassurante. Par named.conf tu entends /etc/bind/named.conf ?


Oui,

(je n'ai que ça) Dedans il n'y a pas de section




logging...

logging {
category lame-servers { null; };
category


resolver { null; };
category edns-disabled { null; };
category


query-errors { null; };
};

Je pense que sa place ds le fichier


importe peu ;
ici elle est placée avant les sections de zones.




J.

Ok, merci.

J'ai placé cette section après les sections zones et
avant la section include /etc/bind/named.conf.local on verra bien...


En tout cas merci bien.

--
Nicolas
Roudninski


S'il vous plaît, évitez de m'envoyer des
pièces jointes au format Word ou PowerPoint.
Voir
http://www.gnu.org/philosophy/no-word-attachments.fr.html

--=_42d137a8252b8e3d0e8cbae6c5e6a280
Content-Transfer-Encoding: quoted-printable
Content-Type: text/html; charset=UTF-8

<html><body>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2p x solid; margin-left:5px; width:100%"><!-- html ignored --><!-- head ignore d --><!-- meta ignored -->
<pre>Le 26/10/2011 14:43, Nicolas Roudninski a &eacute;crit :</pre>
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2p x solid; margin-left:5px; width:100%">Le 26.10.2011 13:53, jacques a &eacut e;crit :
<blockquote type="cite" style="padding-left:5px; border-left:#1010ff 2p x solid; margin-left:5px; width:100%">Le 26/10/2011 12:29, Nicolas Roudnins ki a&eacute;crit :
Pas dangereux. Ces messages sont d&ucirc;s&agrave; des serveurs distants ma l configur&eacute;s ou des routeurs qui filtrent un peu fort sur le chemin . En tous cas aucune action de correction possible de ta part. Si tu as a cc&egrave;s&agrave; named.conf tu peux placer category lame-servers { null; }; category resolver { null; }; category edns-disabled { null; }; category query-errors { null; }; dans la section logging
J.</blockquote>
Merci pour la r&eacute;ponse rapide et rassurante. Par named.conf tu entend s /etc/bind/named.conf ?</blockquote>
<pre>Oui,</pre>
<pre>
logging {
category lame-servers { null; };
category resolver { null; };
category edns-disabled { null; };
category query-errors { null; };
};

Je pense que sa place ds le fichier importe peu ;
ici elle est plac&eacute;e avant les sections de zones.


J.
<span class="sig"></span></pre>
</blockquote>
<p>&nbsp;</p>
<p>&nbsp;</p>
<div>
<pre>--
Nicolas Roudninski


S'il vous pla&icirc;t, &eacute;vitez de m'envoyer des pi&egrave;ces jointes au format Word ou PowerPoint.
Voir http://www.gnu.org/philosophy/no-word-attachments.fr.html</pre>
</div>
</body></html>

--=_42d137a8252b8e3d0e8cbae6c5e6a280--

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: http://lists.debian.org/
jacques
Le #23906671
Le 26/10/2011 16:27, Nicolas Roudninski a écrit :
Le 26.10.2011 15:25, jacques a écrit :

J'ai placé cette section après les sections zones et avant la section
include /etc/bind/named.conf.local on verra bien...



Il faudra redemarrer bind et regarder le log immédiatement après
pour voir si la chose râle...

Nicolas Roudninski


J.

--
Pour passer au message suivant appuyez sur #

--
Lisez la FAQ de la liste avant de poser une question :
http://wiki.debian.org/fr/FrenchLists

Pour vous DESABONNER, envoyez un message avec comme objet "unsubscribe"
vers
En cas de soucis, contactez EN ANGLAIS
Archive: http://lists.debian.org/
Publicité
Poster une réponse
Anonyme