Re: Hard-coded domain name in diego etcd job

Amit Kumar Gupta

You should not change anything in your DNS servers. It is purely internal;
jobs that need to reach other services over the internal domain should be
colocated with consul_agents which will serve those DNS requests. It's all

On Mon, Aug 17, 2015 at 7:47 PM, Meng, Xiangyi <xiangyi.meng(a)> wrote:

Then how should I config my DNS server? Which host/job’s IP should be
mapped to domain “”?

I also attached the etcd job log. Would you please help to take a look?



*From:* Gwenn Etourneau [mailto:getourneau(a)]
*Sent:* 2015年8月17日 18:51
*To:* Discussions about Cloud Foundry projects and the system overall.
*Subject:* [cf-dev] Re: Hard-coded domain name in diego etcd job

You not should change it, this domain is use only with consul as DNS.

Many component rely on it, uaa and so on.

Do you have some logs ?

On Mon, Aug 17, 2015 at 7:41 PM, Meng, Xiangyi <xiangyi.meng(a)>


I am trying to deploy diego 0.1402.0 into vShpere server to work with CF
210. However the deployment failed when creating job ‘etcd’ with following

*Error: cannot sync with the cluster using endpoints

I tried to change the domain name to my own domain name in diego yml file.
But it didn’t work. I found the domain name was hard-coded in

Could anyone tell me how to work around it?



Join to automatically receive all group messages.