| opendevreview | Erik Olof Gunnar Andersson proposed openstack/designate master: Add inactive value to floating ip status https://review.opendev.org/c/openstack/designate/+/830549 | 01:18 |
|---|---|---|
| opendevreview | Arkady Shtempler proposed openstack/designate-tempest-plugin master: Import zone API changes: some refactoring and new test case https://review.opendev.org/c/openstack/designate-tempest-plugin/+/823682 | 09:59 |
| zigo | Hi there! It looks like we have some kind of working Designate thingy in our preprod env. I now wonder: | 15:33 |
| zigo | Should me manual "openstack zone create" our "main" zone that's used by the VMs? | 15:33 |
| frickler | zigo: define "used by the VMs". if you use neutron integration and set dns-domain for a network, then you need to create the matching zone manually, yes | 15:40 |
| zigo | frickler: That answers my question, thanks ! | 15:41 |
| zigo | frickler: Will "old" (ie: before the DNS server was up) VMs be added to the DNS, or only new VMs ? | 15:42 |
| zigo | I also searched how to do the reverse DNS PTRs, is this documented somewhere? | 15:42 |
| frickler | I don't think records for existing VMs will be created | 15:43 |
| zigo | Ok, will try creating new VMs then... :P | 15:44 |
| frickler | for PTRs, you need to set allow_reverse_dns_lookup, see https://docs.openstack.org/neutron/xena/admin/config-dns-int-ext-serv.html | 15:45 |
| frickler | zones there will be created by neutron, you just need to delegate them properly | 15:45 |
| zigo | Thanks. | 16:11 |
| johnsom | FYI: I have started an etherpad for PTG planning: https://etherpad.opendev.org/p/zed-ptg-designate | 16:36 |
Generated by irclog2html.py 2.17.3 by Marius Gedminas - find it at https://mg.pov.lt/irclog2html/!