I've skimmed through 4.0 sources and they didn't look too different from
3.x in this sense.
Perhaps I need to dig deeper.
Thanks,
Valentine
On 28.08.2017 20:15, Harshad Nakil wrote:
There is no point in making external DNS resolution of private IP space. Open
contrail DNS was designed to hav
There is no point in making external DNS resolution of private IP space. Open
contrail DNS was designed to have DNS functionality for private networks.
For external connectivity you should still use Designate. you can still make
contrail DNS as authoritative DNS for public network in Designate
Hi Robert,
Thanks for sharing your experience and your advices.
On 28.08.2017 18:24, Van Leeuwen, Robert wrote:
Only thing I forgot to mention:
The Contrail implementation has one thing going for it: it allows for working
reverse DNS with duplicate IP space.
(e.g. multiple tenants are using 19
Only thing I forgot to mention:
The Contrail implementation has one thing going for it: it allows for working
reverse DNS with duplicate IP space.
(e.g. multiple tenants are using 192.168.1.0/24)
You will not be able to set that up with anything else.
(Note that you cannot extend this outside o
> Consider you have a cluster with >=3 control nodes running (let's call
>them Cn). Think you also have a Virtual DNS configured which allows
> dynamic records from a vRouter agent (that's the default).
>
>
>I would expect all of C1, C2 and C3 to resolve both "foo" and "bar".
>H
Hi all,
I've asked this on #dev, but perhaps this mailing list is a more
appropriate place.
Consider you have a cluster with >=3 control nodes running (let's call
them Cn). Think you also have a Virtual DNS configured which allows
dynamic records from a vRouter agent (that's the default).
