I have looked into similar issues but found a slight variation in my problem for which there may be a different potential solution.
Scenario: (All servers running Server2003 with AD)
Private network 'my.domain.com' setup on 192.168.0.X with 192.168.0.1 being the private side interface on the Netgear NAT router/firewall. The public address is configured with static IP address, 184.108.40.206 (for arguments' sake). The company website is registered publically with DNS for domain 'www.help.me.com'
. The website is actually hosted internally on an IIS server on 192.168.0.2. with forwarding on the router to this address for external access requests.
The problem is this: External clients are able to resolve to www.help.me.com
but internal clients (logging in to my.domain.com) are not. When I enter www.help.me.com
in the address bar from a client machine on the internal side it resolves to the external gateway of the NAT router, bringing up a login dialog to enter router configuration. Running a ping on www.help.me.com
also resolves to the public IP address on the router. If I type in the 192.168.0.2 address in the address bar it resolves to the website as it should.
I have entered the local DNS server address (hosted on PDC on 192.168.0.3) as the primary DNS in DHCP so all clients know of the internal DNS server before attempting to lookup on the external DNS provided by the ISP. However, when attempting to configure a record in the local DNS i am stumped on how to configure a record pointing to 'www.help.me.com'
in the primary zone of my.domain.com. The cname only works on aliases and not on domain names (i think...), A records require a netbios name etc etc. I added a record of this in the reverse lookup primary zone but also to no avail.
QUESTION: HOW DO I ENTER A RECORD FOR 'WWW.HELP.ME.COM'
DOMAIN NAME IN THE LOCAL DNS SERVER FOR CLIENTS ON MY.DOMAIN.COM (along with a number of laptops that pickup 192.168.0.x addresses from the local DHCP server) TO RESOLVE BEFORE GOING OUT TO EXTERNAL DNS FOR LOOKUP?
As a work around I have modified local hosts files to resolve locally, and it does the trick just nicely. Problem is, folks come in with their laptops, pick up an IP address for their machines from local DHCP and get on the internet (workgroup mode and not joining my.domain.com). I cant keep this regime of manually editing hosts files on such a transient population of hosts so I would prefer to fix up local DNS to provide internal users with the abililty to logon to the company website internally.
many thanks in advance...