MAAS does not add node to DNS Domain

Bug #1571621 reported by Trevor G Francis on 2016-04-18
This bug affects 1 person
Affects Status Importance Assigned to Milestone
LaMont Jones

Bug Description

MAAS Version 2.0.0 (beta2+bzr4920)

Steps to reproduce:

Add DNS domain.
Assign Node to DNS domain during ready state, acquire and deploy node. Node is never added to DNS domain (or any other domain for that matter) and thus cannot be reached by DNS.

Related branches

Andres Rodriguez (andreserl) wrote :

Hi Trevor,

With the information you have provided it is pretty impossible to figure out what's wrong. So, pleasE:

1. attach logs (/var/log/maas/*.log)
2. attach syslog
3. attach /etc/bind/maas/*
4. Check that /etc/resolv.conf is pointing to MAAS Region


Changed in maas:
status: New → Incomplete
milestone: none → 2.0.0
LaMont Jones (lamont) wrote :

What domain did you add (and what are the names of the other domains)?

LaMont Jones (lamont) wrote :

At a minimum, delegations are not being added in the parent zones: if the maas domain is, and the user creates after creating secondaries and integrating into his DNS infrastructure, hosts in will not be resolvable unless the maas dns server is queried.

Changed in maas:
assignee: nobody → LaMont Jones (lamont)
Changed in maas:
status: Incomplete → Fix Committed
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