IntraNet DNS

[Glenn Crocker]

Yeah, this kind of thing can work out pretty well.

For example, I have a domain with an external DNS server (remote from my
network).  References to foo.bar.com get a regular, routable IP address that
comes to my NAT Firewall, gets translated, and comes to a machine on my
local net.

On my local network, I have a DNS server that my machines use, and I have
that server configured to resolve for my “bar.com” domain.  So internally,
foo.bar.com resolves to a 192.168. address.  Works great.

The point of all this is that the name foo.bar.com has two numeric
addresses.  One for everyone on the Internet, and another for people on my
internal network.

-glenn

> -----Original Message-----
> From: owner-kclug at marauder.illiana.net
> [mailto:owner-kclug at marauder.illiana.net]On Behalf Of Seth Dimbert
> Sent: Friday, January 25, 2002 11:33 AM
> To: kclug at kclug.org
> Subject: IntraNet DNS
>
>
> We've recently installed a Linux box to serve IntraNet pages locally.
>
> Users currently hit the box using a 192.168 IP. Can I set a DNS
> Server up on the same box to handle DNS for just that server?
>
> Or, if I ask nicely, can our ISP somehow route traffic for a
> 192.168 machine?
>
> -SD