can't update dns resource using cli
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
MAAS |
Fix Released
|
Medium
|
Newell Jensen | ||
2.6 |
Fix Released
|
Medium
|
Newell Jensen |
Bug Description
Created 'com' domain and added one dnsresources:
```
$ maas st dnsresources read domain=com
Success.
Machine-readable output follows:
[
{
"id": 98,
{
},
],
}
],
"fqdn": "163m.com",
},
]
```
Next, want to update it's fqdn:
```
$ maas st dnsresource update 98 fqdn=12com
Success.
Machine-readable output follows:
{
"address_ttl": null,
"id": 98,
"ip_addresses": [
{
"ip": "10.10.26.163",
},
},
{
}
],
}
],
"resource_
"fqdn": "163m.com",
"resource_uri": "/MAAS/
}
```
And update ip address also not works although the output says execute successfully.
```
$ maas sensetime dnsresource update 98 ip_address=
Success.
Machine-readable output follows:
{
"address_ttl": null,
"id": 98,
"ip_addresses": [
{
"ip": "10.10.26.163",
},
},
{
}
],
}
],
"resource_
"fqdn": "163m.com",
"resource_uri": "/MAAS/
}
```
Related branches
- Newell Jensen (community): Approve
-
Diff: 176 lines (+134/-5)2 files modifiedsrc/maasserver/api/dnsresources.py (+36/-4)
src/maasserver/api/tests/test_dnsresources.py (+98/-1)
- Blake Rouse (community): Approve
-
Diff: 176 lines (+134/-5)2 files modifiedsrc/maasserver/api/dnsresources.py (+36/-4)
src/maasserver/api/tests/test_dnsresources.py (+98/-1)
Changed in maas: | |
milestone: | 2.6.0rc2 → 2.7.0beta1 |
Changed in maas: | |
status: | In Progress → Fix Committed |
Changed in maas: | |
status: | Fix Committed → Fix Released |
I'd like to take a closer look at what you're doing here before calling this "Triaged".
But since I haven't had time to do that, I was first wondering why you are creating a "com" domain in MAAS. It seems potentially dangerous to tell MAAS it is authoritative for the "com." TLD.
If you create separate domains for each record you would like to represent under the "com" TLD, such as "example.com", why not create an "example.com" domain directly in MAAS? (You can use the `@` record to represent looking up "example.com" itself without a subdomain, just like in BIND.)