-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
On Jun 19, 2008, at 3:43 PM, Dustin Black wrote:
Interesting. I see that there is some convention to the line return
and
the preceding dash that is both odd and poorly documented. I had:
It's YAML. YAML's datastructures are pretty well defined (at least in
the terms of yaml they are).
foo: blah # is a string variable called 'foo' with the value of 'blah'
foo:
- blah # is an array called 'foo' with an index[0] whose value is
'blah'
manage_forward_zones: 'domain.com'
But changing that to:
manage_forward_zones:
- 'domain.com'
seems to have solved the problem I've been having.
Thanks, James!
-Dustin Black
On Thu, 2008-06-19 at 15:35 -0400, [EMAIL PROTECTED] wrote:
Make sure you have something along the lines of this in your
/etc/cobbler/settings file:
manage_forward_zones:
- 'lab.mycompany.com'
James S. Martin, RHCE
Contractor
Administrative Office of the United States Courts
Washington, DC
(202) 502-2394
[EMAIL PROTECTED] wrote on 06/19/2008 03:17:53 PM:
Dustin Black <[EMAIL PROTECTED]>
Sent by: [EMAIL PROTECTED]
06/19/2008 03:17 PM
Please respond to
[EMAIL PROTECTED]; Please respond to
Fedora/Linux Management Tools <[email protected]>
To
[email protected]
cc
Subject
[et-mgmt-tools] Cobbler BIND DNS management confusion
I could use some help understanding Cobbler's management of BIND.
If I make any changes to the /etc/cobbler/named.template file and
run
'cobbler sync', I can clearly see that the changes that I make are
implemented in the /etc/named.conf file.
Now I've been attempting to create a zone template under a directory
created per the wiki ManageDns documentation
-- /etc/cobbler/zone_templates. I want to create a zone with
static A,
MX, and CNAME entries that are outside the scope of Cobbler's
management
for that zone. If I create the zone template and run 'cobbler
sync',
should I then expect Cobbler to add the zone information to the
named.conf file, as well as use the template to create an
appropriate
zone file under /var/named? This doesn't seem to happen.
If I try to add the zone information explicitly to
the /etc/cobbler/named.template file, named gives an error when
restarting that the /var/named/... zone file doesn't exist.
I then thought that maybe Cobbler wouldn't create the named.conf
zone
entry or the zone file until a Cobbler system entry existed for a
host
in the domain. I created a dummy system with a hostname in the
domain
in question and ran 'cobbler sync', but still no dice -- no zone
entry
and no zone file.
What more do I need to understand about how this BIND management
works?
At what point or under what circumstances is the zone information
generated?
Thanks in advance!
_______________________________________________
et-mgmt-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
_______________________________________________
et-mgmt-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.7 (Darwin)
iD8DBQFIWsyZ0LdOhWiSZUwRAvu7AKCGIYhgKy4qFwGm9UuD8jXUPdVHtQCfWe+S
LBIDFTWEKmqGrHBdD5dOGQw=
=8YQs
-----END PGP SIGNATURE-----
_______________________________________________
et-mgmt-tools mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/et-mgmt-tools
