2 ms·
The article says that Route 53 uses randomly generated name server names, so if at your registrar you are pointing your domain to Route 53 name servers, and the
by tzs 6y ago
The article says that Route 53 uses randomly generated name server names, so if at your registrar you are pointing your domain to Route 53 name servers, and then you remove the records for your domain at Route 53 but leave the record at your registrar pointing to Route 53, it is unlikely that another Route 53 customer could add your domain and get your traffic. Their randomly generated Route 53 name server names would probably not match yours.
I wonder how effective that actually is? As far as I know there is nothing in the DNS protocol like the "Host" header of HTTP that allows the name server to tell what name the client knows the name server by. Two differently named name servers will actually be distinct only if they have different IP addresses.
The question then is how many IP addresses does Route 53 have for name servers?
Ideally, you'd want to have a separate IP address for each customer's name server. Do any of the big hosting companies do that?
I'd expect that they could do it without needing a lot of extra IP addresses by giving each customer who has a static IP address for the hosts an option to have traffic to port 53 of that IP address transparently sent to the hosting provider's name servers along with tagging to let the name servers identify what IP address it was for so it can serve the right name data.
That would allow each customer to have as many apparently dedicated name servers as they have hosts with static IP addresses.
- vegardx 6y agoWhen you create a hosted zone in Route53 you have two options, either let them pick a delegation set for you at random, or request a delegation set upfront, which can be used when creating a hosted zone. You can create 100 delegation sets (until you reach a quota, which can be raised) per account. This would give you 100 possible combinations, rinse and repeat for more account and I'm sure you've exhausted all possible combinations rather quickly. You can also create more accounts programatically. The mitigations does make it negligible harder for someone to swoop in and take control over domains that currently have misconfigured name servers. But at that point the domains won't be resolving anything, so either the user don't care or aren't even using the domain.