der_angler
01.11.10, 00:05
Hallo,
ich habe meinen Server zuhause neu aufgesetzt und jetzt macht mein DNS-Server (bind) beim Systemstart und von Zeit zu Zeit auch so Probleme.
Folgende Fehlermeldung kommt beim Systemstart:
ov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.36.148.17#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.36.148.17#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.36.148.17#53
Nov 1 06:16:47 server kernel: [ 40.289075] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
und während der Server läuft, erscheint von Zeit zu Zeit folgende Fehlermeldung, aber immer mit der gleichen URL!
Oct 31 22:28:49 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:28:49 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:37 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:38 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:51 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:51 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:55 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:55 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:07 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:08 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:15 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:16 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:23 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:24 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Ansonsten scheint aber alles in Ordnung zu sein. Trotzdem stört mich das Verhalten und ich finde keine Antwort warum das so ist.
Meine named.conf sieht so aus:
options {
directory "/var/bind";
// uncomment the following lines to turn on DNS forwarding,
// and change the forwarding ip address(es) :
forwarders {217.237.150.51; 217.237.148.22;};
listen-on-v6 { none; };
listen-on { 192.168.16.1; 127.0.0.1; };
// to allow only specific hosts to use the DNS server:
//allow-query {
// 127.0.0.1;
//};
// if you have problems and are behind a firewall:
//query-source address * port 53;
pid-file "/var/run/named/named.pid";
};
// Briefly, a zone which has been declared delegation-only will be effectively
// limited to containing NS RRs for subdomains, but no actual data beyond its
// own apex (for example, its SOA RR and apex NS RRset). This can be used to
// filter out "wildcard" or "synthesized" data from NAT boxes or from
// authoritative name servers whose undelegated (in-zone) data is of no
// interest.
// See http://www.isc.org/products/BIND/delegation-only.html for more info
//zone "COM" { type delegation-only; };
//zone "NET" { type delegation-only; };
zone "." IN {
type hint;
file "named.cache";
};
zone "localhost" IN {
type master;
file "pri/localhost.zone";
allow-update { none; };
notify no;
};
zone "127.in-addr.arpa" IN {
type master;
file "pri/127.zone";
allow-update { none; };
notify no;
};
zone "home" {
type master;
file "/var/bind/home.hosts";
};
zone "16.168.192.in-addr.arpa" {
type master;
file "/var/bind/192.168.16.rev";
};
und meine beiden Zonefiles.
home.hosts
$ttl 120
@ IN SOA server root.server (
200210037
10800
3600
604800
86400
)
@ IN NS server
server IN A 192.168.16.1
multimedia IN A 192.168.16.1
datenbank IN A 192.168.16.1
netzwerk IN A 192.168.16.1
kraus-automaten IN A 192.168.16.1
trennwand-rink IN A 192.168.16.1
hpl-zuschnitt IN A 192.168.16.1
haus-hahn IN A 192.168.16.1
testserver IN A 192.168.16.1
192.168.16.rev
$ttl 120
@ IN SOA server.home. root.server.home. (
2002100318
28800
14400
3024000
38400
)
@ IN NS server.home.
1 IN PTR server.home.
1 IN PTR multimedia.home.
1 IN PTR datenbank.home.
1 IN PTR netzwerk.home.
1 IN PTR kraus-automaten.home.
1 IN PTR trennwand-rink.home.
1 IN PTR hpl-zuschnitt.home.
1 IN PTR haus-hahn.home.
1 IN PTR testserver.home.
Kann mir bitte jemand weiterhelfen?
ich habe meinen Server zuhause neu aufgesetzt und jetzt macht mein DNS-Server (bind) beim Systemstart und von Zeit zu Zeit auch so Probleme.
Folgende Fehlermeldung kommt beim Systemstart:
ov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.36.148.17#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving './NS/IN': 192.36.148.17#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.148.22#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 217.237.150.51#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.203.230.10#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.5.5.241#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 193.0.14.129#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 198.41.0.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.228.79.201#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.33.4.12#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.63.2.53#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 128.8.10.90#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.112.36.4#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.58.128.30#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 199.7.83.42#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 202.12.27.33#53
Nov 1 06:16:46 server named[3936]: network unreachable resolving 'api.nagios.org/A/IN': 192.36.148.17#53
Nov 1 06:16:47 server kernel: [ 40.289075] eth1: link up, 100Mbps, full-duplex, lpa 0x45E1
und während der Server läuft, erscheint von Zeit zu Zeit folgende Fehlermeldung, aber immer mit der gleichen URL!
Oct 31 22:28:49 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:28:49 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:37 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:38 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:51 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:51 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:29:55 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:29:55 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:07 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:08 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:15 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:16 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Oct 31 22:30:23 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 195.110.124.140#53
Oct 31 22:30:24 server named[3936]: unexpected RCODE (SERVFAIL) resolving 'smarking.com/A/IN': 213.92.11.34#53
Ansonsten scheint aber alles in Ordnung zu sein. Trotzdem stört mich das Verhalten und ich finde keine Antwort warum das so ist.
Meine named.conf sieht so aus:
options {
directory "/var/bind";
// uncomment the following lines to turn on DNS forwarding,
// and change the forwarding ip address(es) :
forwarders {217.237.150.51; 217.237.148.22;};
listen-on-v6 { none; };
listen-on { 192.168.16.1; 127.0.0.1; };
// to allow only specific hosts to use the DNS server:
//allow-query {
// 127.0.0.1;
//};
// if you have problems and are behind a firewall:
//query-source address * port 53;
pid-file "/var/run/named/named.pid";
};
// Briefly, a zone which has been declared delegation-only will be effectively
// limited to containing NS RRs for subdomains, but no actual data beyond its
// own apex (for example, its SOA RR and apex NS RRset). This can be used to
// filter out "wildcard" or "synthesized" data from NAT boxes or from
// authoritative name servers whose undelegated (in-zone) data is of no
// interest.
// See http://www.isc.org/products/BIND/delegation-only.html for more info
//zone "COM" { type delegation-only; };
//zone "NET" { type delegation-only; };
zone "." IN {
type hint;
file "named.cache";
};
zone "localhost" IN {
type master;
file "pri/localhost.zone";
allow-update { none; };
notify no;
};
zone "127.in-addr.arpa" IN {
type master;
file "pri/127.zone";
allow-update { none; };
notify no;
};
zone "home" {
type master;
file "/var/bind/home.hosts";
};
zone "16.168.192.in-addr.arpa" {
type master;
file "/var/bind/192.168.16.rev";
};
und meine beiden Zonefiles.
home.hosts
$ttl 120
@ IN SOA server root.server (
200210037
10800
3600
604800
86400
)
@ IN NS server
server IN A 192.168.16.1
multimedia IN A 192.168.16.1
datenbank IN A 192.168.16.1
netzwerk IN A 192.168.16.1
kraus-automaten IN A 192.168.16.1
trennwand-rink IN A 192.168.16.1
hpl-zuschnitt IN A 192.168.16.1
haus-hahn IN A 192.168.16.1
testserver IN A 192.168.16.1
192.168.16.rev
$ttl 120
@ IN SOA server.home. root.server.home. (
2002100318
28800
14400
3024000
38400
)
@ IN NS server.home.
1 IN PTR server.home.
1 IN PTR multimedia.home.
1 IN PTR datenbank.home.
1 IN PTR netzwerk.home.
1 IN PTR kraus-automaten.home.
1 IN PTR trennwand-rink.home.
1 IN PTR hpl-zuschnitt.home.
1 IN PTR haus-hahn.home.
1 IN PTR testserver.home.
Kann mir bitte jemand weiterhelfen?