Invalid MX record during recordset create/update cause ZONE to enter in Error state
Bug #1927304 reported by
kiran pawar
This bug affects 2 people
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
In Designate it is not possible to create an MX (Mail) record without a . (dot) at the end of fqdn. Which is the way it should be per RFC.
However, Designate allows users to update the MX record and omit/remove the . (dot) at the end of fqdn.
Case 1)
openstack recordset create --record "20 xxxx.test.com" --type MX zone_id mail2.test.com.
Case 2)
openstack recordset create --record "20 xxxx.test.com." --type MX zone_id mail2.test.com.
openstack recordset set --record "20 xxxx.test.com" --type MX zone_id recordset_id
In either of case 1 or 2, causes the zone to be stuck in PENDING and go to ERROR at some point, because the backend server (Bind) cannot fetch the zone from Designate-mdns.
Fix proposed to branch: master /review. opendev. org/c/openstack /designate/ +/790000
Review: https:/