I've got a website somesite.com that we am hosting by myself network. I'm able to can get on from outdoors my network, but any computer systems on my small network cannot can get on by doing somesite.com. Internally it is simply accessible using http://computerdnsname:port/ .

I've got a Server 2008 r2 like a DNS server. I am unsure when the option would be a DNS server setting or perhaps a router setting. I am confident inside my place of work they solve this while using router, but I am unsure if my fundamental bestbuy router or my modem has the features needed to repair this issue.

Without additional particulars regarding your network setup, it's tough to create a definite determination, however it seems like this can be a router problem. Your internet site is solving towards the public IP of the router, as well as your router is not sending this traffic in the internal interface. (Rather, it assumes the visitors are destined for that router itself, and also the router drops this traffic.)

This can be a problem that I have had some knowledge about when confronted with OpenWrt, etc. It appears the common practice here's to complete NAT sending, etc. in line with the interface rather than the destination IP. I do not really accept this, because it causes the precise problem you are most likely going through.

If you are utilizing a router that utilizes or could be exhibited to aid OpenWrt, this can be a part of something similar to things i was using formerly within an iptables script (/etc/firewall.user):

WAN_IP=$(ifconfig $WAN | sed -n 's/ *inet addr:\([0-9.]*\).*/\1/p')
iptables -t nat -A prerouting_rule -p tcp --dport 80 -d $WAN_IP -j DNAT --to $DMZ_IP

The final time I checked out it was around the older "WhiteRussian" discharge of OpenWrt, and everything has transformed considerably since - but even just in the newest versions, as recorded in Firewall configuration, you can observe that things are still based on a needed src attribute - which "identifies the traffic source zone, must make reference to among the defined zone names". Ultimately, these rules are converted to and performed as iptables rules - therefore the above continues to be possible, but you need to do it directly. If you cannot use or aren't confident with a custom router firmware, you are most likely out-of-luck with this particular option...

If you are already hosting your personal internal DNS server (and when connected customers are set up for doing things, through DNS, etc.) - you could include an entry for the site around the internal DNS which directs the visitors to the correct local server rather than the router - basically getting rid of the router from being involved with local traffic for that site. (This appears just like a cleaner approach anyway.)

Minimal steps to obtain this working (utilizing a Home windows Server 2003 VM as reference, but ought to be almost if different under 2008):

In the DNS administration tool (dnsmgmt.msc), right-click "Forward Research Zones" and click on "New Zone...". Choose "Primary Zone". For "Zone title" go into the proper alternative for "somesite.com". You are able to accept other defaults, a minimum of for the time being.

Then, in this particular new zone, produce a new "A" record at least. Right-click the new zone, then click "New Host (A)...". Leave the very best "Title" area blank. Go into the local IP of the website around the local LAN, then finish by clicking the "Add Host" button on that dialog. As lengthy as the customers are by using this Home windows server since it's DNS server, you ought to be good-to-go.

Why not a simple host entry on each machine you want to can get on?