hostname dns resolution not updated on vm restart


Craig Rubendall
 

I have a 2 job (vm) deployment, client and server. In the client, I'm referencing the server host via <index>.<job>.<network>.<deployment>.microbosh, ex. 0.serverNode.default.client-server-deployment.microbosh.

This all works great. I was testing Bosh handling of failover, so I killed the server vm. Bosh correctly restarted the vm. The VM came up with a new IP address.

However, the dns entry for that hostname was not changed after the restart. Now, my client can't connect to the server via that name.

Is this expected behavior? Am I doing something wrong?

Join cf-bosh@lists.cloudfoundry.org to automatically receive all group messages.