Seting up internal websites/dns on server 03.

Krrose27 · 07-07-2008, 02:38 AM

Ok so I am playing around with server 03 here at my house. I am 16 and the closest i have come to actually playing around on servers where at my school.

My school has a setup where we can type in certian things and go to certian websites. if you type "techhelp" into a browser it takes you to our tech support forums. We have countless other items like this. Thing is they dont all run of one server the "domain" are redirecting to the ips i belive.

What i am hoping todo is to setup server 03 where i can do the same thing.

My router enables me to setup the DNS to pass out through dhcp.

So on the server system i have asagin two ips, ip1) 172.16.15.26 (ip2) 172.16.15.28 ; My router will then be pointed to those ip.

I now am trying to figure out how to setup the rest, I am not exactly sure how to do the forwards to opendns and also the local systems for serving.

Confused? I may need to retype this.

**djaburg** · 07-09-2008, 10:14 PM

I'm not sure I'm following the logic of using those particular IP addresses on your server. Normally on a dual NIC system, one is used for internet connectivity and one is used for LAN connectivity. Are you going to have multiple internal websites hosted or are you hoping to have the dns entries you're concerned with pointing to external servers?

Krrose27 · 07-09-2008, 11:49 PM

Ok i figured i messe up my explanation.

I have one server with the internal ip of 172.16.15.26.
I have a static ip from my ISP of (not mine) 97.101.41.51.

My server has a dns running on it. The server does a forward lookup to open dns.

On my router i have the dns pointing to 172.16.15.26 and another DNS server for backup (DHCP handiling this).

On the server i want to make a dns entry so when somone linked to my server inside my house will get redirected to the specified system.

eg. techhelp would point to 172.16.15.27 or anyother internal ip.

The thing is is that techhelp is not a real domain and when i build a reverse lookup and ping techhelp it returns nothing; however, if i ping "techhelp." i recivie the ping to the right IP, why must i put a ".", any ideas what i did wrong?

Does this explain it better?

tannerjohn · 07-12-2008, 07:14 AM

You need your own DNS name space running on your server, like "Home.local", or some such.
If you are hosting a website on this server, or other server on your private network, by the name of "techhelp.home.local" then add the DNS "A" record for "techhelp." pointing to 172.x.x.x

That DNS server needs to have "FORWARDERS" setup that are your ISP's public DNS servers.

All your internal clients need their DNS set to your Home.Local DNS server's IP address as their primary DNS server.

When a client goes to www.google.com their request hits your home.local DNS server....trys to resolve....can't...uses the forwarders to public DNS....finds it....resolves it.

When a client goes to techelp.home.local their request hits your home.local DNS server...resolves it.

07-07-2008, 02:38 AM	#1 (permalink)
Krrose27 Registered User Join Date: Jul 2008 Posts: 38 OS: Serv 03 R2 SP2, Mac Os X 10.5.4, XP Pro SP2, XP Home SP2, Ubuntu	Seting up internal websites/dns on server 03. Ok so I am playing around with server 03 here at my house. I am 16 and the closest i have come to actually playing around on servers where at my school. My school has a setup where we can type in certian things and go to certian websites. if you type "techhelp" into a browser it takes you to our tech support forums. We have countless other items like this. Thing is they dont all run of one server the "domain" are redirecting to the ips i belive. What i am hoping todo is to setup server 03 where i can do the same thing. My router enables me to setup the DNS to pass out through dhcp. So on the server system i have asagin two ips, ip1) 172.16.15.26 (ip2) 172.16.15.28 ; My router will then be pointed to those ip. I now am trying to figure out how to setup the rest, I am not exactly sure how to do the forwards to opendns and also the local systems for serving. Confused? I may need to retype this.

07-09-2008, 10:14 PM	#2 (permalink)
djaburg TSF Enthusiast Join Date: May 2008 Posts: 1,319 OS: XP SP3/Vista/7 Server 2K/2K3/2K8	Re: Seting up internal websites/dns on server 03. I'm not sure I'm following the logic of using those particular IP addresses on your server. Normally on a dual NIC system, one is used for internet connectivity and one is used for LAN connectivity. Are you going to have multiple internal websites hosted or are you hoping to have the dns entries you're concerned with pointing to external servers? __________________ Computers make it easier to do a lot of things, but most of the things they make it easier to do don't need to be done. The inherent vice of capitalism is the uneven division of blessings, while the inherent virtue of socialism is the equal division of misery.

07-09-2008, 11:49 PM	#3 (permalink)
Krrose27 Registered User Join Date: Jul 2008 Posts: 38 OS: Serv 03 R2 SP2, Mac Os X 10.5.4, XP Pro SP2, XP Home SP2, Ubuntu	Re: Seting up internal websites/dns on server 03. Ok i figured i messe up my explanation. I have one server with the internal ip of 172.16.15.26. I have a static ip from my ISP of (not mine) 97.101.41.51. My server has a dns running on it. The server does a forward lookup to open dns. On my router i have the dns pointing to 172.16.15.26 and another DNS server for backup (DHCP handiling this). On the server i want to make a dns entry so when somone linked to my server inside my house will get redirected to the specified system. eg. techhelp would point to 172.16.15.27 or anyother internal ip. The thing is is that techhelp is not a real domain and when i build a reverse lookup and ping techhelp it returns nothing; however, if i ping "techhelp." i recivie the ping to the right IP, why must i put a ".", any ideas what i did wrong? Does this explain it better?

07-12-2008, 07:14 AM	#4 (permalink)
tannerjohn Registered User Join Date: Jun 2008 Posts: 43 OS: vista 64bit	Re: Seting up internal websites/dns on server 03. You need your own DNS name space running on your server, like "Home.local", or some such. If you are hosting a website on this server, or other server on your private network, by the name of "techhelp.home.local" then add the DNS "A" record for "techhelp." pointing to 172.x.x.x That DNS server needs to have "FORWARDERS" setup that are your ISP's public DNS servers. All your internal clients need their DNS set to your Home.Local DNS server's IP address as their primary DNS server. When a client goes to www.google.com their request hits your home.local DNS server....trys to resolve....can't...uses the forwarders to public DNS....finds it....resolves it. When a client goes to techelp.home.local their request hits your home.local DNS server...resolves it. __________________ Hope it helps. My notes: headtreez.com/site/JohnsHeadTree