suresh.tattikota@info-spectrum.com schrieb:
hi this is my named.conf
// // named.conf for Red Hat caching-nameserver //
options { directory "/var/named"; dump-file "/var/named/data/cache_dump.db"; statistics-file "/var/named/data/named_stats.txt"; /* * 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; // forward first; // forwarders { // 172.18.1.212; // }; forward first; forwarders { 203.193.139.150; }; };
// // a caching only nameserver config // controls { inet 127.0.0.1 allow { localhost; } keys { rndckey; }; };
key "rndckey" { algorithm hmac-md5; secret "8Ik4b9wwIirsJU0AVy5gy29V3F7VpEpNV6TqlEZVz6OSCoOMAb"; };
zone "." IN { type hint; // file "named.ca"; file "named.root"; };
zone "localdomain" IN { type master; file "localdomain.zone"; allow-update { none; }; }; 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 "0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa" IN { type master; file "named.ip6.local"; allow-update { none; }; };
zone "255.in-addr.arpa" IN { type master; file "named.broadcast"; allow-update { none; }; };
zone "0.in-addr.arpa" IN { type master; file "named.zero"; allow-update { none; }; };
zone "suresh.com" IN { type master; file "open-ims.dnszone"; notify no; };
this is my rndc.conf
key "rndckey" { algorithm hmac-md5; secret "8Ik4b9wwIirsJU0AVy5gy29V3F7VpEpNV6TqlEZVz6OSCoOMAb"; };
options { default-key "rndckey"; default-server 127.0.0.1; default-port 953; };
this is the log message # named -g -p 53 21-Jun-2008 07:19:35.630 starting BIND 9.3.3rc2 -g -p 53 21-Jun-2008 07:19:35.631 found 1 CPU, using 1 worker thread 21-Jun-2008 07:19:35.635 loading configuration from '/etc/named.conf' 21-Jun-2008 07:19:35.637 listening on IPv4 interface lo, 127.0.0.1#53 21-Jun-2008 07:19:35.639 listening on IPv4 interface eth0, 127.0.0.1#53 21-Jun-2008 07:19:35.640 could not configure root hints from 'named.root': file not found 21-Jun-2008 07:19:35.641 loading configuration: file not found 21-Jun-2008 07:19:35.641 exiting (due to fatal error)
this is the error
# rndc reload rndc: decode base64 secret: bad base64 encoding
Different errors now, compared with your previous postings.
21-Jun-2008 07:19:35.640 could not configure root hints from 'named.root': file not found
// file "named.ca"; file "named.root";
Create the file if you have it renamed or deleted.
rndc: decode base64 secret: bad base64 encoding
Build up a valid secret key. Use `rndc-confgen -a' for this.
Alexander