Open Stack

After doing more research I've become even more confused.

I'm not at all confident in my understanding of how internal dns is
supposed work anymore.

I've seen different slideshows and forum posts that seem to point out that
internal dns should be working exactly as I want it to. IE: I have a
private network that has dns_domain information set. Should I be able to
lookup that host via FQDN using the internal dnsmasq provided dns?

Apologies for the quick reply to my post, but I'm just trying to understand
how things should work.

Thanks,
Brandon

On Wed, Sep 7, 2016 at 9:42 AM Brandon Sawyers <brandor5 at gmail.com> wrote:

> Hello everyone:
>
> I'm wondering if there is a way to manage internal dns in mitaka other
> than setting dns_domain to a blanket domain in neutron.conf (that applies
> to all guests created across all projects/networks).
>
> What I'd like to be able to do is have each private network (or project
> maybe?) be able to control the domain names attached to their guests.
>
> For example projectX has two internal networks test and prod. The test
> network would have the dns_domain 'test.local.' associated with it, while
> prod would have 'prod.local.'
>
> Any new guest created on the test network would come up as
> guest1.test.local and be able to access guestX.test.local by name.
>
> Is this doable?
>
> If not, am I missing something obvious? It's starting to feel like I am.
>
> Thanks for the help!
> Brandon
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack/attachments/20160907/ac570f24/attachment.html>