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.
--
To unsubscribe send "unsubscribe miami-talk-ml" to
"[EMAIL PROTECTED]". For help on list commands send "help" to
"[EMAIL PROTECTED]".
