Skip site navigation (1)Skip section navigation (2)
Date:      Fri, 07 Nov 97 19:14:28 -0800
From:      "Studded" <Studded@dal.net>
To:        "freebsd-questions@FreeBSD.ORG" <freebsd-questions@FreeBSD.ORG>, "ringlord@bbs.dcoisp.net" <ringlord@bbs.dcoisp.net>
Subject:   Re: named concerns
Message-ID:  <199711080314.TAA14416@dragonlair.dal.net>

next in thread | raw e-mail | index | archive | help
On Fri, 7 Nov 1997 19:25:58 -0500, ringlord@bbs.dcoisp.net wrote:

>Hello to all.

	Greetings. :)

>I recently setup my own nameserver running bind 4.96 on a freebsd
>2.2.2-r box.  I am reading the o'reilly and associates book on dns and
>bind.

	Congrats. :)  If you are relying on your nameserver for something
critical (like outside resolution) you should seriously consider upgrading
to BIND 4.9.6 since it has much better protection against hostname
spoofing, etc.  The easiest way for you to do that would probably be to
upgrade to FreeBSD 2.2.5, which comes with BIND 4.9.6 in the base system. 
However neither is something you would need to do tomorrow... just
something to plan on.

[snip]
>However, when I look in the /var/log/messages file, I am receiving
>syntax errors all over the place.  These errors point to my db files,
>both db.domain and db.ip-number files.

	Ok, first off, if you are reporting error messages, please tell us
what they are. :)   I can guess at the one from your forward resolution
file, but your PTR file didn't come through.  Next time please send the
files in the body of your letter, instead of as an attachment.  They are
small enough.  

>Now, qmail will not resolve remote names, but it will when I switch to
>my secondary nameserver, which is run by my isp.
>So.  With all that said, I am lead to believe that there is indeed
>something incorrect with my syntax.

	The syslog doesn't lie. :)  If BIND sees an error, it will report
it, and since it's the authority, you can assume that it's right.

[snip]
>BTW.  I am using long names here, not short-cuts.

	This shouldn't matter, it's just a little extra work for you.

>The name of the file is: db.dcoisp and the domain is dcoisp.net.  SHould
>I name the file, db.dcoisp.net?

	You could name it GeorgehasGreenHair and it wouldn't matter.  :)

Ok, here is a blow-by-blow for your zone file:

dcoisp.net. IN SOA mail.dcoisp.net.
1
10800
3600
604800
86400

dcoisp.net. IN NS mail.dcoisp.net.

; here comes the hosts!
localhost.dcoisp.net. IN A 127.0.0.1
bbs.dcoisp.net. IN A 208.128.192.226
mail.dcoisp.net. IN A 208.128.192.227
www.dcoisp.net. IN A 208.128.192.228
twcmedia.dcoisp.net. IN A 208.128.192.241

; aliases anyone?
dcoisp.net. IN CNAME bbs.dcoisp.net.

	It's a good idea to start with an origin statement, just so that
your named doesn't get confused.  Also, it doesn't cost you a thing to add
a hostname for ns.dcoisp.net, and it looks a little more professional. 
You also need a zone contact in your SOA record.  And you need parentheses
to indicate that the SOA record is continuing on another line.  Using the
date, plus a counter at the end for your serial number will give you an
integral accounting mechanism to keep track of changes.  Finally, you
can't have a cname for something that already has any other kind of
record, which is at least one thing that you're getting syntax errors
about.  Here is how I'd set up the same zone:

$ORIGIN dcoisp.net.

@	IN SOA ns.dcoisp.net. ringlord.bbs.dcoisp.net. (
1997110701	; Serial
10800		; Refresh
3600		; Retry
604800		; Expire
86400 )		; Default TTL

	IN NS	ns.dcoisp.net.
	IN A	208.128.192.226 ; This is in place of the cname

; here comes the hosts!
localhost	IN A	127.0.0.1
ns		IN A	208.128.192.227
mail		IN A	208.128.192.227
bbs		IN A	208.128.192.226
www		IN A	208.128.192.228
twcmedia	IN A	208.128.192.241

Hope this helps,

Doug
Hostmaster, DALnet Internet Relay Chat network

*** Proud operator, designer and maintainer of the  world's largest
*** Internet Relay Chat server. 4,168 clients and still growing. :-)
*** Try spider.dal.net on ports 6662-4    (Powered by FreeBSD)
***		Part of the DALnet IRC network		***




Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199711080314.TAA14416>