creating a dnsresource-record at the root of a zone should allow fqdn=

Bug #1562919 reported by LaMont Jones on 2016-03-28
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
MAAS
High
Unassigned

Bug Description

This works: maas test dnsresource-records create name=@ domain=maas rrtype=txt rrdata=foo

This fails, and should be equivalent:
maas test dnsresource-records create fqdn=maas rrtype=txt rrdata=meh

Note that fqdn=@.maas just feels wrong, and should probably not be supported, but fqdn=$name_of_domain should resolve to name=@, domain=domain, regardless, since we cannot put the data in the parent zone if we are authoritative for the child.

Related branches

Changed in maas:
milestone: none → 2.0.0
importance: Undecided → High
status: New → Confirmed
LaMont Jones (lamont) wrote :

It's actually more complicated:

When foo.example.com is a domain that we know about, then fqdn=foo.example.com needs to separate into (name=@, domain=example.com)

When the domain bar.example.com is created and RRsets exist for bar.example.com, dnsresource.{name,domain} need to be updated to accept the insertion.

There should never be entries (name=baz, domain=example.com) when the domain baz.example.com exists in Domain.

LaMont Jones (lamont) wrote :

1) models.dnsresource.separate_fqdn needs to learn to check Domain.objects to see if fqdn is defined in the DB, and behave correctly. (name=@, domain=orig_fqdn)
2) domain creation needs to check for dnsresource records for fqdn==domain.name and migrate those to the new domain, and adjust the names.

Changed in maas:
status: Confirmed → 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