Op zaterdag 08 juni 2002 15:32 schreef jep het volgende:
Wat werkt er precies niet allemaal?
Hoe ziet je named.conf eruit?
Post je gemaakte zonefiles eens?
/etc/named.conf
// generated by named-bootconf.pl
options {
directory "/var/named";
/*
* 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 uses an unprivileged
* port by default.
*/
// query-source address * port 53;
};
//
// a caching only nameserver config
//
controls {
inet 127.0.0.1 allow { localhost; } keys { rndckey; };
};
zone "." IN {
type hint;
file "named.ca";
};
zone "localhost" IN {
type master;
file "localhost.zone";
allow-update { none; };
};
zone "0.0.127.in-addr.arpa" IN {
type master;
file "named.local";
allow-update { none; };
};
zone "home" IN {
type master;
file "home.local";
};
zone "0.168.192.in-addr.arpa" IN {
type master;
file "reverse";
};
include "/etc/rndc.key";
----------------------------------------------------------
/var/named/home.local
$TTL86400
@ IN SOA home. rkm_fs1.rkmdomain.home. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
home. IN NS ns.rkmdomain.home.
ns.rkmdomain.homeA192.168.0.2
home.IN MX 10 rkmdomain.home
home.IN A 192.168.0.2
ns.IN A 192.168.0.2
rkm_fs1 IN A 192.168.0.2
/var/named/localhost.zone
$TTL86400
$ORIG IN localhost.
@1D IN SOA@ root (
42; serial (d. adams)
3H; refresh
15M; retry
1W; expiry
1D ); minimum
1D IN NS@
1D IN A 127.0.0.1
/var/named/named.ca
/var/named/named.local
$TTL86400
@ IN SOA localhost. root.localhost. (
1997022700 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400 ) ; Minimum
IN NS localhost.
1 IN PTR localhost.
/var/named/reverse
192.168.in-addr.arpa.IN SOA home rkm_fs1.rkmdomain.home (
1
10800
3600
604800
38400 )
192.168.in-addr.arpa. IN NS home.
2.0.168.192.in-addr.arpa. IN PTR rkm_fs1.rkmdomain.home.
dit zijn mijn config file's