>On Wed, 5 Apr 2000, Fred Wright wrote:
>> > 4) MiamiTCPDump shows an "unreachable" error when trying to route the
>> > reply from the DNS server:
>> This is the normal firewall problem. With TCP one can recognize an
>> incoming packet as a "response" without knowledge of the application
>> protocol. But this isn't true of UDP, thereby causing trouble, although
>> if NAT understood DNS specifially it could get around that.
>What I'd like to see: a small cacheing nameserver to get around this
>problem and some of the "windoze keeps doing stuff that makes me connect"
>problems. This would also help when MiamiDX finds the nameservers
>dynamically but the other NATed or otherwise connected boxes have to have
>the DNS configured statically.
>And it's also faster when some stuff can live in the cache so not every
>machine has to get it over the slow link to the net.
That's an excellent idea. It shouldn't be too hard to do either, and may
already have been done. Does anyone know of a program like this, either for
the Amiga, or an Open Source project that could be easily ported?
Of course the other machines would still need static DNS entries, but they
would be the Gateway Amiga's address, which would pass through to lookups
even on dynamic DNS servers.
-----------------------------------------------------------------------------
Rhett R. Rodewald
Have you written your own real-time OS lately???
Wait a tick while I hit the depth gadget the Doom window is in the way...
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
