Skip site navigation (1)Skip section navigation (2)
Date:      Tue, 11 Jul 2006 14:20:32 -0400
From:      "Lisa Casey" <lisa@jellico.com>
To:        <freebsd-questions@freebsd.org>
Subject:   Re: Bind problem
Message-ID:  <004e01c6a516$b2bd45d0$d51a2cd0@lisac>
References:  <001701c6a454$ad756d40$d51a2cd0@lisac> <20060710194312.GC3260@osiris.chen.org.nz> <002701c6a468$91f20830$d51a2cd0@lisac> <6.0.0.22.2.20060710181656.025a9148@mail.computinginnovations.com>

next in thread | previous in thread | raw e-mail | index | archive | help
Hi,


> The installed bind is not in /usr/local/bin that is where the port is
> installed.  You might want to do a:
> # which bind
>
> and set rc.conf to the right value for the program.
>
>         -Derek
>
>
> At 04:34 PM 7/10/2006, Lisa Casey wrote:
>
>>----- Original Message ----- From: "Jonathan Chen" <jonc@chen.org.nz>
>>To: "Lisa Casey" <lisa@jellico.com>
>>Cc: <freebsd-questions@freebsd.org>
>>Sent: Monday, July 10, 2006 3:43 PM
>>Subject: Re: Bind problem
>>
>>
>>>Did you remember to add:
>>>    named_program="/usr/local/sbin/named"
>>>to /etc/rc.conf?
>>
>>Yes. /etc/rc.conf has the following lines for named:
>>
>>named_enable="YES"
>>named_program="/usr/local/sbin/named"
>>named_flags="-u bind -g bind -c /etc/namedb/named.conf"
>>
>>
>>Lisa Casey
>>

This actually didn't quite answer the problem, but it did lead me in the 
right direction to solve it.

which bind, of course, doesn't work and which named just gives me the path 
to the named executable as given in /etc.rc.conf  But, this got me to 
thinking so I did a     find / -name named -print       And found something 
interesting. I have named executables in both /usr/local/sbin and  /usr/sbin 
So I changed the line in /etc/rc.conf that read: 
named_program="/usr/local/sbin/named"  to named_program="/usr/sbin/named" 
and rebooted the box.  So far, so good. named -v  gives me BIND 9.3.0 and in 
/var/messages the reboot info shows the same when named loads:

Jul 11 13:40:50 netlink kernel: Mounting root from ufs:/dev/da0s1a
Jul 11 13:40:50 netlink named[293]: starting BIND 9.3.0 -u bind -c 
/etc/namedb/n
amed.conf -t /var/named
Jul 11 13:40:51 netlink named[293]: command channel listening on 
127.0.0.1#953

(It's also picking  up the command channel, so I guess I did that right).

I have one last problem (or at least I hope so!). I maybe ought to ask this 
in a bind newsgroup, but there are enough folks on this list running bind on 
FreeBSD that someone  ought to know. Evidently Bind 9 doesn't like my zone 
files whereas Bind 8 was OK with them. A little background:  My main domain 
name is jellico.com    I also host several virtual domains using IP based 
virtual domains in Apache2. So each of my virtual domains has been assigned 
an IP address out of my Class C.   In /etc/namedb/M (the directory where I 
keep my zone files that this  DNS server is master for) I have (among other 
zones) jellico.com.db which is my forward file for the domain and 
26.44.208.in-addr.arpa  which is the reverse zone file for the domain. I 
have always had my virtual domains configured into my forward file 
(jellico.com.db) so as to  enable forward DNS resolution on those. They are 
configured into jellico.com.db like this:

jellico.tn.us.  IN      A       208.44.26.225
multi-226       IN      A       208.44.26.226
multi-227       IN      A       208.44.26.227
multi-228       IN      A       208.44.26.228
multi-229       IN      A       208.44.26.229
multi-230       IN      A       208.44.26.230
tspma.com.      IN      A       208.44.26.231
copperhill.com. IN      A       208.44.26.232
multi-233       IN      A       208.44.26.233
www.jellico.net.        IN      A       208.44.26.234
multi-235       IN      A       208.44.26.235
stair-way-to-heaven.com.        IN      A       208.44.26.236
multi-237       IN      A       208.44.26.237
kcsvo.com.      IN      A       208.44.26.238
multi-239       IN      A       208.44.26.239
multi-240       IN      A       208.44.26.240
wingsofvictorychurch.org.       IN      A       208.44.26.241
multi-242       IN      A       208.44.26.242
multi-243       IN      A       208.44.26.243

There are a few others, but you get the idea. I have also always had my 
virtual domains setup in my reverse file so as to enable reverse DNS 
resolution on these. This section of my reverse file looks like so:

225     IN      PTR     jellico.tn.us.
226     IN      PTR     multi-226.jellico.com.
227     IN      PTR     multi-227.jellico.com.
228     IN      PTR     multi-228.jellico.com.
229     IN      PTR     multi-229.jellico.com.
230     IN      PTR     multi-230.jellico.com.
231     IN      PTR     tspma.com.
232     IN      PTR     copperhill.com.
233     IN      PTR     multi-233.jellico.com.
234     IN      PTR     www.jellico.net.
234     IN      PTR     multi-234.jellico.com.
235     IN      PTR     multi-235.jellicocom.
236     IN      PTR     stairway-to-heaven.com.

Bind 9 is OK with my reverse file, but it doesn't like any entry in my 
forward file that ends in a dot (so as not to append jellico.com to it). 
When I rebooted the box, as soon as the nameserver loads I get these error 
messages in /var/messages:

Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:222: ignoring 
out-of-zone d
ata (mail.campbellcounty.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:224: ignoring 
out-of-zone d
ata (campbellcounty.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:522: ignoring 
out-of-zone d
ata (jellico.tn.us)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:528: ignoring 
out-of-zone d
ata (tspma.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:529: ignoring 
out-of-zone d
ata (copperhill.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:531: ignoring 
out-of-zone d
ata (www.jellico.net)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:533: ignoring 
out-of-zone d
ata (stair-way-to-heaven.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:535: ignoring 
out-of-zone d
ata (kcsvo.com)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:538: ignoring 
out-of-zone d
ata (wingsofvictorychurch.org)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:544: ignoring 
out-of-zone d
ata (netlink2000.net)
Jul 11 13:40:51 netlink named[293]: M/jellico.com.db:549: ignoring 
out-of-zone d
ata (shamrockweb.com)

I do, of course, also have separate zone files in /etc/namedb/M for each 
virtual domain, stair-way-to-heaven.com.db, shamrockweb.com.db, 
wingsofvictorychurch.org.db, etc.

(Finally) here's my question. Bind 8 was evidently quite OK with me defining 
virtual domains in my forward file as I have done for years. Bind 9 is not 
happy with this at all.   How do I do this in Bind 9? My forward file 
contains an entry for each IP address of the Class C, I have to call the IP 
addresses something in my forward file, and that something OUGHT to be the 
name of the domain that I have assigned that IP address to in order for 
forward resolution to work correctly. Isn't this right? Sigh,  obviously not 
since Bind is complaining. So how DO I define these virtual domains in my 
forward file under Bind 9?

Thanks for all the help,

Lisa Casey




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?004e01c6a516$b2bd45d0$d51a2cd0>