Question Locked

routing internal users to web servers in DMZ

0 helpful
9 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

My internal users are on private IPs (192.168.50.x/24), the web servers are on private as well(192.168.10.x/24) There is an ASA 5520 seperating them and the internet.

The issue is that when an internal user trys to hi our web server using the proper domain name it trys to get to the public IP which does not work because you cant use the same pipe out and in.

My question is that I need to know where to configure in the ASA to redirect these requests inside prior to them leaving the network or should this be corrected using pointers on the DNS server?

Thanks,

9 replies

by synner

Can they access the web server via IP? If they can, than you need to take a look DNS servers otherwise you'll need some configuration on the ASA.

by twindragon99

Yes they can see the web servers via IP. Also if they direct to the web servers using the internal share name then they can see the pages as well. it is only when they try to hit the public domain name.

by synner

The "public domain name" is not resolving to the IP address of the web server sitting in the DMZ. Are the clients pointing to a DNS server that you host or some other DNS server?

by twindragon99

it is an internal DNS, it looks like the way this conversation is going that you feel a new DNS entry will be the proper solution for this particular issue.

by synner

Do a reverse dns lookup on the ip address and see what returns. Do a forward lookup on the hostname and see what returns. The two has to match otherwise you will only hit the server that is returned on the forward lookup when you try to access it by hostname.

by cg it

depends on who's DNS server is authoritative for your FQDN and what address that DNS server says is that domain name. Also depends on forwarders in your DNS server.

A DMZ zone typically is a subnet between the public and your private network. Routers are used to create the DMZ zone. Your DNS server for your private network answers queries by users for resources on the private network. Queries that can not be answered by your DNS server are forwarded to servers listed in the forwarders of your DNS server. Those DNS servers either answer the query or put out a call to other DNS servers basically asking, Anyone know whois this domain name. If no DNS servers answer, then you get page can not be displayed. If a DNS server answers then the traffic is directed to that IP address.

In your case, the DNS request for your web site gets sent out to the internet. A DNS server that is authoritative for your FQDN needs to answer with your ISP public address. If this doesn't happen, then users can't find the web site.

Putting a DNS entry in your internat DNS server probably won't solve the problem because your FQDN is associated with a public IP address and that DNS server needs to answer. If your DNS server is authoritative for your FQDN, then your domain name registar DNS server listing should list your server.

by synner

The easiest solution, put a DNS entry for that fqdn in the hosts file that way you don't have to worry about SOA. If you are the SOA of the domain then a dns entry will solve your problem.

If this is an internal server that isn't connected to the internet and is only for internal machines, defining a zone and make it the SOA, adding the dns entry will solve your problem. Just gotta make sure this one doesn't replicate with any other servers.

by twindragon99

Thank you Syner, you were correct, my DNS was missing the entry for the domain. once added all users are now able to navigate properly.

This discussion is closed to new replies.