MAAS packaging doesn't include maas-generated named.conf.options.inside.maas file

Bug #1275649 reported by Ante Karamatić on 2014-02-03
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Julian Edwards
maas (Ubuntu)
Undecided
Unassigned

Bug Description

By default, MAAS uses root DNS servers in bind. Access to root DNS servers is not always allowed. Bind supports defining forwarders. MAAS should set forwarders based on DHCP information (if MAAS server gets IP from DHCP; sounds weird but it is deployment we've seen) or there should be an element in web UI that woul populate bind's config option and restart bind daemon. What we are looking for in bind is:

 forwarders {
  192.168.1.1;
  192.168.1.2;
 };

Related branches

Ante Karamatić (ivoks) on 2014-02-03
description: updated
Raphaël Badin (rvb) wrote :

There is already support for that in MAAS (Added in revision 1729). The config option (that you can set using the CLI/API or the UI) 'upstream_dns' does exactly that: it adds a "forwarders {…}" statement in the DNS config.

Changed in maas:
status: New → Invalid

On Monday 03 Feb 2014 08:49:13 you wrote:
> There is already support for that in MAAS (Added in revision 1729).
> The config option (that you can set using the CLI/API or the UI)
> 'upstream_dns' does exactly that: it adds a "forwarders {…}" statement
> in the DNS config.
>
> ** Changed in: maas
> Status: New => Invalid

Beware that the packaging does not set this up yet, you have to configure
named.config.options manually at the moment so that it includes the forwarders
file that MAAS creates.

So, if I read Julian's comment correctly, even if you use maas' cli tool to set forwarders, bind will not use them?

Julian Edwards (julian-edwards) wrote :

Not unless you configure the /etc/bind/named.conf.options to include the /etc/bind/named.conf.options.inside.maas file.

Sadly, bind won't let you include a second options{} block in its config, hence these hurdles.

Julian Edwards (julian-edwards) wrote :

I am going to retarget this bug to the packaging to remind us to get that change in.

summary: - MAAS needs a way of defining DNS forwarders
+ MAAS packaging doesn't include maas-generated
+ named.conf.options.inside.maas file
Julian Edwards (julian-edwards) wrote :

And thinking about it, we need to write some code in maas to make it easier for packaging to insert the config.

Changed in maas:
status: Invalid → Triaged
importance: Undecided → High
milestone: none → 14.04
Julian Edwards (julian-edwards) wrote :

This is almost ready to be fixed; there's a dependent branch in maas waiting to land which is blocked on the iscpy package getting accepted into trusty.

Changed in maas:
assignee: nobody → Julian Edwards (julian-edwards)
status: Triaged → In Progress
Changed in maas:
status: In Progress → Fix Committed
Changed in maas (Ubuntu):
status: New → Confirmed
Changed in maas:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers