Linux Archive

Linux Archive (http://www.linux-archive.org/)
-   Fedora/Linux Management Tools (http://www.linux-archive.org/fedora-linux-management-tools/)
-   -   fix zone config matching and minimize the number of zone files generated (http://www.linux-archive.org/fedora-linux-management-tools/85065-fix-zone-config-matching-minimize-number-zone-files-generated.html)

Michael DeHaan 05-09-2008 03:10 PM

fix zone config matching and minimize the number of zone files generated
 
John Eckersberg wrote:

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

http://jeckersb.fedorapeople.org/cobbler/0001-fix-zone-config-matching-and-minimize-the-number-of.patch



This fixes a few problems that I ran into as I sat down and actually
started deploying my own feature :)

Previously manage_forward_zones and manage_reverse_zones were optional
and were supposed to restrict the zone files generated. Except it
didn't really work all that well. For example...

If my settings looked like this:

manage_forward_zones:
~ - 'foo.example.com'

Only hosts that matched 'hostname.foo.example.com' would go into the
zone. If you had hostname.subdomain.foo.example.com it would not match.

Furthermore if you did not specify manage_forward_zones then it would
take every host, chop the hostname off the front and create a zone file
for the remainder of the FQDN. As I started to use it I realized the
number of zone files was quickly getting unmanageable. I have other
nameservers to configure as slaves for these zones and I was needing to
update them everytime somebody invented a new subdomain (which around
here is about every 5 minutes :D).

Which brings us to how things work now.

manage_forward_zones and manage_reverse_zones are now mandatory for BIND
management. The items listed in these values will directly map into
zone files. Hosts will go into their "best fit" as far as zone files.
To illustrate this:

If my settings looked like this:

manage_forward_zones:
~ - 'foo.example.com'
~ - 'bar.foo.example.com'

The host 'baz.bar.foo.example.com' would go into the
'bar.foo.example.com' zone whereas the host 's1.foo.example.com' would
go into the 'foo.example.com' zone.

I hope everyone who is testing this out finds this to be much more
useful than the way it previously functioned. I know I sure do.

I'm going to go put most of this information onto the wiki.

- --
John Eckersberg
Production Operations
Red Hat, Inc.

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org

iD8DBQFIJEfAO5VSO/Qqm+gRAngqAJ9C9aL9fBYASJRQBAh+nw3mqrINDACgtGg9
E9KrC9JkAhg9tRka7vHiFuc=
=93hk
-----END PGP SIGNATURE-----

_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


Applied, thanks!

--Michael


_______________________________________________
et-mgmt-tools mailing list
et-mgmt-tools@redhat.com
https://www.redhat.com/mailman/listinfo/et-mgmt-tools


All times are GMT. The time now is 08:50 AM.

VBulletin, Copyright ©2000 - 2014, Jelsoft Enterprises Ltd.
Content Relevant URLs by vBSEO ©2007, Crawlability, Inc.