I use AWS to run instances of our DNS Engines so I have to configure both DNS (UDP 53) and tcp port 53 to allow inbound access to the engine instances but it's only because I'm running DNS servers in AWS. For anything use, DNS flows properly as the traffic is outbound in those instances.
I suppose I don't find having to configure TCP and UDP as problematic since I've automated instance creation and teardown with the AWS EC2 apis and ansible so it's one script to instantiate, one script to tear down and it includes the security group creation, configuration and subsequent deletions. -a Adrian Beaudin Principal Architect, Special Projects Nominum, Inc. o: +1.650.587.1513 adrian.beau...@nominum.com ________________________________________ From: dns-operations [dns-operations-boun...@dns-oarc.net] on behalf of Fred Morris [m3...@m3047.net] Sent: Wednesday, January 28, 2015 6:38 PM To: dns-operati...@dns-oarc.net Subject: Re: [dns-operations] AWS footnote: DNS firewall rules are UDP only On Wed, 28 Jan 2015, Paul Hoffman wrote: > Are there any Route 53 people on this list? If so, this should be fixed ASAP. I'm not sure that this is a Route 53 issue, I was trying to run my own DNS (for "other" purposes). I would characterize it as a tragically uninspired UX. -- Fred Morris _______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs _______________________________________________ dns-operations mailing list dns-operations@lists.dns-oarc.net https://lists.dns-oarc.net/mailman/listinfo/dns-operations dns-jobs mailing list https://lists.dns-oarc.net/mailman/listinfo/dns-jobs
