Feature request
In general, our forward DNS servers are setup to our internet service provider’s DNS server.
But we’ve got an intranet DNS domain that should be accessible, too.
Since the default installation type of MAAS is the snap installation nowadays, I’d like to get a solution back again to use our local intranet DNS server for selected zones.
Within snap, customizing the file below is not possible any more.
Solution before snap
Before upgrading from local MAAS installation to a MAAS snap installation (done on update from Ubuntu 18.04 to 20.04), I was able to add 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—
Current pains without this solution
My current workaround to forward everything to our local ActiveDirectory DNS-Server is causing Microsoft licensing (direct and indirect access to windows servers requires Windows client access licenses). So, new users always cause unnecessary costs…
More details also available at https://bugs.launchpad.net/bugs/1908449 with last status of recommending this requirement as a feature request here in this discussion.
