[2.0, 2.1] update docs to explain how to disable reverse dns generation for a subnet

Bug #1634294 reported by Nathaniel W. Turner
16
This bug affects 3 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
High
Graham Morrison

Bug Description

It seems MAAS configures BIND to serve a zone for every subnet it discovers. However, some nodes may have additional interfaces connected to subnets not under MAAS control, and DNS queries for PTR records in those subnets should really be forwarded to the upstream DNS servers.

If there is a way to tell MAAS to not serve these zones, it's not easy to find.

Versions:
maas 2.1.0~beta2+bzr5454-0

Revision history for this message
LaMont Jones (lamont) wrote :

There is, and it's clearly not well documented.

Using the CLI, you can say:
    maas SESSION subnet update ID rdns_mode=0
Where ID is the subnet id, probably found from something like:
    SUBNET_CIDR=10.0.3.0/24
    maas SESSION subnets read | jq -r '.[] | select(.cidr == "'$SUBNET_CIDR'").id'

Valid values for rdns_mode are:
    2: (default) -- generate reverse DNS, and a parent zone containing any rfc 2317 glue if needed
    1: generate reverse DNS, but no parent glue zone (they're doing that)
    0: do not generate reverse DNS

Leaving this bug open as a documentation bug.

tags: added: maas-docs
summary: - MAAS wants to serve authoritative reverse DNS for every subnet it finds
+ [2.0, 2.1] update docs to explain how to disable reverse dns generation
+ for a subnet
Changed in maas:
status: New → Triaged
importance: Undecided → High
Revision history for this message
LaMont Jones (lamont) wrote :

See also bug #1634595.

tags: added: docteam
Changed in maas:
assignee: nobody → Graham Morrison (morrisong)
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
Revision history for this message
Nathaniel W. Turner (nturner) wrote :

Were the docs updated?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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