On 09/03/15 20:51, Gal Sagie wrote:
I am not sure if this address what you need specifically, but it would
be worth checking these
two approved liberty specs:
1)
https://github.com/openstack/neutron-specs/blob/master/specs/liberty/internal-dns-resolution.rst
2)
https://github.com/openstack/neutron-specs/blob/master/specs/liberty/external-dns-resolution.rst
Thanks Gal,
So I see that from the bp [1] the fqdn will be configurable for each and
every port ?
I think that this does open up a number of interesting possibilities,
but I would also think that it would be sufficient to do this on a
subnet level?
We do already have the option of setting nameservers per subnet - I
assume the data model is already implemented - which is interesting -
because I don't see that as part of the information that is sent by
dnsmasq so it must be coming from neutron somewhere.
The domain suffix - definitely is handled by dnsmasq.
On Thu, Sep 3, 2015 at 8:37 PM, Steve Wormley <openst...@wormley.com
<mailto:openst...@wormley.com>> wrote:
As far as I am aware it is not presently built-in to Openstack.
You'll need to add a dnsmasq_config_file option to your dhcp agent
configurations and then populate the file with:
domain=DOMAIN_NAME,CIDR for each network
i.e.
domain=example.com <http://example.com>,10.11.22.0/24
<http://10.11.22.0/24>
...
-Steve
On Thu, Sep 3, 2015 at 1:04 AM, Maish Saidel-Keesing
<mais...@maishsk.com <mailto:mais...@maishsk.com>> wrote:
Hello all (cross-posting to openstack-operators as well)
Today the setting of the dns suffix that is provided to the
instance is passed through dhcp_agent.
There is the option of setting different DNS servers per
subnet (and and therefore tenant) but the domain suffix is
something that stays the same throughout the whole system is
the domain suffix.
I see that this is not a current neutron feature.
Is this on the roadmap? Are there ways to achieve this today?
If so I would be very interested in hearing how.
Thanks
--
Best Regards,
Maish Saidel-Keesing
__________________________________________________________________________
OpenStack Development Mailing List (not for usage questions)
Unsubscribe:
openstack-dev-requ...@lists.openstack.org?subject:unsubscribe
<http://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://openstack-dev-requ...@lists.openstack.org?subject:unsubscribe>
http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev
--
Best Regards ,
The G.
--
Best Regards,
Maish Saidel-Keesing
__________________________________________________________________________
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
