02-03-2016 09:07 AM - edited 03-12-2019 12:14 AM
We control our external DNS to the internet, and currently they sit outside of the firewall on public IPs. It's time to upgrade and I want to bring them inside the ASA and NAT them.
Maybe I'm looking at this too hard, but is it as simple as NAT'ing the existing public IPs to the new internal servers in the DMZ and allowing port 53 traffic through?
Thanks!
Solved! Go to Solution.
02-03-2016 09:08 AM
Sounds about right.
02-03-2016 07:26 PM
In addition to Johnson's comment, couple of other notes..
1. As these servers need to initiate DNS queries to Internet, make sure to allow DNS traffic only to Internet from DMZ (sourced from server pvt IPs).
2. You may be aware of this but you need to allow both tcp & udp for DNS traffic.
3. Make sure to block any connection initiated from these servers to your Internal IPs (using ACLs on DMZ).
hth
MS
02-03-2016 09:08 AM
Sounds about right.
02-03-2016 07:26 PM
In addition to Johnson's comment, couple of other notes..
1. As these servers need to initiate DNS queries to Internet, make sure to allow DNS traffic only to Internet from DMZ (sourced from server pvt IPs).
2. You may be aware of this but you need to allow both tcp & udp for DNS traffic.
3. Make sure to block any connection initiated from these servers to your Internal IPs (using ACLs on DMZ).
hth
MS
02-04-2016 07:18 AM
Thanks all!
#3... I still need to allow port 53 to/from my DCs for DNS forwarding, correct?
02-08-2016 07:45 PM
Hi Robert,
If your DCs are inside and using DMZ servers as forwarders, I don't see a need to open any ports. If your ASA version is pre 8.3 , you need static (Inside, DMZ) DCIP DCIP mask x.x.x.x and for 8.3 and after- the communication allowed by config.
hth
MS
02-12-2016 11:08 AM
Thanks guys! I got the crud and forgot to come back on here and update.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide