Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Was going to switch to route 53 while you guys were down and switch back, but the page says it'll take a day...Might as well just wait at that point. I know it's panic mode over there, but some kind of failover record would be awesome for when this happens in the future(or an option for one).


Everything related to DNS says it'll take a day but that's "worst case"... I've successfully transferred DNS for 5 Namecheap-registered domains to Route 53 since this all started a couple hours ago, and they're now up & running smoothly.

Their "update DNS server" page was acting a bit wonky, kept saying some of my nameservers were invalid when they weren't, but I eventually got them all switched.

This isn't a dig against Namecheap, it sounds like this attack is pretty bad, but for important domains Route53 just seems like a much better setup (geographically dispersed, different nameservers for each hosted zone, etc).


Yeah, Route53 isn't as feature rich though. Also I have the same problem, keeps giving me errors about bad nameservers. I guess I'll keep trying.


Hi, I work on Route 53, can you clarify; are you seeing a problem from your registrar when you try to move to Route 53? We're also always keen to hear about features customers would like.


Secondary DNS from a normal bind nameserver.


I second this. I'll add that Route 53 would need to respond to notifies for this to be useful.


It's definitely on our list, but in the meantime there is https://code.google.com/p/route53d/ which will let you translate an AXFR/IXFR from a bind server directly into Route 53 authenticated calls.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: