I ran into a problem this morning where resuming a suspended VM does not refresh the DNS zone.
I suspect I could use the "ResumeComplete" event trigger to kick DNS in some way, but I thought I should ask advice.
Does anyone have a way to handle this? For us, I have told users to suspend their VMs at night and not to worry about the DNS. It's handled, but it seems like DNS just disappears for suspended instances.
REPLICATE IT
- Create a DNS Zone and point it at a Farm Role.
- When you issue the suspend command DNS records are removed from the zone record even before the system is fully suspended.
- Once the WebUI says the instance is suspended, it is not completely suspended, but in 20 seconds or so it reaches that state in AWS.
- On resume Scalr will fire the "ResumeComplete", but this does not seem to refresh the DNS zone.