MAAS

Cannot specify additional nameservers for reverse zones

Bug #1680537 reported by LaMont Jones
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Wishlist
Unassigned
MAAS 2.3.x

Bug Description

There is no way to specify additional NS RRs for reverse DNS.

If I try the obvious (and probably the best/correct) approach of creating the reverse DNS domain (name=1.168.192.in-addr.arpa) then I get:

Apr 6 08:49:36 maas named[14362]: loading configuration from '/etc/bind/named.conf'
Apr 6 08:49:36 maas named[14362]: /etc/bind/maas/named.conf.maas:48: zone '1.168.192.in-addr.arpa': already exists previous definition: /etc/bind/maas/named.conf.maas:12
Apr 6 08:49:36 maas named[14362]: reloading configuration failed: failure

When creating the DNS configuration, MAAS should merge any reverse DNS Domain objects in with the auto-generated reverse domains.

See original description
Tags: dns
Andres Rodriguez (andreserl)
Changed in maas:
milestone: none → 2.3.0
LaMont Jones (lamont)
description: updated
Revision history for this message
Andres Rodriguez (andreserl) wrote :

Please provide steps to reproduce and more in depth information of what/how you are trying to achieve it.

Changed in maas:
status: New → Incomplete
Revision history for this message
LaMont Jones (lamont) wrote :

One question that comes up from time to time is "how do I specify a secondary nameserver for a MAAS controlled domain?" -- The answer is to add an NS RR to the domain [maas SESSION dnsresource-records create name="@" domain="maas" rrtype=ns rrdata="fqdn.of.secondary."]. While this works for any so-called forward zone (those with a Domain object), there is no way to do this for the reverse zones (which are synthesized from the Subnet object).

This synthesis has some other issues as well, particularly if MAAS is controlling one or more subnets within another subnet that it controls.

See also Bug# 1680567

tags: added: dns
LaMont Jones (lamont)
Changed in maas:
importance: Undecided → Wishlist
Andres Rodriguez (andreserl)
Changed in maas:
milestone: 2.3.0 → 2.3.x
status: Incomplete → Triaged
Revision history for this message
Adam Collard (adam-collard) wrote :

This bug has not seen any activity in the last 6 months, so it is being automatically closed.

If you are still experiencing this issue, please feel free to re-open.

MAAS Team

Changed in maas:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.