Currently Being ModeratedFeb 13, 2013 12:04 PM (in response to mike.it)
if your web server is not responding when browsing via name on the LAN and browsing via IP address works
it's probably a DNS problem
Currently Being ModeratedFeb 13, 2013 12:48 PM (in response to mike.it)
You are probably running your own internal DNS server, probably in order to run Open Directory. If you like many have used the same company domain name for the internal network as your website uses externally then this is a common configuration called a 'Split Horizon DNS'.
The outside i.e. the Internet will be using a DNS server on the Internet to resolve your website e.g. www.company.com often this domain record is hosted by your ISP or web hosting firm. Your internal network is using your Mac server. What you need to do is add a record to your internal DNS server for www.company.com with the correct external public IP address. This way when internal users ask your internal DNS server to resolve that name it will answer correctly.
Currently Being ModeratedFeb 13, 2013 12:52 PM (in response to John Lockwood)
Thank you John. I'll look into this and see if this was the problem.
Currently Being ModeratedFeb 14, 2013 11:27 AM (in response to mike.it)
Currently Being ModeratedFeb 14, 2013 11:46 AM (in response to mike.it)
Check the following.
1. On a Mac on your internal LAN, what is the IP address of the DNS server it is using. This is probably your Mac server. If it is the Mac server then do the next check.
2. On the Mac server is the DNS service running. If so does it have a DNS zone (aka. Domain) defined the same as the domain name of the external web server. If the webserver is www.company.com then the domain name/zone is company.com. It does not have to have the same domain defined but if it does (as I suspect) then it needs a www.company.com A record (aka. machine record) defined which needs the external IP address of web site.
So if your web servers Internet IP address is 22.214.171.124 then you would need on your internal Mac DNS server a machine record linking www.company.com to 126.96.36.199
Try using Network Utility on the Mac server to lookup your webserver e.g. www.company.com
Currently Being ModeratedFeb 14, 2013 4:16 PM (in response to John Lockwood)
Lol...After fixing one issue, another one came up. This time it has to do with the name I am using. For example:
www.exmaple.com and tm1.example.com (both are hosted with different ips)
Since they are both using the same name: exmaple.com, I cannot access the www.exmaple.com, but I can access the tm1.example.com
You have been a great help John, is there anyway to fix this?
Currently Being ModeratedFeb 14, 2013 8:53 PM (in response to mike.it)
From your diagram tm1.example.com looks like it is an internal server, you therefore need to define it on your internal Mac DNS server as an A (machine) record with the IP address being the internal private IP address.
I am guessing it is a Time Machine server.
If you want to use two different names for the same server (and therefore same IP address), the first name uses an A (machine) record, the second name uses a Cname (alias) record and points to the first name.