© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
@Nobuto,
All the traffic is now proxy through the rack controller (Please refer to the announcements on [1]). That means that all DNS, HTTP, Squid, etc, is now proxied.
The rack DNS is now configured very similar, with the exception that the zone management still remains in the Region, but the rack config defines all regions as forwarders. A rack config will look like this:
forwarders {
region-ip-1;
region-ip-2;
};
dnssec-validation no;
allow-query { any; };
allow-recursion { trusted; };
allow-query-cache { trusted; };
Where 'trusted' is the ACL of subnets/hosts that are allowed to access DNS from. Note that if the region/rack are in the same subnet as facing the machine, there's a possibility that both region/rack will be used as DNS resolvers for deployed machines
[1]: https:/
Anyway, let me know when you have a chance to investigate and see what would work for you on 2.5, given that proxying through the rack was a field requested feature, and this request has a potential to impact how this gets configured in split configurations.