Re: [cobalt-users] A single SOA for all unlisted Zones.... how?

["E.B. Dreger" <eddy+public+spam@xxxxxxxxxxxxxxxxx>]

CL> Date: Sat, 1 Feb 2003 11:34:10 +1000
CL> From: Cobalt List


CL> I have been trying to create a solution such that a global
CL> SOA is used for unresolved domains which have the NS listed
CL> as that of my server; I have an idea on what it should be
CL> like but this obviously doesn't work>>

Okay.  Sort of like the "we registered our domain with <x>"
pages?


CL> In /etc/named.conf :
CL> ======================================================
CL> # This would catch all unresolved and set them to be processed by
CL> # pri.unresolved zone file
CL> zone "*" { type master; file "pri.unresolved"; };
CL> ======================================================

I'd recommend using separate zone files.  What happens when you
must edit one domain?


CL> In /etc/named/pri.unresolved:
CL> ======================================================
CL> # Set the NS for all unresolved as ns1.auzit.net
CL>
CL> $TTL 86400
CL> * IN SOA ns1.auzit.net. viper.staff.cairnscity.com. (
CL>         2003012610
CL>         10800
CL>         3600
CL>         604800
CL>         86400
CL>         )
CL>
CL> # Wildcard NS
CL> * IN      NS      ns1.auzit.net.
CL> * IN      NS      ns2.auzit.net.

I really don't think you want wildcard NS records. :-)


CL> # Now A Names which define the domains.
CL>
CL> domain1.com.    in      a       10.0.0.4
CL> www.domain1.com.        in      a       10.0.0.4
CL> domain2.com.    in      a       10.0.0.99
CL> www.domain2.com.        in      a       10.0.0.99

Better yet... just use

	@   IN   A   10.0.0.4
	www   IN   A   10.0.0.4

No need manually appending $ORIGIN to the RRs.

Also:  Do you need the domains to go to separate IP addresses?
If so, why are you trying to use a single zone file in the first
place?!  BIND complains loudly when a zonefile contains RRs that
live outside the current SOA. :-)

When you create an SOA record, you're stating that you are
authoritative for that entire zone, except for where you have
glue records signifying cuts.  If you want to offer DNS for:

	zone1.example
	somedomain.example
	yet.another.example

you _cannot_ create an SOA record for the .example zone... unless
you have all the glue records for .example zones you don't host.
(Hint:  You don't.  You're not running GTLD DNS on a Cobalt.)

Thus you need separate SOAs for each of the above... unless all
zones have identical information.  Hence why I ask if you need to
use separate IP addresses.


CL> Hopefully you can see what I'm trying to achieve, however I
CL> have no idea how to make it work (what you've seen is me
CL> trying to apply my limited knowledge to areas where it
CL> doesn't fit :P ).

Cobalts store zone information in

	/etc/named/records

This is the file used by the CGI scripts to generate zone files.
If you write to it, the expected zone files, and named.conf, you
should be in good shape.  Alternatively, you can modify the above
file, then regenerate the rest via the GUI; that's what I do.

Shameless plug:  Autodetecting unconfigured zones is a feature
we're incorporating in the new version of our DNS service.
Details off-list.  I know of no other automated service like
this; if one exists, please post so archive readers are aware of
all such offerings.


Eddy
--
Brotsman & Dreger, Inc. - EverQuick Internet Division
Bandwidth, consulting, e-commerce, hosting, and network building
Phone: +1 (785) 865-5885 Lawrence and [inter]national
Phone: +1 (316) 794-8922 Wichita

~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Date: Mon, 21 May 2001 11:23:58 +0000 (GMT)
From: A Trap <blacklist@xxxxxxxxx>
To: blacklist@xxxxxxxxx
Subject: Please ignore this portion of my mail signature.

These last few lines are a trap for address-harvesting spambots.
Do NOT send mail to <blacklist@xxxxxxxxx>, or you are likely to
be blocked.