Hi Kim,
Thanks for trying the feature out! There are 2 levels of Neutron
integration with DNS:
1. Integration with Neutron's own internal DNS service. In short, ports
get a DHCP lease from a dnsmasq instance associated to their network. This
dnsmasq instance also assigns DNS attributes to the port, which are shown
to the user in the dns_assigment dictionary returned by the API. It
contains a FQDN, that is the concatenation of the port's dns_name and the
dns_domain defined in neutron.conf. The purpose of the dns_assignment
attribute is exclusively to show to the user the DNS attributes that
dnsmasq assigns to the port.
2. Integration with external DNS services (OpenStack Designate being the
reference implementation). If this integration is enabled, a port will be
known to an external DNS service by the FQDN that results from
concatenating its dns_name atribute and its network's dns_domain. This
latter attribute has no influence whatsoever in the port's dns_assignment.
In the latest release, Pike, we also added a dns_domain attribute to ports.
But again, it only has an effect on the external DNS service, with no
effect on dns_assigment
I hope this helps. Please feel free to ping me in #openstack-neutron. My
IRC nickname is mlavalle
Regards
Miguel
On Fri, Oct 6, 2017 at 7:50 AM, Kim-Norman Sahm
wrote:
> I've tried to upgrade my testing environment to ocata but i have the
> same issue...
>
> does anybody has an idea?
>
> regards
> Kim
>
>
>
> Am Freitag, den 29.09.2017, 09:32 +0200 schrieb Kim-Norman Sahm:
> > Hi,
> >
> > i'm currently testing the integration of designate and i found the
> > dns integration on neutron:
> > https://docs.openstack.org/newton/networking-guide/config-dns-int.htm
> > l
> >
> > In this example the value "dns_domain = example.org." is set in the
> > neutron.conf.
> > if i create a port with the "--dns_name fancyname" it is assigned to
> > the domain example.org: fancyname.example.org.
> >
> > if i set another domain name in another network "neutron net-update
> > --dns-domain anotherdomain.org. net2" and create a port in this
> > network the dns records is still in the example.org. domain.
> > is there a way to overwrite the global dns domain in a project and
> > inherit the dns-domain to the ports in this network?
> >
> > Best regards
> > Kim
> > Kim-Norman Sahm
> > Cloud & Infrastructure(OCI)
> > noris network AG
> > Thomas-Mann-Straße 16-20
> > 90471 Nürnberg
> > Deutschland
> > Tel +49 911 9352 1433
> > Fax +49 911 9352 100
> >
> > kim-norman.s...@noris.de
> > https://www.noris.de - Mehr Leistung als Standard
> > Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel
> > Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB
> > 17689
> >
> >
> >
> >
> >
> > __
> > OpenStack Development Mailing List (not for usage questions)
> > Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubs
> > cribe
> > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
> Kim-Norman Sahm
> Cloud & Infrastructure(OCI)
> noris network AG
> Thomas-Mann-Straße 16-20
> 90471 Nürnberg
> Deutschland
> Tel +49 911 9352 1433
> Fax +49 911 9352 100
>
> kim-norman.s...@noris.de
> https://www.noris.de - Mehr Leistung als Standard
> Vorstand: Ingo Kraupa (Vorsitzender), Joachim Astel
> Vorsitzender des Aufsichtsrats: Stefan Schnabel - AG Nürnberg HRB 17689
>
>
>
>
>
> __
> OpenStack Development Mailing List (not for usage questions)
> Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
>
>
__
OpenStack Development Mailing List (not for usage questions)
Unsubscribe: openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
