Web Site Works externally, but not internally 1

[R3AP3R]

Ok being a network guy by nature, i was thrown into the fire of server administration.. so bare with me.

I have subdomains that are pointed to my external ip. If i try to access the site off the network, i can access it just fine. When i am within the lan, i cannot view page. In order for me to view page i need to manually edit my host file with FQDN as well as private ip of apache server.

I was reading up on various fixes which included named virtual host in apache, dns lan server, and also nat on a stick.

Im thinking since i have to manually edit hosts file with private ip of apache server, common sense tells me that i need a DNS lan server to resolve the hostname to its private ip, and not public, but not too sure if this is the best route to go. Any suggestions ?

 

[smah]

Yes, this is definately a DNS resolution problem. Do a tracert on that address & tell us what happens. A local/internal DNS server would certainly solve the problem, but might not always be required. Sometimes it's only because your gateway device doesn't properly 'loopback' it's own public IP address. What's the gateway to the internet - a router appliance?

 

[R3AP3R]

i have a /30 between my cable modem and cisco 3640. On 3640 i have dhcp enabled as well as PAT. From there its going into a 3550 which then plugs into all my devices. (cable modem > Cisco 3640 > cisco 3550 > Lan computers / phones.) When i do a tracert from within the network it will comlete to its public IP, with the host file edited, it will complete to its private ip. Is split-dns another solution? ive also read quite a bit on issues where routers aernt able to "loopback" its own public ip address. When i hear loopback, automatically i think of virtual interface on routers..

 

[R3AP3R]

Currently i only have one /30 assigned to my cisco. What if i put that static on my apache server, and assign my cisco a different /30. That way when internal users try to reach the site, it will get query my isp dns server, and since its a completely diff subnet, it should have a route to it.

Im also looking into split-dns as a solution to this. Being able to install a local hostname resolution zone internally, and everything else externally sounds like it could work.. I gotta do some more reading.. later

 

[R3AP3R]

if you guys need a quick solution to this issue, this is what i did to resolve the problem.

Installed Simple DNS v5.0. Set up Nat Ip alias. Point internal lan clients to ip of machine running Simple DNS.

My cisco 3640 is not capapable of dns doctoring, so im looking into getting a pix, but for the meantime Simple DNS resolved this problem instantly.