bind still using forwarder

Mark.Andrews at nominum.com Mark.Andrews at nominum.com
Sat Mar 10 22:43:50 UTC 2001


> 
> I have just completed setup of bind 9.  I am having one problem that I
> can't root out.  The config is as follows;
> 
> FreeBSD4.1Stable on an Intel PI
> Bind 9.1
> Connected via Broadband through a Linksys router (192.168.1.1) using NAT
> 
> The WAN side of the router uses DHCP. There is a "keep alive" so my IP
> has been static for 3 months.
> I use "route add default 192.168.1.1" to get the network pointed in the
> right direction.
> 
> My local subnet is 192.168.1/24. After a few tweeks of the db files(the
> O'Reiley BIND book is v8) the named daemon gets up and running with some
> minor complaints about my IPv6 zone entry.

	Well if named is complaining about a error in a zone file then
	it will not be serving that zone file.  Fix the error.

> Before trying to set up as a
> primary name server I had a forwarder defined in my named.conf file.
> That pointed to my upstream ISP name server. I have since commented that
> line out. I have "kill -11"d the named daemon and restarted a number of
> times. Yet, when I do an nslookup, it still uses the forwarding name
> server and does not check my local name server data at all. I suspect I
> might get it straight with a reboot but I'm wondering where or why this
> information is saved. My current situation is a test environ at home,
> but when I go to the production implementation at work, reboots will be
> more painful. Any direction will be humbley appreciated.
> 
> 
> 
> 
--
Mark Andrews, Nominum Inc.
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark.Andrews at nominum.com


More information about the bind-users mailing list