On 26/01/17 16:35, Alan McAlexander wrote:
> From zones.conf:
>
> zone "0.X.X.10.in-addr.arpa" {
> type master;
> file "/var/cache/bind/zones/db.0.X.X.10.in-addr.arpa";
> update-policy {
> grant rndc-key zonesub ANY;
> };
> };
> zone "hq.corp.viasat.com" {
> type master;
[..]
The in-addr.arpa zone here does not match the zone in your first
message, see my quoted response:
> On 26/01/17 00:38, Alan McAlexander wrote:
>> ;; flags: qr ra; ZONE: 1, PREREQ: 0, UPDATE: 0, ADDITIONAL: 1
>>
>> ;; ZONE SECTION:
>>
>> ;10.in-addr.arpa. IN SOA
>
> This indicates the zone is 10.in-addr.arpa, check that's what's
> configured in BIND. If you have a more specific zone, then change the
> subnet configuration (prefix length/netmask) in Foreman to match.
For the 0.X.X.10.in-addr.arpa zone, the subnet in Foreman should be
10.X.X.0 with a 255.255.255.0 or 24 bit prefix specified. It appears
that it's set to 8.
--
Dominic Cleal
[email protected]
--
You received this message because you are subscribed to the Google Groups
"Foreman users" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at https://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.
