yahoo-eng-team team mailing list archive

[Jimin Shin <2097212@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

I create a server in the subnet with --dns-publish-fixed-ip, so the
port's fqdn of the server is set to 'server-name.network-dns-doamin'.
However, the server's resolv.conf search domain is always set to the
neutron.conf dns_domain. I think it should be set to the network's
dns_domain.

Reproduction steps:
  1. Make a network with a --dns-domain option.
  2. Make a subnet for the network with a --dns-publish-fixed-ip option.
  3. Make a server in the network using cirros image.
  4. Check the server port's fqdn and the /etc/resolv.conf file in the server.

I'm using stable/2024.1.

** Affects: neutron
     Importance: Undecided
         Status: New

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

Title:
  Resolv.conf search domain is different from the network's dns_domain

Status in neutron:
  New

Bug description:
  I create a server in the subnet with --dns-publish-fixed-ip, so the
  port's fqdn of the server is set to 'server-name.network-dns-doamin'.
  However, the server's resolv.conf search domain is always set to the
  neutron.conf dns_domain. I think it should be set to the network's
  dns_domain.

  Reproduction steps:
    1. Make a network with a --dns-domain option.
    2. Make a subnet for the network with a --dns-publish-fixed-ip option.
    3. Make a server in the network using cirros image.
    4. Check the server port's fqdn and the /etc/resolv.conf file in the server.

  I'm using stable/2024.1.

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