Bind problem
Derek Ragona
derek at computinginnovations.com
Tue Jul 11 19:11:20 UTC 2006
Lisa,
Your forward file should be something like this:
================================================
$TTL 3600
@ IN SOA ns.jellico.com. dnsadmin.jellico.com. (
2003071101 ; serial
3H ; refresh
1H ; retry
1W ; expiry
1D ) ; minimum
; DNS Servers
@ IN NS ns.jellico.com.
@ IN NS ns2.jellico.com.
; Machine Names
localhost IN A 127.0.0.1
mail IN A 208.44.26.225
pop IN A 208.44.26.225
@ IN A 208.44.26.225
; Aliases
www IN CNAME @
ww IN CNAME @
w IN CNAME @
; MX Record
@ IN MX 10 mail.jellico.com.
================================================
Just correct the IP's and add the rest of your hosts, and
correct any names that may be incorrect. Make sure you name
the file the same as bind is looking for in:
/etc/namedb/named.conf
If you have specific questions to any of the file entries you can email me
directly.
-Derek
At 01:20 PM 7/11/2006, Lisa Casey wrote:
>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 at chen.org.nz>
>>>To: "Lisa Casey" <lisa at jellico.com>
>>>Cc: <freebsd-questions at 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
>
>_______________________________________________
>freebsd-questions at freebsd.org mailing list
>http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at freebsd.org"
>
>--
>This message has been scanned for viruses and
>dangerous content by MailScanner, and is
>believed to be clean.
>MailScanner thanks transtec Computers for their support.
>
--
This message has been scanned for viruses and
dangerous content by MailScanner, and is
believed to be clean.
MailScanner thanks transtec Computers for their support.
More information about the freebsd-questions
mailing list