> 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". > However, with data flows shown above, C1 would know nothing of "foo", > and C3 won't resolve "bar". > > What do I miss here? Nothing! It indeed works like this. It will only update the active master and active slave. In a 3 node setup this is a problem since the third inactive node will not get any updates.
We eventually switched to using designate for DNS usage (via a link-local service) because we had quite a lot of headaches with the contrail DNS implementation. This also gives OpenStack users an interface to manage DNS records which is a nice addition. One other noteworthy thing is that the DNS vrouter functionality is not supporting the full RFC like queries over TCP which is needed for large DNS result sets. I have not looked at the 4.0 product yet but IMHO this part of the product needs either a LOT of attention / rework or it should be ripped out of the product if there is no capacity to support it properly. Cheers, Robert van Leeuwen _______________________________________________ Dev mailing list Dev@lists.opencontrail.org http://lists.opencontrail.org/mailman/listinfo/dev_lists.opencontrail.org
