yahoo-eng-team team mailing list archive

[OpenStack Infra <1715842@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/504349
Committed: https://git.openstack.org/cgit/openstack/neutron/commit/?id=59f5e37ff419af33bc7dbffd35ef98e6990dec24
Submitter: Zuul
Branch:    master

commit 59f5e37ff419af33bc7dbffd35ef98e6990dec24
Author: Jens Harbott <j.harbott@xxxxxxxx>
Date:   Tue Sep 12 11:23:06 2017 +0000

    Fix documentation for DNS resolver config
    
    We need to correctly describe what is really happening: The dnsmasq
    processes in the DHCP agent act as forwarding masquerading resolvers for
    the instances in their particular subnets.
    
    Change-Id: I50ef9f488eb1efb8f709b75537ca4a4e9efce75a
    Closes-Bug: 1715842


** Changed in: neutron
       Status: In Progress => Fix Released

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

Title:
  Wrong information about DNS resolution in admin guide

Status in neutron:
  Fix Released

Bug description:
  In the section "Name resolution for instances" (doc/source/admin
  /config-dns-res.rst) the functional description for case 2 and 3 is
  wrong.

  In both cases, the DHCP agents do not offer the mentioned IP addresses
  to the instances. Instead, the DHCP agents offer the list of IP
  addresses of DHCP agents in the respective subnet to the instances in
  that subnet. The DHCP agents then run dnsmasq as a forwarding and
  masquerading resolver, forwarding DNS requests from the instances to
  the configured IP addresses, i.e. to the ones configured in
  ``dnsmasq_dns_servers`` in case 2 and to the ones configured in
  ``/etc/resolv.conf`` on the host in case 3.

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