Bing9 PTR Zone error : multiple RRs of singleton type
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Designate |
Fix Committed
|
Undecided
|
Kiall Mac Innes |
Bug Description
Hi
With Designate V2, a user should be able to change the PTR of his own floating IPs. This feature doesn"t work with bind9 at the moment.
Designate generates the following zone file :
-------
root@devstack-
$ORIGIN 4.24.172.
$TTL 3600
4.24.172.
1410969503 ; serial
3600 ; refresh
600 ; retry
86400 ; expire
3600 ; minimum
)
4.24.172.
4.24.172.
4.24.172.
3.4.24.
-------
As you can see there are 2 SOA and 2 NS records. This is problematic with Bind9. Bind9 complains with
Sep 17 15:58:22 XX named[3155]: zone 4.24.172.
Sep 17 15:58:22XX named[3155]: zone 4.24.172.
If I edit manually the zone file and remove the duplicate entries, everything work as expected.
According to this doc : http://
Changed in designate: | |
milestone: | none → juno-rc1 |
Changed in designate: | |
assignee: | nobody → Jordan Pittier (jordan-pittier) |
Changed in designate: | |
assignee: | Jordan Pittier (jordan-pittier) → Kiall Mac Innes (kiall) |
I am facing this bug with the floating IP API, ie I make curl call to /v2/reverse/ floatingips