Bing9 PTR Zone error : multiple RRs of singleton type

Bug #1370621 reported by Jordan Pittier
6
This bug affects 1 person
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-15h-55m17-09-14:/var/log# cat /opt/stack/data/designate/bind9/4.24.172.in-addr.arpa._484147f6-644a-43ce-9b3f-cbeb8202d7a7.zone
$ORIGIN 4.24.172.in-addr.arpa.
$TTL 3600

4.24.172.in-addr.arpa. IN SOA ns1.devstack.org. email.example.io. (
    1410969503 ; serial
    3600 ; refresh
    600 ; retry
    86400 ; expire
    3600 ; minimum
)

4.24.172.in-addr.arpa. IN NS ns1.devstack.org.

4.24.172.in-addr.arpa. IN SOA ns1.devstack.org. email.example.io. 1410969503 3600 600 86400 3600
4.24.172.in-addr.arpa. IN NS ns1.devstack.org.
3.4.24.172.in-addr.arpa. IN PTR toto.lol.com.
------------------------------------------------------------------------------------------------------------------------------

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.in-addr.arpa/IN: loading from master file /opt/stack/data/designate/bind9/4.24.172.in-addr.arpa._484147f6-644a-43ce-9b3f-cbeb8202d7a7.zone failed: multiple RRs of singleton type
Sep 17 15:58:22XX named[3155]: zone 4.24.172.in-addr.arpa/IN: not loaded due to errors.

If I edit manually the zone file and remove the duplicate entries, everything work as expected.

According to this doc : http://www.brandonhutchinson.com/multiple_RRs_of_singleon_type.html the duplicates entries are an error.

Changed in designate:
milestone: none → juno-rc1
Revision history for this message
Jordan Pittier (jordan-pittier) wrote :

I am facing this bug with the floating IP API, ie I make curl call to /v2/reverse/floatingips

Changed in designate:
assignee: nobody → Jordan Pittier (jordan-pittier)
Revision history for this message
Kiall Mac Innes (kiall) wrote :
Changed in designate:
status: New → In Progress
Changed in designate:
assignee: Jordan Pittier (jordan-pittier) → Kiall Mac Innes (kiall)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (master)

Reviewed: https://review.openstack.org/119768
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=3caefe64ee06cba5c02dd2cedeb01337fff15a50
Submitter: Jenkins
Branch: master

commit 3caefe64ee06cba5c02dd2cedeb01337fff15a50
Author: Kiall Mac Innes <email address hidden>
Date: Mon Sep 8 15:02:58 2014 +0100

    Backends need to implement c/u/d_recordset

    The current code means the central generate SOA/NS records are
    not provisioned, nor or any records create via the V2 API.

    Change-Id: I49dc3dda9d4b49305646a8b222165abaa3506959
    Closes-Bug: 1366821
    Closes-Bug: 1370621

Changed in designate:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.