bind: problem mit konfiguration?

Alle weiteren Dienste, die nicht in die drei oberen Foren gehören.
Antworten
init
Beiträge: 6
Registriert: 29.04.2005 11:45:29
Wohnort: Offenburg

bind: problem mit konfiguration?

Beitrag von init » 03.05.2005 11:36:43

Hi,
nachdem ich meinen dediziertern Server von Suse auf Debian umgestellt habe,
kriege ich Bind nicht mehr zur mitarbeit bewegt:

Zu dem vor der Umstellung gesicherten Zonenfile:

Code: Alles auswählen

$TTL 12h
gk-net.de. IN SOA ns1.gk-net.de. hostmaster.gk-net.de. (
        2002061311      ; Serial
        3h                    ; Refresh
        1h                    ; Retry
        1w                    ; Expire
        12h )                 ; Negative Caching-TTL

gk-net.de. IN NS ns1.gk-net.de.
gk-net.de. IN NS ns1.granitecanyon.com.
gk-net.de. IN NS ns2.granitecanyon.com.

gk-net.de.                   IN A    217.172.179.177
ns1.gk-net.de.             IN A    217.172.179.177
meint die Debugausgabe jetzt (Bind gestartet mit /usr/sbin/named -d 1):

Code: Alles auswählen

......
May 03 09:31:42.844 zone db.gk-net.de/IN: starting load
May 03 09:31:42.845 dns_master_load: db.gk-net.de:2: ignoring out-of-zone data (gk-net.de)
May 03 09:31:42.845 dns_master_load: db.gk-net.de:9: ignoring out-of-zone data (gk-net.de)
May 03 09:31:42.846 dns_master_load: db.gk-net.de:10: ignoring out-of-zone data (gk-net.de)
May 03 09:31:42.846 dns_master_load: db.gk-net.de:11: ignoring out-of-zone data (gk-net.de)
May 03 09:31:42.847 dns_master_load: db.gk-net.de:13: ignoring out-of-zone data (gk-net.de)
May 03 09:31:42.847 dns_master_load: db.gk-net.de:14: ignoring out-of-zone data (ns1.gk-net.de)
May 03 09:31:42.849 zone db.gk-net.de/IN: loaded
May 03 09:31:42.849 zone db.gk-net.de/IN: journal rollforward completed successfully: no journal
May 03 09:31:42.849 no_references: delete from rbt: 0x8095270 db.gk-net.de
May 03 09:31:42.849 zone db.gk-net.de/IN: could not find NS and/or SOA records
May 03 09:31:42.850 zone db.gk-net.de/IN: has 0 SOA records
May 03 09:31:42.850 zone db.gk-net.de/IN: has no NS records
.......
nun gut, vielleicht hat sich ja die Syntax mit verschiedenen Versionen irgendwie geändert, dachte ich. Nach reichlichem googeln, Foren lesen und ausprobieren hab ich
jetzt folgende Variante:

Code: Alles auswählen

$TTL 12h
@       IN      SOA     gk-net.de.      hostmaster.gk-net.de. (
        2005042913      ; Serial
        3h              ; Refresh
        1h              ; Retry
        1w              ; Expire
        12h )           ; Negative Caching-TTL
;
        IN NS   ns1
        IN NS   ns1.granitecanyon.com.
;
        IN A    217.172.179.177
Ein dig @localhost gk-net.de bringt mir aber trotzdem ein SERVFAIL :

Code: Alles auswählen

; <<>> DiG 9.2.1 <<>> @localhost gk-net.de
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 11434
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;gk-net.de.                     IN      A

;; Query time: 258 msec
;; SERVER: 127.0.0.1#53(localhost)
;; WHEN: Tue May  3 09:15:38 2005
;; MSG SIZE  rcvd: 27
----------------------------------------
( Ein mitlaufendes tail -f /var/log/daemon.log bringt zum Zeitpunkt der dig-Abfrage
mehrmals:
May 3 09:15:38 chicago177 named[505]: lame server resolving 'gk-net.de' (in 'gk-net.de'?): 69.67.108.10#53 )

Obwohl ich in der Debugausgabe von bind beim Start keinen Fehler mehr sehe:
/usr/sbin/named -d 1 mit der neuen Zone:

Code: Alles auswählen

May 03 09:19:52.206 starting BIND 9.2.1 -d 1
May 03 09:19:52.208 using 1 CPU
May 03 09:19:52.217 loading configuration from '/etc/bind/named.conf'
May 03 09:19:52.232 no IPv6 interfaces found
May 03 09:19:52.233 listening on IPv4 interface lo, 127.0.0.1#53
May 03 09:19:52.235 listening on IPv4 interface eth0, 217.172.179.177#53
May 03 09:19:52.244 command channel listening on 127.0.0.1#953
May 03 09:19:52.245 now using logging configuration from config file
May 03 09:19:52.246 load_configuration: success
May 03 09:19:52.246 zone 0.in-addr.arpa/IN: starting load
May 03 09:19:52.248 zone 0.in-addr.arpa/IN: loaded
May 03 09:19:52.249 zone 0.in-addr.arpa/IN: journal rollforward completed successfully: nojournal
May 03 09:19:52.249 zone 0.in-addr.arpa/IN: loaded serial 1
May 03 09:19:52.250 zone 127.in-addr.arpa/IN: starting load
May 03 09:19:52.252 zone 127.in-addr.arpa/IN: loaded
May 03 09:19:52.252 zone 127.in-addr.arpa/IN: journal rollforward completed successfully: no journal
May 03 09:19:52.253 zone 127.in-addr.arpa/IN: loaded serial 1
May 03 09:19:52.253 zone 177.179.172.217.in-addr.arpa/IN: starting load
May 03 09:19:52.255 zone 177.179.172.217.in-addr.arpa/IN: loaded
May 03 09:19:52.256 zone 177.179.172.217.in-addr.arpa/IN: journal rollforward completed successfully: no journal
May 03 09:19:52.256 zone 177.179.172.217.in-addr.arpa/IN: loaded serial 2002061310
May 03 09:19:52.256 zone 255.in-addr.arpa/IN: starting load
May 03 09:19:52.258 zone 255.in-addr.arpa/IN: loaded
May 03 09:19:52.259 zone 255.in-addr.arpa/IN: journal rollforward completed successfully: no journal
May 03 09:19:52.259 zone 255.in-addr.arpa/IN: loaded serial 1
May 03 09:19:52.259 zone db.gk-net.de/IN: starting load
May 03 09:19:52.262 zone db.gk-net.de/IN: loaded
May 03 09:19:52.262 zone db.gk-net.de/IN: journal rollforward completed successfully: no journal
May 03 09:19:52.262 zone db.gk-net.de/IN: loaded serial 2005042913
May 03 09:19:52.263 zone localhost/IN: starting load
May 03 09:19:52.265 zone localhost/IN: loaded
May 03 09:19:52.265 zone localhost/IN: journal rollforward completed successfully: no journal
May 03 09:19:52.265 zone localhost/IN: loaded serial 1
May 03 09:19:52.266 dns_zone_maintenance: zone localhost/IN: enter
May 03 09:19:52.266 dns_zone_maintenance: zone 127.in-addr.arpa/IN: enter
May 03 09:19:52.266 dns_zone_maintenance: zone 0.in-addr.arpa/IN: enter
May 03 09:19:52.266 dns_zone_maintenance: zone 255.in-addr.arpa/IN: enter
May 03 09:19:52.266 dns_zone_maintenance: zone db.gk-net.de/IN: enter
May 03 09:19:52.266 dns_zone_maintenance: zone 177.179.172.217.in-addr.arpa/IN: enter
May 03 09:19:52.267 dns_zone_maintenance: zone version.bind/CH: enter
May 03 09:19:52.267 running
May 03 09:19:52.267 zone_timer: zone 0.in-addr.arpa/IN: enter
May 03 09:19:52.267 zone_maintenance: zone 0.in-addr.arpa/IN: enter
May 03 09:19:52.268 zone_timer: zone db.gk-net.de/IN: enter
May 03 09:19:52.268 zone_maintenance: zone db.gk-net.de/IN: enter
May 03 09:19:52.268 zone db.gk-net.de/IN: sending notifies (serial 2005042913)
May 03 09:19:52.269 createfetch: ns1.granitecanyon.com A
May 03 09:19:52.269 createfetch: ns1.granitecanyon.com A6
May 03 09:19:52.269 zone_timer: zone localhost/IN: enter
May 03 09:19:52.269 zone_maintenance: zone localhost/IN: enter
May 03 09:19:52.270 zone_timer: zone 127.in-addr.arpa/IN: enter
May 03 09:19:52.270 zone_maintenance: zone 127.in-addr.arpa/IN: enter
May 03 09:19:52.270 zone_timer: zone 177.179.172.217.in-addr.arpa/IN: enter
May 03 09:19:52.270 zone_maintenance: zone 177.179.172.217.in-addr.arpa/IN: enter
May 03 09:19:52.270 zone 177.179.172.217.in-addr.arpa/IN: sending notifies (serial 2002061310)
May 03 09:19:52.270 createfetch: ns2.granitecanyon.com A
May 03 09:19:52.271 createfetch: ns2.granitecanyon.com A6
May 03 09:19:52.271 zone_timer: zone 255.in-addr.arpa/IN: enter
May 03 09:19:52.271 zone_maintenance: zone 255.in-addr.arpa/IN: enter
May 03 09:19:52.271 zone_timer: zone version.bind/CH: enter
May 03 09:19:52.271 zone_maintenance: zone version.bind/CH: enter
May 03 09:19:52.271 createfetch: . NS
May 03 09:19:52.610 createfetch: ns.senator.org A
May 03 09:19:52.737 createfetch: ns1.granitecanyon.com AAAA
May 03 09:19:54.635 createfetch: ns2.granitecanyon.com AAAA
Jetzt gehen mir rapide die Ideen aus. Was mache ich falsch?

Weitere Konfigurationsfiles:

/etc/bind/named.conf:

Code: Alles auswählen

options {
        directory "/var/cache/bind";
        query-source address * port 53;
        version "nix";
        auth-nxdomain no;    # conform to RFC1035

};
// prime the server with knowledge of the root servers
zone "." {
        type hint;
        file "/etc/bind/db.root";
};
// be authoritative for the localhost forward and reverse zones, and for
// broadcast zones as per RFC 1912
zone "localhost" {
        type master;
        file "/etc/bind/db.local";
};
zone "127.in-addr.arpa" {
        type master;
        file "/etc/bind/db.127";
};
zone "0.in-addr.arpa" {
        type master;
        file "/etc/bind/db.0";
};
zone "255.in-addr.arpa" {
        type master;
        file "/etc/bind/db.255";
};
// add entries for other zones below here
zone "db.gk-net.de" {
        type master;
        file "db.gk-net.de";
};
zone "177.179.172.217.in-addr.arpa" {
        type master;
        file "db.217.172.179.177";
};
/etc/resolv.conf:

Code: Alles auswählen

nameserver 217.172.179.177
nameserver 217.172.191.10
nameserver 217.172.166.9
/etc/hosts:

Code: Alles auswählen

127.0.0.1      localhost
217.172.179.177 chicago177.server4free.de chicago177.server4you.de ns1.gk-net.de
Danke und Gruss
Guido

Antworten