Subj : RE: PRO
To   : Jay Fuller
From : Chris Cranford
Date : Sat Dec 08 2001 08:09 am

Jay -

-> yes, that's exactly what is happening.  and I've already read your
-> response, and I'm not happy with it ;)

-> see, when I had the internal DSL modem and winroute, I did not have this
-> problem. I can't necessarily point to "cullmanhosting.com" because that
-> is an actual internet domain pointing to my ip address which gets
-> forwarded to my webserver and the proper website gets served depending
-> on that address. With an internal modem it did just fine. Of course, I
-> can't type in 192.168.0.1 and hit the server because than it does not
-> know which website to serve.  I've got five machines on my LAN here. I
-> really don't need to be editing 5 hosts files (yes, I've done this
-> before), but i've never setup internal DNS before, either.  DNS right
-> now is being handled out of ZONEEDIT.

-> help me here. ;)  When I type cullmanhosting.com or baylorcove.com or
-> jfuller.dyndns.org, I'd like to get the same thing I get from the
-> outside network.  Can I not do that through some config on the router?

-> Oh, and I can't get to the telnet port on DSN either (but i couldn't
-> through winroute either) - I did have to do directly to that machine
-> from the LAN.  IT'll work coming in from the outside...but then again,
-> *everything* works coming in from the outside. Only problem is, it needs
-> to work from the inside too :)

-> and override the external domain?

Ok, here's the deal.  If you're running your NETGEAR router and
protecting all your machines behind the router using private IP
addresses, there are only 2 ways to get what works on the out-
side to work on the inside.  Again those are:

 1) Edit HOST files
 2) Internal DNS server

Now, here at tkdsoftware.com we have 5 domains we're currently
hosting.  These domains are all hosted via 1 IP address which 
is the external WAN interface on the NETGEAR router.  The 
solution we choose was to setup an Internal DNS server.  

On the internal machines, we setup the DNS server to point to
that of the internal DNS server (192.168.0.25).  This DNS 
server is setup to resolve for domains we host and forward
the requests to the root DNS servers shall a query come in
for a domain we don't host.

If each of your resources (www.domain1.com, www.domain2.com)
resolved to different public IP addresses, you would not 
be experiencing this problem, hence you wouldn't be running
the router but instead a switch.

There are a number of DNS server software packages out there
which you can use.  Some of them are free while others are 
not.  

Do you have a RedHat/Linux installation on any of your boxes
currently on your network?  If not, could you afford to 
convert 1 box to RedHat/Linux?

This is what we did here.  We have 1 RedHat 7.1 box that 
handles DNS.  It has two NICs which serve for Internal and
External DNS requests.  This way, people who query for our
domains hit the External interface while we, internally, 
query the Internal interface for DNS requests.

Let me know if you need any more help.
Chris
--- Mail-ennium/32 v1.0.236
 * Origin: www.tkdsoftware.com - Mail-ennium/32 Mail Tosser Home (1:379/1200.0)

.