10-17-2001 01:23 PM - edited 03-08-2019 08:53 PM
Hello,
Inside users can start connections and surf the web fine. However, they cannot access web server sites located internally. The internal sites can be accessed fine externally. DNS servers reside externally. It appears the internal sites resolve the site's internal address correctly, then die. Infact, a webserver cannot pull up it's own address or a site of a server next to it, but can hit any site outside. DNS issue?
Thanks!
10-17-2001 02:19 PM
Yes this is a DNS issue. What you have to do is create a internal DNS server to serve your internal network to your websites located behind the firewall. Make usre you set your workstations with the internal DNS sever first then the external DNS. Hope this helps.
10-17-2001 02:30 PM
Thanks for your help! I take it I would have to do this regardless, since we are going to put the mail servers behind the pix. Otherwise, different domains would not be able to email each other if they both reside behind the firewall.
10-17-2001 02:31 PM
if you are using a PIX Firewall, just issue some alias commands, and your done....
10-17-2001 02:35 PM
Would the alias commands be instead of adding an internal DNS? Also, could I use the "net" alias technique where as aliasing the entire subnet?
10-18-2001 03:17 PM
alias (inside) "InT_IP" "Ext_IP" 255.255.255.255
Set the servers DNS address to a server on the outside. Do an nslookup and look what you see
The PIX does the work for you
10-19-2001 07:48 AM
From a security point of view you should use the solution wiht 2 seperate DNS servers. This would comply with the 'Defense In-Depth' approach. Using a single DNS forces you to reveal more information that you should.
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