I have a domain and a WWW server within my network. I have one public address and running NAT on a router. Server is naturally port-forwarded. Let's say my domain is kitet.com so when anyone on the internet types kitet.com in a browser's address bar, a page from my server is shown. I need to configure my network in sucha way, so that when I am connected to it (from inside) I can also operate using my internet name (I am using some more services, WWW example chosen for simplicity).
Right now I can't connect to my site at all when I type my domain name in the browser, while being inside. I can connect from outside w/o problems.
I want to do this because I'm working mainly on my laptop, which is being moved between places, inside or outside my organization, and I require an SSL certificate that won't verify when i type e.g. 192.168.0.9, when inside my network. This is also for my employees and guests that won't be able to visit my site ONLY while within my network...
So there is summary of what i want and tried to do:
- My site kitet.com should work wherever I am, as kitet.com, not only local address
- No entries inside "hosts" file (or any other file on personal computers, devices and so on) should be necessary to make it work
- I already tried a linux router with kernel 2.2, where I added a PREROUTING entry, well, that worked, but I feel like all the traffic, that should go from e.g. my laptop to server is going through that router at all times, thereby generating unnecessary traffic on it. I dropped that approach.
- I could run a DNS on my Win 2012 server, only I don't know how to configure forward lookups to map my domain address to a computer within my network. I feel like this is my last option here, please advise how do I configure it.
EDIT: CASE STUDY
Imagine I'm in a train, or at a client's, accessing my kitet.com on port 443 to update my page, which is located on one machine, at the same time reading mail while connecting to the same kitet.com on port 110 which is in my LAN on another machine, at the same time demonstrating my projects on Team Server, which is - you guessed it - on yet another machine. I'm returning home and I STILL want to access kitet.com, without reconfiguring my mail program, to access servers at some 192.168.0.9 or a local name, without telling Visual Studio that TFS is now at some 192.168.0.10 or a different local name.
That's it, hope I made myself clear this time.