Stale zone files cause incorrect DNS mapping

Bug #1383329 reported by Adam Collard
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
Expired
Undecided
Unassigned

Bug Description

I had a MAAS install which had multiple name mappings for a given IP address, in turn causing a node's name to be missing from DNS.

maas 1.7.0~beta7+bzr3266-0ubuntu1~trusty1

The node who was missing from DNS was galileo.

As you can see in https://pastebin.canonical.com/119017/ there were two mappings for 10.1.4.2. It was only maxwell that actually had that address, the zone.maas file was old and irrelevant. To fix it I moved the old zone files out of the way (there was another which contained a typo in the zone name) and restarted maas-clusterd, bind9 and apache2. At that point galileo was in DNS and resolving to the correct IP (10.1.5.12).

I remember having to change the FQDN of the node in question since it was .maas and not .local (.beretstack) as desired.

Tags: landscape
Revision history for this message
Adam Collard (adam-collard) wrote :

Note I subsequently filled in the correct value for "default domain for new nodes" in the settings.

Revision history for this message
Raphaël Badin (rvb) wrote :

Can you double check that the stale zone file was included from BIND's main config?

Revision history for this message
Adam Collard (adam-collard) wrote :

I saw from the logs that the stale zone files weren't being loaded by BIND but there was confusion(?) in the zone.1.10.in-addr.arpa file which didn't feature galileo

It seemed like the presence of galileo in the stale zone file prevented it from being included in either the PTR file or the beretstack zone file.

Revision history for this message
Julian Edwards (julian-edwards) wrote :

I'm a little confused by the description. Could you please produced a step by step guide to reproduce this?

Revision history for this message
Graham Binns (gmb) wrote :

Marking incomplete until we have a guide to reproduce the problem

Changed in maas:
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for MAAS because there has been no activity for 60 days.]

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