strange behavior of dns_domain with designate multi domain

[Satish Patel]

I am running ussuri on centOS8 and trying to integrate neutron with designate but i am seeing strange behavior so want to verify if its bug or not.

I have two network net-foo and net-bar and i have mapped following designate domain name with each network

$ openstack network set net-foo --dns-domain foo.com.
$ openstack network set net-bar --dns-domain bar.com.

my /etc/neutron/neutron.conf pointing

dns_domain = example.com.

I spun up VM with net-foo and net-bar nothing happened, i didn't see any A record in DNS.

now changed /etc/neutron/neutron.conf point to dns_domain = foo.com.

I spun up VM with both net-foo and net-bar and noticed foo.com. got A record but not bar.com. (look like it has to match with dns_domain in neutron.conf)

Now i changed /etc/neutron/neutron.conf to dns_domain = com.

Now both net-foo and net-bar working fine, and i can see both created A records in DNS.

Question is do i need to use dns_domain = . (dot) to meet each domain in worlds like foo.com foo.net foo.org foo.io etc.?

is this normal behavior because i haven't seen any document talking about this.

[Bence Romsics (bence-romsics)]

I'm no designate expert, but last time I played with it, I realized that reading neutron-server logs can help me understand where neutron-server couldn't progress when I was expecting a new A recordm but didn't get it. One particular case I remember (not the exact conditions though, sorry) is that you may need to create the zones you want the A records in, like: openstack zone create ...

Another thing that helped me was to realize that I better go through both of these documents (in this order) because the 2nd builds on the first:

https://docs.openstack.org/neutron/latest/admin/config-dns-int.html
https://docs.openstack.org/neutron/latest/admin/config-dns-int-ext-serv.html

[Satish Patel (satish-txt)]

Thanks for reply,

I do have both zone in designate foo.com and bar.com and if i want to use both then i need to add dns_domain = . (ending dot) in neutron.conf to make it work which is not documented so wanted to verify if this is right way to do.

otherwise everything is working fine no issue, my VM automatically getting register in designate DNS.

[Bence Romsics (bence-romsics)]

Sorry I'm not able to answer your question. It may be easier to find answers to your questions if you can find somebody familiar with the designate integration on the #openstack-neutron channel.

[Dr. Jens Harbott (j-harbott)]

I don't understand what you are trying to do. When you talk about seeing things "in DNS", are you talking about designate or about the neutron internal DNS servers on the DHCP agents? Can you show a complete list of commands needed to reproduce your issue?

[Launchpad Janitor (janitor)]

[Expired for neutron because there has been no activity for 60 days.]

[Satish Patel (satish-txt)]

Hey!

sorry for delay,

I am not sure this is neutron issue or designated issue. so far look like neutron issue. It's been long time so hard to re-capture logs but i can setup quick devstack to test it out. In short If i want to host DNS service in my cloud for multiple domains like foo.com, bar.com and abc.net various TLD (top-level-domain) then i have to use following setting in neutron to make it work otherwise it won't work for multiple TLD domain.

dns_domain = .