Server Fault is a question and answer site for system and network administrators. Join them; it only takes a minute:

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I am currently running an authorative Bind9 DNS server for a bunch of domains. This authorative server currently replicates to a couple of slaves which are then used to meet the subnet requirement for DNS. The server is currently installed on a bare metal machine with a static WAN IP for itself.

I'd like to move this this server behind a NAT into a virtual machine. Since I don't know all that much about DNS I was wandering: are there any special constraints I need to be aware of when running an authorative DNS behind a NAT? Can I share an IP and route just bind specific ports or do I need to reserve and route a full IP for the DNS services?

share|improve this question
up vote 6 down vote accepted

Nope. I don't see why you couldn't just do it by forwarding port 53 for TCP and UDP and then run the DNS server from the forwarding IP address...

Incoming Ports:

TCP 53
UDP 53

Outgoing Ports:

TCP 53
UDP 53
share|improve this answer
If the NAT is stateful, then running out of memory is a risk. Other than that, it should work. – kasperd Mar 27 '15 at 17:25

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.