Forward DNS scenario not supported any more or missing documentation

Bug #1908449 reported by Jochen Wezel
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
MAAS
Invalid
Undecided
Christian Grabowski

Bug Description

Since upgrading from Ubuntu 18.04 to 20.04, the maas engine moved from local system into a snap module (currently MAAS v2.7.3).

Since it's a snap module, direct edit of resolv.conf doesn't work any more for adding DNS forwarding zones to a local DNS server for an internal domain

In past, I added following lines to /etc/bind/named.conf.local

----SNIP---
zone "my.active.directory.local" {
        type forward;
        forwarders {
               192.168.2.4;
               192.168.2.5;
        };
};
----/SNIP---

Alternatives like adding a domain and adding some NS entries pointing to my DNS servers didn't work for me - maybe because it's not a supported feature or I did the wrong setup.

Please provide some documentation how to setup a forwarding domain in DNS server of MAAS!

Revision history for this message
Christian Grabowski (cgrabowski) wrote :

MAAS does allow and have documentation around adding global forwarders, however it does not currently support per-zone forwarding. The documentation can be found here: https://maas.io/docs/snap/2.9/ui/managing-dhcp#heading--set-a-dns-forwarder or for your specfic version, here: https://maas.io/docs/snap/2.7/cli/managing-dhcp#heading--set-a-dns-forwarder

Changed in maas:
assignee: nobody → Christian Grabowski (cgrabowski)
Changed in maas:
status: New → Incomplete
Revision history for this message
Jochen Wezel (jwezel) wrote :

> however it does not currently support per-zone forwarding
That's exactly the point: zone forwarders (e.g. for intranet domain) are missing

Revision history for this message
Björn Tillenius (bjornt) wrote :

I think this is a feature request, and not a bug. While what you did worked, it's not something that was supported. It doesn't really scale when you have multiple region controllers, since you have to manually make sure all the servers are in sync.

Would you mind filing this as a feature request at https://discourse.maas.io/c/features/15?

Changed in maas:
status: Incomplete → New
status: New → Incomplete
Revision history for this message
Jochen Wezel (jwezel) wrote :
Revision history for this message
Jochen Wezel (jwezel) wrote :

@Björn: thank you very much so far!

Revision history for this message
Jochen Wezel (jwezel) wrote :

@cgrabowski: thank you for all digging into documentation and code so far!

Revision history for this message
Björn Tillenius (bjornt) wrote :

Thanks for the discourse post! I'm going to close this bug, and then we'll see if we can fit this in. I'm hoping it's not too much work supporting this use case. @cgrabowski, can you look into this?

Changed in maas:
status: Incomplete → Invalid
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.