Unregistered local domain yet internet access?

[Jack Aubert]

That's exactly what I'm doing at home.  I called my internal domain aubert.
it has hosts like papabear.aubert, mamabear.aubert... etc.  The local
nameserver that has SOA for "aubert" just forwards to the cable operator's
DNS.

Obviously I can't resolve a name from the internet to anything on the
inside, but since I keep the connection nailed up, I keep a permanent lease
on the same internet address which is on one side of the proxy firewall and
so I can use the IP address to get to the internal web server from the
outsice.... not practical for anything commercial, but I can keep family
pictures on it.


Michael Voight wrote in message <37711DE3.989CFD4B at cisco.com>...
>DNS has no clue about the difference between a registered name and a non
>registered name except for the fact the root servers know about the top
>level names (and a bit more). I assume you are referring to cable
>modems. In this envrionment, normally my customers use DHCP to send a
>private address to the modem, and public addresses to the device or
>devices behind it. Since you are the one deciding which DNS server each
>machine will use, you might want to direct internal machines to an
>internal server and the otherss to point directly at the external DNS
>server. Or.. You could point all devices at the internal server and use
>a forwarder definition on that server to route unknown requests to the
>outside DNS server.