- Newest
- Most votes
- Most comments
Given that you have no control over the target DNS and you want to have a very strict allow-list of things that you can connect to you're going to need to set something up that verifies the validity of your allow-list against the firewall.
For example: Have a list (probably external to DNS Firewall) that has all of the site/DNS records that are allowed. Look each one up. If it is a CNAME, find the record that is returned and add that to the list and therefore to the firewall as well.
You could do this manually, but far better to automate it.
Note that this isn't going to be perfect. Even if you run it at one minute intervals you may have some clients blocked as changes occur. And it's entirely possible that the web pages that users are reaching are going to have other sites that they link to so there is a larger problem here. Restrictive allow-lists are always going to be a lot more work to maintain than is originally thought.
This feature is now available. You can enable Route 53 Resolver DNS Firewall to automatically skip the inspection of domains included in a domain redirection chain, such as Canonical Name (CNAME) and Delegation Name (DNAME), thus avoiding the need to explicitly specify each domain from the chain in your Route 53 DNS Firewall rules when allow-listing domains.
Relevant content
- asked 3 months ago
- asked 8 months ago
- asked 2 years ago
- asked 5 years ago
- AWS OFFICIALUpdated a year ago
- AWS OFFICIALUpdated 7 months ago
- AWS OFFICIALUpdated 2 years ago
- AWS OFFICIALUpdated a year ago