3143d86b69
Updates for patchset 2 review comments Changed link depth of main Planning index and added some narrative guidance Added planning/openstack as sibling of planning/kubernetes Related additions to abbrevs.txt Added max-workers substitution to accomodate StarlingX/vendor variants Signed-off-by: Ron Stone <ronald.stone@windriver.com> Change-Id: Ibff9af74ab3f2c00958eff0e33c91465f1dab6b4 Signed-off-by: Stone <ronald.stone@windriver.com>
24 lines
1.0 KiB
ReStructuredText
Executable File
24 lines
1.0 KiB
ReStructuredText
Executable File
|
|
.. kss1491241946903
|
|
.. _internal-dns-resolution:
|
|
|
|
=======================
|
|
Internal DNS Resolution
|
|
=======================
|
|
|
|
|prod-os| supports internal DNS resolution for instances. When this feature
|
|
is enabled, instances are automatically assigned hostnames, and an internal
|
|
DNS server is maintained which associates the hostnames with IP addresses.
|
|
|
|
The ability to use hostnames is based on the OpenStack DNS integration
|
|
capability. For more about this capability, see
|
|
`https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html
|
|
<https://docs.openstack.org/mitaka/networking-guide/config-dns-int.html>`__.
|
|
|
|
When internal DNS resolution is enabled on a |prod-os| system, the Neutron
|
|
service maintains an internal DNS server with a hostname-IP address pair for
|
|
each instance. The hostnames are derived automatically from the names assigned
|
|
to the instances when they are launched, providing |PQDNs|. They can be
|
|
concatenated with a domain name defined for the Neutron service to form fully
|
|
|FQDNs|.
|