BIND Zone Help!!

[Brenton Bartel]

Hello all.
I seem to be having a terrible difficulty setting up my BIND stuff. I have 2 domains (say domain1.org & domain2.com) that will be pointing to the same server, and just wondering what's the best way to do it. I would post what I have so far and ask why it's not working, but I figure I'll just start from scratch.
So the question is, what's the best way to set all this stuff up?? Input as to what the zone files & the named.conf should look like would be great!
Thanx

[W.C. Epperson]

It would take a lot less time to critique what you've done so far than to write conf and zone files for you. Maybe someone else has the time right now. But they'll probably need to know your BIND version to help.

Among many excellent BIND resources on the Internet is the "Setting Up a Name Server" chapter in Mark Burgess's "Principles of System Administration" at http://www.iu.hio.no/~mark/sysadmin/SystemAdmin_toc.html
It includes sample zone and conf files for named 8.x.

[Brenton Bartel]

Alrighty, I am currently running BIND 8.something, here's what I have thus far (names & IPs changed):

// named.conf:
options {
directory "/var/named";
* port 53;
};

zone "." {
type hint;
file "root.hints";
};

zone "0.0.127.in-addr.arpa" {
type master;
file "named.local";
allow-update { none; };
};

zone "letrabb.com" {
type master;
notify no;
file "mydomain.com";
};

zone "11.22.33.in-addr.arpa" {
type master;
notify no;
file "mydomain.addr";
};

key "key" {
algorithm hmac-md5;
secret "mysecretkey";
};
//-----------
//mydomain.com zone:
$TTL 86400
@ IN SOA dns1.mydomain.com. brentonb.uvic.ca. (
2002091103 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400) ; Minimum

NS dns1.mydomain.com.
MX 10 mail

localhost A 127.0.0.1

mydomain.com. A 11.22.33.44
mail A 11.22.33.44
ftp A 11.22.33.44
www A 11.22.33.44
CNAME 11.22.33.44

// -----
// mydomain.addr zone
$TTL 86400
@ IN SOA mydomain.com. brentonb.uvic.ca. (
2002091101 ; Serial
28800 ; Refresh
14400 ; Retry
3600000 ; Expire
86400) ; Minimum

NS dns1.mydomain.com.
160 PTR mydomain.com.

I have no idea where it's goin wrong, but it is. Any help would be grand.
Thank you

[W.C. Epperson]

The first thing that jumps out is that there's no "A" record for dns1.mydomain.com, so it's not defined by its own authoritative server. The next is that there are both "A" and "CNAME" records for mydomain.com, which is illegal. Finally, none of the Resource Records (A, MX, CNAME, PTR) have a "class" field (IN), which may be presumed (I'd have to do a bit of reading and experimentation to say for sure), but I always put it in explicitly, e.g.
mail IN A 11.22.33.44Also, you could use CNAME instead of A records for ftp.mydomain.com and www.mydomain.com. It's recommended that an MX not point to a CNAME, so you should leave mail.mydomain.com the way it is.

Just a quick once-over. Post what you fixed and what results you get when you load the zones and when you try to query them and we can go another round if it's not fixed. One of the frustrating things about DNS is that bad zone data often makes things work weirdly instead of definitively breaking.

[W.C. Epperson]

OH: Your inverse zone would be:
33.22.11.in-addr.arpa

[W.C. Epperson]

These students have short attention spans. I'm too old to care about the points, but it would have been nice to know if he got the zone working. Sigh.