<div dir="ltr"><br><br><div class="gmail_quote"><div dir="ltr">On Wed, Sep 7, 2016 at 6:47 PM Turbo Fredriksson <<a href="mailto:turbo@bayour.com">turbo@bayour.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">On Sep 7, 2016, at 11:03 PM, Brandon Sawyers wrote:<br>
<br>
> <a href="https://openstack.nimeyo.com/83652/openstack-neutron-designate-tenancy-neutrons-integration?start=0#a_list_title" rel="noreferrer" target="_blank">https://openstack.nimeyo.com/83652/openstack-neutron-designate-tenancy-neutrons-integration?start=0#a_list_title</a><br>
<br>
"and the zone from the private network".<br>
<br>
Meaning, "there can be only one"! And it's automatic (this<br>
part: "the network is set to publish all port FQDNs to Designate").<br>
<br>
So, it is as I described - you set the "dns_domain" on the network<br>
and "dns_name" on the port, and it's automatic. But more than that<br>
you can't do. I.e., your original question<br>
<br>
What I'd like to be able to do is have each private network (or project<br>
maybe?) be able to control the domain names attached to their guests.<br>
<br>
Can only be done with Designate, not Neutron.<br>
<br>
Unless what you want is what I _do not_ - one network, one domain.<br>
If you want one network, several different domains, then you can't do<br>
that this way. You have to do it manually.<br>
<br>
> | dns_assignment | {"hostname": "test", "ip_address": "10.0.0.15",<br>
> "fqdn": "<a href="http://test.cloud.int" rel="noreferrer" target="_blank">test.cloud.int</a>."} |<br>
<br>
So that's the internal Neutron/DNSMasq DNS I was talking about. Don't know<br>
how much use that actually is, but if I remember the docs I read months ago<br>
(briefly! :) about this, that _SHOULD_ be possible to use internally within<br>
the instances.<br>
<br>
That's the private IP..<br>
<br>
> | dns_name | test |<br>
> | fixed_ips | {"subnet_id": "3a6bedd6-3c8f-4bfb-8e2b-60db8c711afd", "ip_address": "10.0.0.15"} |<br>
<br>
Do you have "dns_domain" on the network that's the "father" of the subnet<br>
"3a6bedd6-3c8f-4bfb-8e2b-60db8c711afd"?<br>
<br>
> | network_id | a42ea9bf-2aa8-4097-a0be-fce7db9a2707<br>
> |<br>
<br>
That network.<br>
<br>
> | dns_domain | test.internal. |<br>
> | id | a42ea9bf-2aa8-4097-a0be-fce7db9a2707 |<br>
<br>
Ah, yes. Good.<br>
<br>
> | 30efcfd8-220c-44fd-ac4e-da85efc3a497 | test.test.internal. | A | 172.21.14.62 | ACTIVE | NONE |<br>
<br>
> Everything that should be there seems to be. Even the floating ip of a<br>
> previous iteration.<br>
<br>
So where's the floating IP [port] entry for _this_ instance? And does<br>
that have "dns_name" set? <br></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
<br>
So let's recap:<br>
<br>
1. You have the "dns_domain" set on the network.<br>
2. You have the "dns_name" set on [one of] the port(s) - the private<br>
one.<br>
<br>
So you have an entry for "test.test.internal." (correct - first "test" is<br>
the "dns_name" in the port, the "test.internal." is from the network)<br>
pointing to "172.21.14.62" (wrong!).<br>
<br>
It _should_ (if I'm reading your output correctly) have pointed to<br>
"10.0.0.15" (because that's the IP of the port).<br>
<br>
But you say "of a previous iteration"! What do you mean? If you delete<br>
the port(s) etc, is the domain updated? I.e., is that entry/line I quoted<br>
above gone?<br></blockquote><div>That's a floating ip that I set in an earlier test but didn't release before killing the instance. It shouldn't be there. If I had released before deleting the entry wouldn't be there.<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
If yes, what happens if you DON'T add a floating IP when you add (create)<br>
everything back again? Is the domain pointing to the private then? Maybe<br>
the latest port overwrites the previous? Because I'm assuming that you're<br>
adding the floating IP after the private IP.. ?<br></blockquote><div> No, it never points at the private ip, but this is what I want.<br><br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<br>
I can't remember if I ever tested having two identical A records pointing<br>
to two different IPs (I just have very vague, nagging feeling that that<br>
isn't possible - I'm probably wrong, but the feeling is still there)..<br>
In Bind, that's perfectly legal, but I don't know if Designate supports that.<br>
--<br>
I love deadlines. I love the whooshing noise they<br>
make as they go by.<br>
- Douglas Adams<br>
<br>
</blockquote></div></div>