Install and configure for Ubuntu in designate
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Designate |
Triaged
|
High
|
Unassigned | ||
Bug Description
This bug tracker is for errors with the documentation, use the following as a template and remove or add fields as you see fit. Convert [ ] into [x] to check boxes:
- [ ] This doc is inaccurate in this way: ______
- [x] This is a doc addition request.
- [ ] I have a fix to the document that I can paste below including example: input and output.
If you have a troubleshooting or support issue, use the following resources:
- Ask OpenStack: http://
- The mailing list: http://
- IRC: 'openstack' channel on Freenode
-------
Release: 6.0.0.0b3.dev6 on 2017-12-18 19:22
SHA: 0740dbb53d8e3d5
Source: https:/
URL: https:/
| Filippo DiNoto (fdinoto) wrote | #1 |
| Changed in designate: | |
| status: | New → Triaged |
| importance: | Undecided → High |
| tags: | added: docs low-hanging-fruit |
I've had a lot of difficulty understanding the documentation and I'd like to offer some suggestions.
The install/config documents that comprehensively explain how to get designate working using the BIND9 backend makes gratuitous use of 127.0.0.1 which I assume is because it is intended to get a standalone dev/poc working asap.
Personally I would like to see the docs changed to a scenario that does not use 127.0.0.1 wherever possible because it makes it difficult to grasp exactly what each part of the configuration is doing.
I realize that there are other sections in the docs that do not use 127.0.0.1 everywhere but those all seem to be based on PowerDNS which causes uncertainty for anyone who is familiar with bind but trying to learn designate. It introduces a double-unknown that completely destroys my confidence in what I already know :)