Bind 9.1.1rc3

[Mark.Andrews at nominum.com]

	Firstly only start named, not lwresd.  You have told named to
	act as lwresd as well as named.

	Secondly, since I see no error messages about zone errors I
	can only assume that you are missing a PTR record for
	131.0.168.192.IN-ADDR.ARPA.

	Search the archives for "nslookup sucks" for more details.

	Mark

> 
> I have successfully compiled and installed  bind 9.1.1rc3, an upgrade from 8.
> 2.x and slightly modified the /etc/named.conf file ( shown below). The logs i
> ndicate it is running ok but then when I try to test the nameserver for my lo
> cal homenet using nslookup I get the error message " can't find server name f
> or address 192.168.0.131: non existent host/domain" Could any one check my co
> nfig files and log message to let me know what I am doing wrong?
> 
> /etc/resolv.conf:
> search  homenet.com
> nameserver 192.168.0.131
> nameserver 204.52.135.1
> nameserver 204.52.135.2
> lwserver 192.168.0.131
> 
> named.conf:
> acl homenet { 192.168.0.0/24; };	
> options {
> 	directory "/var/named";
>         pid-file "/var/run/named-pid";
>         auth-nxdomain yes;
>         listen-on port 53 { 192.168.0.131; };
>         sortlist { localhost; homenet; };     
>          allow-transfer { 192.168.0.129; };
>          allow-query { 192.168.0.0/24; localhost; };
>          allow-recursion { 192.168.0.0/24; localhost; };
>          version " Go Away! ";
>          notify no;
> };
> logging {
>          category lame-servers { null; };
> };
> lwres {
>       listen-on { 192.168.0.131;};
>       search { homenet.com; };
> };
> // 
> // a master nameserver config
> // 
> zone "homenet.com" {
> 	type master;
> 	file "homenet.db";
>         allow-query { any; }; 
> };
> zone "0.168.192.in-addr.arpa" {
> 	type master;
> 	file "192.168.0.rev";
>         allow-query { any; };
> };
> zone "0.0.127.in-addr.arpa" {
> 	type master;
> 	file "named.local";
>         notify no;
> };
> zone  "." { type hint; file "named.ca"; };
> 
> LOGS:
> Mar 13 05:38:18 linuxserv /usr/local/sbin/named[530]: starting BIND 9.1.1rc3
> Mar 13 05:38:18 linuxserv /usr/local/sbin/named[530]: using 1 CPU
> Mar 13 05:38:18 linuxserv /usr/local/sbin/lwresd[532]: starting BIND 9.1.1rc3
> Mar 13 05:38:18 linuxserv /usr/local/sbin/lwresd[532]: using 1 CPU
> Mar 13 05:38:18 linuxserv /usr/local/sbin/named[535]: loading configuration f
> rom '/etc/named.conf'
> Mar 13 05:38:19 linuxserv /usr/local/sbin/lwresd[537]: loading configuration 
> from '/etc/lwresd.conf'
> Mar 13 05:38:19 linuxserv /usr/local/sbin/lwresd[537]: the default for the 'a
> uth-nxdomain' option is now 'no'
> Mar 13 05:38:19 linuxserv modprobe: can't locate module net-pf-10
> Mar 13 05:38:19 linuxserv /usr/local/sbin/lwresd[537]: no IPv6 interfaces fou
> nd
> Mar 13 05:38:19 linuxserv /usr/local/sbin/lwresd[537]: not listening on any i
> nterfaces
> Mar 13 05:38:19 linuxserv modprobe: can't locate module net-pf-10
> Mar 13 05:38:19 linuxserv /usr/local/sbin/named[535]: no IPv6 interfaces foun
> d
> Mar 13 05:38:19 linuxserv /usr/local/sbin/named[535]: listening on IPv4 inter
> face eth0, 192.168.0.131#53
> Mar 13 05:38:19 linuxserv /usr/local/sbin/named[535]: lwres listening on 192.
> 168.0.131#921
> Mar 13 05:38:19 linuxserv /usr/local/sbin/lwresd[537]: running
> Mar 13 05:38:19 linuxserv /usr/local/sbin/named[535]: running
> Mar 13 05:46:26 linuxserv modprobe: can't locate module net-pf-10
> Mar 13 05:46:26 linuxserv lwresd[612]: no IPv6 interfaces found
> Mar 13 05:46:26 linuxserv lwresd[612]: not listening on any interfaces
> Mar 13 05:46:26 linuxserv lwresd[612]: running
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com