Designate

Wildcard NS records are not allowed by backend like BIND

Bug #1533299 reported by James Li
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Designate
Fix Released
Critical
James Li
Designate mitaka-3 "m3"

Bug Description

Designate allows user to add a NS record with a wildcard domain name, for example *.bind.com.

But backend like BIND does NOT allow this. If a customer adds such a NS record to a zone using BIND backend, BIND will reject the zone and all future updates to the zone will fail to propagate (and will show up as such in Designate) until the wildcard NS record is removed.

See original description
James Li (james-li-3)
description: updated
James Li (james-li-3)
Changed in designate:
assignee: nobody → James Li (james-li-3)
Tim Simmons (timsim)
Changed in designate:
status: New → Triaged
importance: Undecided → Critical
milestone: none → mitaka-3
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (master)

Fix proposed to branch: master
Review: https://review.openstack.org/268362

Changed in designate:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (master)

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

commit fe3f7df4df91802e6daedd1ca7550c3c775d577f
Author: James Li <email address hidden>
Date: Thu Jan 14 13:13:19 2016 -0600

    Fix wildcard NS record

    BIND does not allow a NS record having a wildcard name,
    e.g. *.example.com.

    Change-Id: I358d26a10129305bcfef91f5577c1f6ae08701d2
    Closes-Bug: #1533299

Changed in designate:
status: In Progress → Fix Released
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to designate (stable/liberty)

Fix proposed to branch: stable/liberty
Review: https://review.openstack.org/276182

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to designate (stable/liberty)

Reviewed: https://review.openstack.org/276182
Committed: https://git.openstack.org/cgit/openstack/designate/commit/?id=2df661f97479ac7ac27279a23991505a13a4e466
Submitter: Jenkins
Branch: stable/liberty

commit 2df661f97479ac7ac27279a23991505a13a4e466
Author: James Li <email address hidden>
Date: Thu Jan 14 13:13:19 2016 -0600

    Fix wildcard NS record

    BIND does not allow a NS record having a wildcard name,
    e.g. *.example.com.

    Change-Id: I358d26a10129305bcfef91f5577c1f6ae08701d2
    Closes-Bug: #1533299

tags: added: in-stable-liberty
Revision history for this message
Thierry Carrez (ttx) wrote : Fix included in openstack/designate 2.0.0.0b3

This issue was fixed in the openstack/designate 2.0.0.0b3 development milestone.

Revision history for this message
Davanum Srinivas (DIMS) (dims-v) wrote : Fix included in openstack/designate 1.0.2

This issue was fixed in the openstack/designate 1.0.2 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote :

This issue was fixed in the openstack/designate 1.0.2 release.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

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