Jun 26 04:01:38 server1 named[12646]: lame server resolving '90.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:38 server1 named[12646]: lame server resolving '90.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:39 server1 named[12646]: lame server resolving '89.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:39 server1 named[12646]: lame server resolving '89.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:39 server1 named[12646]: lame server resolving '89.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '89.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '88.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '88.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '90.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '88.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '90.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '88.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:40 server1 named[12646]: lame server resolving '87.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.253.12#53
Jun 26 04:01:41 server1 named[12646]: lame server resolving '86.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
Jun 26 04:01:41 server1 named[12646]: lame server resolving '87.82.180.66.in-addr.arpa' (in '82.180.66.in-addr.arpa'?): 66.35.255.12#53
named[12646]: lame server resolving ... was bedeutet lame server?
named[12646]: lame server resolving ... was bedeutet lame server?
Kann mir jemand verraten was diese Einträge bedeuten? Ich finde so etwas recht unregelmäßig im syslog.
Re: named[12646]: lame server resolving ... was bedeutet lame server?
Lame Server beudetet, das dieser Server zwar als NS für eine bestimmte Domain eingetragen ist, diese auf ihm jedoch nicht konfiguriert/aktiviert ist.
Solche Meldungen kannst du getrost ignorieren.
Solche Meldungen kannst du getrost ignorieren.