bob prohaska wrote:

>Is it possible to use a combined DNS/NATD machine to provide
>Internet access to hosts with registered names but no routeable
>IP numbers?
>
>The simplest situation would be a single, static IP host which
>serves as gateway to a 192.168.1.x network and also a nameserver
>for a domain. The nameserver would know the private address associated
>with each name, but would have to reply to queries with its own
>address, and some sort of "tag" which would be returned in subsequent
>traffic so it could properly recognize which host on the private
>network is the intended destination.
>

Even if the nameserver were to provide such a "tag", it would have to be
propagated through the resolver routines, picked up by the client app,
which would then need an interface to the networking stack to be able to
tag the packets that the client is using to connect to the server.
That's an awful lot of redesign work to accommodate a kludge (IMO) like NAT.

I suppose if more client apps used SRV records, then you could
theoretically direct different clients to different ports dynamically,
and then use port forwarding. However, SRV record support hasn't even
made it into web browsers yet, let alone clients of less-common protocols...


- Kevin