Internal links and redirects for mesos not redirecting properly

[tayzlor]

For example if you visit http://10.0.1.11:5050 and .13 is the master. Mesos will try redirecting you, it will redirect to -

http://ip-10-0-1-13.eu-west-1.compute.internal:5050/

Which is not resolvable through the browser / VPN.

A similar thing occurs if you click on a link from the web interface to one of the frameworks. We probably need to set -

/etc/mesos-master/hostname
/etc/marathon/conf/hostname

to addresses that we can resolve properly.

[wallies]

could not we not use internal consul dns to resolve these e.g. master1,2,3.consul

[tayzlor]

not sure that would be resolvable through the browser, if we just point them to the private_ip (e.g. 10.0.1.11:5050) that would work while connecting through the VPN

[wallies]

true that. unless we link up the routing table with consul somehow.
http://docs.aws.amazon.com/AmazonVPC/latest/UserGuide/vpc-dns.html#vpc-dns-updating
http://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zones-private.html