We recently moved a MAC running File Maker Pro Server from the DMZ to the internal subnet (10.0.3.x) The reason for this is so we could eventually validate user information entered on the MAC against Active Directory. It is our understanding that in order for that to work, the MAC would need to be joined to the domain. So, the first step was to move it off the DMZ to the subnet.
The firewall has a NAT rule to direct traffic to the URL office.ourdomain.com to the correct place (ourdomain = the name of our domain). This works fine for external access. If you enter http://office.ourdomaiin.com
you get the correct page and links off that page work; entering http://office.ourdomain.com/filemaker
takes you to the correct page to select a database. However, internal access is not working. If I enter http://office
I can get the home page (and links work off that page). Entering http://office/filemaker
does not work.
We are running DNS internally on Server 2K3 R2. We forward to the router on 10.0.3.1 whicih in turn passes things on the the appropriate DNS server. This is working fine, except for the recent change of the MAC machine. I'm not a DNS expert. Our domain is a third level domain, sfo.ourdomain.com - don't know if that is the problem. I did create a host (A) record for the MAC.
How do I get DNS to resolve this correctly? Please let me know if you need additional information.