badg.us is running at 188.8.131.52 now, so the domain should point to it as well.
mrz owns this domain. I've created a record set in AWS. Since badg.us is hosted in AWS, it makes more sense to take advantage of Route53. @mrz, please can you point badg.us to: ns-1260.awsdns-29.org ns-1618.awsdns-10.co.uk ns-494.awsdns-61.com ns-873.awsdns-45.net Another option is for corporation to take ownership of the domain. We could file for that if you'd prefer. @Jan So that we can auto-scale, we should point this to a load balancer. I've created csa-badgus-production. Once I've confirmed that the load balancer works with badg.us, shall I point it at the load balancer? We can't achieve high availability without it.
Summary: Point badg.us to 184.108.40.206 → Move badg.us to Route53
The load balancer works... http://csa-badgus-production-1360536758.us-east-1.elb.amazonaws.com/en-US/
Nothing in this bug pointed to me and it was never on my radar. Are you ready to take the NS RRs for this domain?
Yep, we're ready to take them.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.