yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1891512@xxxxxxxxxxxxxxxxxx>]

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

** Changed in: neutron
       Status: Incomplete => Expired

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to neutron.
https://bugs.launchpad.net/bugs/1891512

Title:
  strange behavior of dns_domain with designate multi domain

Status in neutron:
  Expired

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/neutron/+bug/1891512/+subscriptions