0

I host two websites that are accessable from the Internet by podcast.example.com. They are one-to-one NAT on an internal network. On the internal network, I would like to have the hosts type podcast.example.com into there browser and the request go to 192.168.168.240 instead of the public IP. I have 30-50 hosts on the network so going to everyone and modifying the host file is not really an option.

2
  • 1
    Short Version: Get a router that supports full hairpin routing, or setup local DNS entries for that host/domain. Aug 26, 2013 at 18:45
  • I support @techie007 's suggestion in a way: separate internal and external DNS servers, which is actually more secure anyway if implemented correctly.
    – MDMoore313
    Aug 26, 2013 at 18:53

2 Answers 2

1

Your description is a bit scary, in that the outside world has access to internal web servers. MDMoore's suggestion, about separate DNS servers, is accurate. I'd go one further and say that you should be hosting the web servers externally.

That being said, if you're forced to work with what you have, what you are seeking is the "view" feature in BIND9. Take a look at the following two links. Pay attention to the "acl" and "view" statements.

The short version of what this does is alters what is returned in response to a DNS query, based on the network address from where it was asked.

0

One solution is to set up your own DNS server.

This is quite reasonable solution for a network containing 30-50 hosts.

Not the answer you're looking for? Browse other questions tagged .