Designate

Dynamic DNS update backend

Registered by Yury Konovalov

This blueprint has been superseded. See the newer blueprint "Dynamic DNS over HTTP Endpoint" for updated plans.

User may wish to use Designate to manage an existing zone hosted elsewhere. Standard DNS update protocol (RFC2136) is widely used for updating zone on remote DNS server and thus is a good choice. Separate Designate Backend needs to be implemented to send updates to remote DNS service via DNS update instead of managing local DNS servers.

Blueprint information

Status:
Complete
Approver:
None
Priority:
Undefined
Drafter:
Yury Konovalov
Direction:
Needs approval
Assignee:
None
Definition:
Superseded
Series goal:
None
Implementation:
Unknown
Milestone target:
None
Completed by
Tim Simmons

Related branches

Sprints

Whiteboard

RFC2136 sadly doesn't define a method for triggering "create zone" or "delete zone" , which is one of the key reasons behind the work going into "MiniDNS" - Which will use AXFR's to actually transfer the bulk of the data over the the final DNS server. Additionally, handling failure cases with DNS UPDATE queries will be incredibly difficult, to the point that we likely won't be able to do this reliably.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.