creating a dnsresource-record at the root of a zone should allow fqdn=
Bug #1562919 reported by
LaMont Jones
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
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_
Related branches
lp:~lamont/maas/bug-1571621
- Mike Pontillo (community): Approve
-
Diff: 679 lines (+447/-26)10 files modifiedsrc/maasserver/dns/tests/test_zonegenerator.py (+18/-0)
src/maasserver/dns/zonegenerator.py (+12/-6)
src/maasserver/models/dnsdata.py (+55/-5)
src/maasserver/models/dnsresource.py (+25/-2)
src/maasserver/models/domain.py (+81/-0)
src/maasserver/models/staticipaddress.py (+14/-2)
src/maasserver/models/tests/test_dnsdata.py (+42/-10)
src/maasserver/models/tests/test_dnsresource.py (+45/-0)
src/maasserver/models/tests/test_domain.py (+137/-1)
src/maasserver/models/tests/test_staticipaddress.py (+18/-0)
Changed in maas: | |
milestone: | none → 2.0.0 |
importance: | Undecided → High |
status: | New → Confirmed |
Changed in maas: | |
status: | Confirmed → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
To post a comment you must log in.
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.