dns_master_load issues

[Mark Andrews]

> This is an OpenPGP/MIME signed message (RFC 2440 and 3156)
> --------------enig9E4C606388E5B127F6327655
> Content-Type: text/plain; charset=ISO-8859-1
> Content-Transfer-Encoding: 7bit
> 
> Mark Andrews wrote:
> >>Funny you say that since I realized about an hour before you sent this 
> >>email that was going on. I don't suppose there's any other way to share 
> >>one zone file with two zones? The main problem is the fact that this 
> >>zone has over a hundred origins and setting them for one domain negates 
> >>it from being used for the other domain since its out of its zone. I was 
> >>hoping doing origins like this would enable me to share the file with 
> >>both zones, but now I realize that won't work. So either I'm missing how 
> >>I can do this in a simple manner or create some other method of keeping 
> >>both zones the same.
> >>
> >>Any ideas?
> > 
> > 
> > 	You can use $INCLUDE, the origin is reset on return.
> 
> Ah, didn't realize origin was reset like that when you used the $INCLUDE
> directive. That would work for a portion of our subdomains, but we have
> some origins that only have a handful of hosts in them so making a
> separate file for each would become a headache eventually.
> 
> > 	You can use DNAME for one of the zones.
> 
> I just read about those records (hadn't really used them before). I
> tried doing a few things with DNAME records and it doesn't seem to like
> applying these to ORIGINS that are set. i.e.:
> 
> For the foo.example zone (bar.example being the other one)
> 
> 	IN DNAME foo.example.
> $ORIGIN blah.bar.example.
> 
> It complains about out-of-zone data with that. Or is there another way
> to use DNAMEs to make it work the way I'd like? I'm sure that I'm
> probably not using the right syntax or something :)

	One zone would be just.

@	SOA   ...
@	NS    ...
@	MX    ...
@	A     ...
@	AAAA  ...
@	DNAME <otherzone>

	Lookups in this zone would be converted to CNAMES on the fly
	by the nameservers.

	e.g.

; <<>> DiG 8.3 <<>> e.a.e.e.f.9.e.f.f.f.4.7.8.0.2.0.0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.int ptr 
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9691
;; flags: qr aa rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 2, ADDITIONAL: 0
;; QUERY SECTION:
;;	e.a.e.e.f.9.e.f.f.f.4.7.8.0.2.0.0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.int, type = PTR, class = IN

;; ANSWER SECTION:
0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.int.  1H IN DNAME  0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
e.a.e.e.f.9.e.f.f.f.4.7.8.0.2.0.0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.int.  0S IN CNAME  e.a.e.e.f.9.e.f.f.f.4.7.8.0.2.0.0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.
e.a.e.e.f.9.e.f.f.f.4.7.8.0.2.0.0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.  1H IN PTR  drugs.dv.isc.org.

;; AUTHORITY SECTION:
0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.  1H IN NS  ns-ext.vix.com.
0.2.8.0.0.0.f.1.0.7.4.0.1.0.0.2.ip6.arpa.  1H IN NS  ns-int.vix.com.

;; Total query time: 0 msec
;; FROM: drugs.dv.isc.org to SERVER: 127.0.0.1
;; WHEN: Wed Aug 17 08:17:17 2005
;; MSG SIZE  sent: 89  rcvd: 268

> > 	You can use multiple labels for the owners names, etc. and
> > 	not use $ORIGIN.
> 
> Could you elaborate more on this? I'm not quite following what you're
> suggesting here.

	foo.bar	 A  1.12.4.5
	xxx.yyy  A  1.12.3.4
 
> Thanks for the info so far!
> 
> -- 
> Lance Albertson
> 
> --------------enig9E4C606388E5B127F6327655
> Content-Type: application/pgp-signature; name="signature.asc"
> Content-Description: OpenPGP digital signature
> Content-Disposition: attachment; filename="signature.asc"
> 
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.1 (GNU/Linux)
> 
> iD8DBQFDAf+sQW+hXSf0t0IRAu2BAKDWhstIOb9BlrgpPBIfSenlBYaJngCfUVhP
> 0F0embot8DvkZ9dC1OINJUQ=
> =UILy
> -----END PGP SIGNATURE-----
> 
> --------------enig9E4C606388E5B127F6327655--
--
Mark Andrews, ISC
1 Seymour St., Dundas Valley, NSW 2117, Australia
PHONE: +61 2 9871 4742                 INTERNET: Mark_Andrews at isc.org