Re:A Server Naming Scheme
by Total_Meltdown on Wednesday July 09, 2014 @11:10PM
(#8013385)
I have run into this at least twice this week alone with both Nginx and HAProxy pointing at Amazon Elastic Load Balancers. Amazon occasionally rotates out IPs for ELBs, so everything's working fine for weeks and then boom, now we're having a bad day.
[ Parent
| on HN ]
Re:A Server Naming Scheme
by aalbertson on Friday July 11, 2014 @11:54PM
(#8023664)
As a rule, NEVER EVER use CNAME's within AWS on Route53. You should always use their A Alias function. This provides near instant changes when you need to adjust a record. This only works on aws resources, but it is a great feature they built in.
Re:A Server Naming Scheme
by Total_Meltdown on Saturday July 12, 2014 @09:57PM
(#8026385)
I totally agree. In these two specific cases, R53 + ELB wasn't going to work for us though, because of reasons. (I don't think I can go into specifics, but they're actual reasons.) Our workaround was reloading the configs (which triggers a DNS cache flush on both Nginx[1] and HAproxy[2]) once every couple of minutes.
I know, I know, I hate it too. We're working on it. Just wanted to share the workaround.
[1] http://wiki.nginx.org/CommandLine#Loading_a_New_Configuratio...
[2] http://www.mgoff.in/2010/04/18/haproxy-reloading-your-config...