-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Michael DeHaan wrote:
denmat wrote:
> Hi,
>
> I am trying to let cobbler manage my DNS (and dhcp) but I am having
> issues with getting it to work with dns.
>
>
.. snip ..
> cat modules.conf
> [serializers]
> settings = serializer_yaml
> distro = serializer_yaml
> profile = serializer_yaml
> system = serializer_yaml
> repo = serializer_yaml
> [authentication]
> module = authn_denyall
> [authorization]
> module = authz_allowall
> [dns]
> module = manage_bind
> [dhcp]
> module = manage_isc
>
> cat named.template
> options {
> listen-on port 53 { 127.0.0.1; 10.61.236.1; };
> directory "/var/named";
> dump-file "/var/named/data/cache_dump.db";
> statistics-file "/var/named/data/named_stats.txt";
> memstatistics-file "/var/named/data/named_mem_stats.txt";
> allow-query { localhost; localnets; };
> recursion yes;
> };
>
> logging {
> channel default_debug {
> file "data/named.run";
> // severity dynamic;
> severity debug;
> };
> };
>
> zone "." IN {
> type hint;
> file "named.ca";
> };
>
> $zone_include
>
> cat zone.template
> \$TTL 300
> @ IN SOA $cobbler_server.
>
admin.gdn.example.com (
> $serial ; Serial
> 600 ; Refresh
> 1800 ; Retry
> 604800 ; Expire
> 300 ; TTL
> )
>
> IN NS $cobbler_server.
>
>
> $host_record
>
>
gdn.example.com. MX 10
mail.example.com.
>
> cat
zone_templates/gdn.example.com
> \$TTL 300
> @ IN SOA $cobbler_server.
>
admin.gdn.example.com (
> $serial ; Serial
> 600 ; Refresh
> 1800 ; Retry
> 604800 ; Expire
> 300 ; TTL
> )
>
> IN NS $cobbler_server.
>
>
> $host_record
>
>
gdn.example.com. MX 10
mail.example.com.
>
> It doesn't seem to pick up anything in the zone_templates directory.
> If I put crap in the zone file it doesn't provide any error
> notification. If I move /etc/named.conf and run cobbler sync the
> /etc/named.conf file is recreated but it doesn't seem to read the
> $zone_include.
>
> Cobbler doesn't seem to have any logging options available apart from
> the logging of clients attaching to it.
/var/log/cobbler/cobbler.log exists, but you're never going to get a log
about a template file not being
set up correctly, as cobbler can't realistically model all of your
configurations.
> Setting debug to named doesn't
> point to any issues (but you can see it doesn't read any of the
> cobbler managed zone files).
>
> Any idea where I'm going wrong?
>
John Eckersberg might be able to offer some more info as he implemented
the BIND management
features, though site-specific configurations are always a bit difficult
to debug with knowing all of the items
in play.
> Regards,
> denmat
> _______________________________________________
> cobbler mailing list
> cobbler(a)lists.fedorahosted.org
>
https://fedorahosted.org/mailman/listinfo/cobbler
>
Hi denmat,
Two things jump out at me, and I noticed that neither of them were
mentioned in the wiki so I went ahead and added notes on them (shame on me):
1. Your syntax for manage_reverse_zones is wrong, instead of
'236.61.10.in-addr.arpa' replace it with just '10.61.236'. Might be
worth an RFE to make it accept either syntax.
2. Make sure your systems have the hostname attribute set on all
interfaces that you want records generated for. If a particular
interface does not have a hostname set it is excluded from the zone files.
Hope that helps, lemme know if that fixes your problem.
- --
John Eckersberg
Production Operations
Red Hat, Inc.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (GNU/Linux)
Comment: Using GnuPG with Fedora -
http://enigmail.mozdev.org
iEYEARECAAYFAki+3nIACgkQdxt4pd4ztYstxQCgprlKrwVo7k1P8RY5v0MgbTcR
BUYAoLYDL2UHQXKe0owL3jKJO0LSrS2U
=DS49
-----END PGP SIGNATURE-----