bind9 on freebsd 5.2

[pablobsd]

i'm new to freebsd but i need to setup dns server for pratice ... installed bind 9 fine
here is my named.conf file
getting error cannot fine named server server listening fine on port 53 to corresponding ip able to telnet ..
// $FreeBSD: src/etc/namedb/named.conf,v 1.14 2003/02/07 20:58:38 keramida Exp $
//
// Refer to the named.conf(5) and named(8) man pages for details. If
// you are ever going to set up a primary server, make sure you
// understand the hairy details of how DNS works. Even with
// simple mistakes, you can break connectivity for affected parties,
// or cause huge amounts of useless Internet traffic.

options {
directory "/etc/namedb";
allow-query {192.168.10/24; 127.0.0.1; };
pid-file "/var/run/named/pid";

// In addition to the "forwarders" clause, you can force your name
// server to never initiate queries of its own, but always ask its
// forwarders only, by enabling the following line:
//
forward only;
// If you've got a DNS server around at your upstream provider, enter
// its IP address here, and enable the line below. This will make you
// benefit from its cache, thus reduce overall DNS traffic in the Internet.
/*
forwarders {
127.0.0.1; 24.153.22.67;
};
*/
/*
* 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;

/*
* If running in a sandbox, you may have to specify a different
* location for the dumpfile.
*/
// dump-file "s/named_dump.db";
};

// Note: the following will be supported in a future release.
/*
host { any; } {
topology {
192.168.10.0/24; 127.0.0.0/8;
};
};
// Setting up secondaries is way easier and a rough example for this
// is provided below.

zone "1.0.0.0.0.0//
// If you enable a local name server, don't forget to enter 127.0.0.1
// first in your /etc/resolv.conf so this server will be queried.
// Also, make sure to enable it in /etc/rc.conf.

zone "." {
type hint;
file "named.root";
};

zone "0.0.127.IN-ADDR.ARPA" {
type master;
file "localhost.rev";
};
zone "domain.ca"
type master;
file "db.domain.ca";
allow-transfer {none; };

};
zone "0.0.127.IN-ADDR.ARP" {
type master;
file "db.0.0.127";
allow-transfer {none; };

};
zone "10.168.192.in-addr.arp" {
type master;
file "db.10.168.192";
allow-transfer {none; };
};

// RFC 3152.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"
type master;
file "localhost-v6.rev";
};
// RFC 1886 -- deprecated
zone "1.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.INT" {
type master;
file "localhost-v6.rev";
};
// NB: Do not use the IP addresses below, they are faked, and only
// serve demonstration/documentation purposes!
//
// Example secondary config entries. It can be convenient to become
// a secondary at least for the zone your own domain is in. Ask

// your network administrator for the IP address of the responsible
// primary.
//
// Never forget to include the reverse lookup (IN-ADDR.ARPA) zone!
// (This is named after the first bytes of the IP address, in reverse
// order, with ".IN-ADDR.ARPA" appended.)
//
// Before starting to set up a primary zone, make sure you fully
// understand how DNS and BIND works. There are sometimes
// non-obvious pitfalls. Setting up a secondary is simpler.
//
// NB: Don't blindly enable the examples below. Use actual names
// and addresses instead.
//
// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:

// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:

// NOTE!!! FreeBSD can run bind in a sandbox (see named_flags in rc.conf).
// The directory containing the secondary zones must be write accessible
// to bind. The following sequence is suggested:
//
// mkdir /etc/namedb/s
// chown bind:bind /etc/namedb/s
// chmod 750 /etc/namedb/s

*
zone "domain.ca" {
type slave;
file "s/domain.ca.bak";
masters {
192.168.10.51; 127.0.0.1;
};
};
zone "10.168.192.in-addr.arpa" {
type slave;
file "s/10.168.192.in-addr.arpa.bak";
masters {
192.168.10.51; 127.0.0.1
};
};
*/

controls {
inet 127.0.0.1 allow {localhost; } keys { "rndc-key";
};

 

[Claudek]

Have you done any nslookups? To both host and IP addresses. Log info would be great too.
Btw,you may want to change the line:
pid-file "/var/run/named/pid";
to
pid-file "/var/run/named.pid";



Claudius (What certifications??)

http://www.iteq.com.au

 

[pablobsd]

yes i tried ns lookup it goes to the 127.0.0.1 fine but if i type server and specify server ip address and then try to resolve it will resolve local domain but when i try to reosolve from other computer on my local network it resolve but does not resolve and public address. and if i only use that dns server address on local machine not able to access outsidde website ..

 

[pablobsd]

thanks for the help.. reinstalled everything now all working fine ... guess the problem was bcs i reinstalled bind on the old bind