Hmmm...With my DSL connection I have to have an ISP, whether it's
the phone company or a third party (which it is in my case). My
ISP handles all DNS services for my domain. They know about my
domain and any server I tell them the name of (like WWW., FTP.,
etc.) They direct all packets to my single, static, IP address.
My STN installation takes the packets and routes them to the
correct internal machine based on the port used.
I don't think my ISP has to provide the DNS service, it could be
anybody willing to do it. My ISP just doesn't charge anything
for doing it.
The STN DNS server is visible to the outside world, and you can
query it from outside to see what's on the inside and even
get the IPs of the "hidden" machines. You just can't send
anything to those IPs, because they are in a non-routable range.
So, I'm not sure you can use STN's DNS server as the primary
domain server, because it has to know the internal IPs. The
ISP DNS server just treats all valid hosts defined in my domain
as one, static, IP, which is valid to any host on the Internet.
Dave
The Rosens wrote:
>
> I believe that if DNS is running on a machine, DNS makes itself
> available to all networks connected to that box. Check out DNS and BIND
> (O'Reilly & Associates; ISBN: 1565925122) or consult a DNS guru for the
> accuracy of this statement.
>
> Why would this be useful?
>
> GREAT QUESTION- And something I've been considering for a while now. Can
> anyone tell me if the following makes sense (read: does it really work
> this way?):
>
> I believe that, if you were to register your own domain
> (www.yourdomain.com) with interNIC (woops, I mean Network Solutions:
> http://www.networksolutions.com) you need to provide them with a primary
> (and secondary) DNS server, who will translate "www.yourdomain.com" into
> an IP address. Obviously, you would want to be your own primary DNS
> site. But, if your entire network is hiding behind STN, how would this
> be done?
>
> Although I haven't done this, it appears, that you would provide
> InterNIC with the IP address that your cable modem provides your STN
> router (assuming, of course, that this address is static or at least
> comes with a rather long lease from your ISP). When some surfer out on
> the net, attempts to go to www.yourdomain.com, his initial request will
> be pointed to port 53 of your STN machine. This is the STN DNS server.
> This should return the same external address of your STN machine (since
> your internal IP address are meaningless outside your network). When the
> actual http request comes back to you (via port 80), your STN machine
> will transfer the packets to the appropriate machine in your network.
> This gets defined in your "Inbound Services" page.
>
> Has anyone done this?
>
> Am I missing something?
>
> Feel free to correct me (but, please no flames)...
>
> ...steve...
> [EMAIL PROTECTED]
>
> _______________________________________________
> ShareTheNet maillist - [EMAIL PROTECTED]
> http://www.webserv.com/mailman/listinfo/sharethenet
_______________________________________________
ShareTheNet maillist - [EMAIL PROTECTED]
http://www.webserv.com/mailman/listinfo/sharethenet
