|
Hallo, ich habe ein Problem mit meinem bind9 Name Server. Und zwar wurde er nach folgender Anleitung konfiguriert: http://rimuhosting.com/support/bindviawebmin.jsp Es handelt sich um die Domain freeload4u.de. Um den NS zu testen, habe ich nslookup www.freeload4u.de eingegeben. Und bekomme als Antwort immer den named5.hansenet.de nicht
ns1.freeload4u.de. Der Aufbau sieht folgendermaßen aus: Router: 192.168.0.1 (DMZ = 153) Server( Name: box) : 192.168.0.153 /Debian Etch WinXPClient : 192.168.0.152 WinVistaCLient: 192.168.0.151 Meine /etc/hosts : ################ 127.0.0.1 localhost loopback 127.0.1.1 box.freeload4u.de # The following lines are desirable for IPv6 capable
hosts ::1 ip6-localhost ip6-loopback fe00::0 ip6-localnet ff00::0 ip6-mcastprefix ff02::1 ip6-allnodes ff02::2 ip6-allrouters ff02::3 ip6-allhosts /etc/resolv.conf ################# nameserver 127.0.0.1 /etc/bind/named.conf.options ################# options { directory "/etc/bind"; // If there is a firewall between you and
nameservers you want // to talk to, you might need to
uncomment the query-source // directive below. Previous versions of
BIND always asked // questions using port 53, but BIND 8.1
and later use an unprivileged // port by default. // query-source address * port 53; // If your ISP provided one or more IP
addresses for stable // nameservers, you probably want to use
them as forwarders. // Uncomment the following block, and
insert the addresses replacing // the all-0's placeholder. forwarders { 10.0.0.1; }; auth-nxdomain no; # conform to RFC1035 listen-on-v6 { any; }; notify no; }; /etc/bind/named.conf ################### // This is the primary configuration file for the
BIND DNS server named. // // Please read /usr/share/doc/bind9/README.Debian.gz
for information on the // structure of BIND configuration files in Debian,
*BEFORE* you customize // this configuration file. // // If you are just adding zones, please do that in
/etc/bind/named.conf.local include "/etc/bind/named.conf.options"; // 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"; }; // zone "com" { type delegation-only; }; // zone "net" { type delegation-only; }; // From the release notes: // Because many of our users are uncomfortable
receiving undelegated answers // from root or top level domains, other than a few
for whom that behaviour // has been trusted and expected for quite some
length of time, we have now // introduced the "root-delegations-only"
feature which applies delegation-only // logic to all top level domains, and to the root
domain. An exception list // should be specified, including "MUSEUM"
and "DE", and any other top level // domains from whom undelegated responses are
expected and trusted. // root-delegation-only exclude { "DE";
"MUSEUM"; }; include "/etc/bind/named.conf.local"; /etc/bind/named.conf.local ####################### // // Do any local configuration here // // Consider adding the 1918 zones here, if they are
not used in your // organization //include "/etc/bind/zones.rfc1918"; zone "freeload4u.de" { type master; file
"/etc/bind/freeload4u.de.hosts"; }; /etc/bind/freeload4u.de.hosts ######################### freeload4u.de. IN SOA box.
webmaster.freeload4u.de. ( 1188553418 10800 3600 604800 38400 ) freeload4u.de. IN NS box. freeload4u.de. IN A 192.168.0.153 freeload4u.de. IN NS ns1.freeload4u.de. www.freeload4u.de. IN CNAME
freeload4u.de. mail.freeload4u.de. IN A 192.168.0.153 freeload4u.de. IN MX 1 mail.yourdomain.com. Hier noch mal eine Zusammenfassung aller Records: Link: http://www.freeload4u.de/outdoor/debian_list_uebersicht.jpg Wo liegt der Fehler? Ich komme einfach nicht weiter. Kann mir jemand helfen? Gruß Henry |
