anoncontractor

3 ms·

1. 1.▲
   by anoncontractor 8y ago

   I don’t work for AWS, but I’ve talked to people that work on Route53. Amazon just isn’t willing to support it, none of their large customers care about it enough it seems like. Plus DNSSEC has all sorts of issues, some of which people in th
2. 2.▲
   by anoncontractor 8y ago

   “If they were using support tickets and manually implemented changes by hand then there would not be an account.” Your contracting team may not have a DNS account, but the contractor that deals with DNS changes certainly does. The point is
3. 3.▲
   by anoncontractor 8y ago

   Yes, this is pretty close to how this agency does things. Your contracting team files a support request for a record change and a manager from within the agency approves. The contractor that owns DNS changes then goes and does it. This make
4. 4.▲
   by anoncontractor 8y ago

   For sure, you can totally make something like this happen, but again that means writing and securing a bespoke system. If you’re a team managing your AWS infrastructure with Terraform, it sucks to have to write a totally different system (a
5. 5.▲
   by anoncontractor 8y ago

   As someone who has recently dealt with a major government agency, the requirement of DNSSEC means that agencies can’t use Route53 as it doesn’t support DNSSEC. This makes it much less likely that an agency will use something like Terraform