|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
Subject: Re: dnscache
From: Russ Allbery (rra
stanford.edu)Date: Wed Jun 14 2000 - 15:20:14 CDT
- Next message: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Previous message: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Next in thread: Russ Allbery: "Re: dnscache"
- Maybe reply: Russ Allbery: "Re: dnscache"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Wietse Venema <wietse
porcupine.org> writes:
> Bennett Todd wrote:
>> Rask, if you want to serve DNS data via TCP, djb's software does it
>> fine. dnscache serves both UDP and TCP as needed. Tinydns only serves
>> UDP, since that's all that's needed to return authoritative data to
>> currently-used recursive resolvers.
> What if the reply is "too large" for UDP?
I believe that tinydns refuses to process the zone file if it would result
in that large of a reply. Note that it doesn't include various additional
but not required fields like BIND does, so it returns smaller results in
general and therefore can serve more data within the UDP data size.
You can put a *lot* in 512 bytes. I'm somewhat suspicious of the
existence of real-world problems that require larger DNS returns and can't
be solved via some other, better way.
-- Russ Allbery (rrastanford.edu) <http://www.eyrie.org/~eagle/>
- Next message: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Previous message: Russ Allbery: "Re: Don't add domainname to 'To: Undisclosed-Recipient:;'"
- Next in thread: Russ Allbery: "Re: dnscache"
- Maybe reply: Russ Allbery: "Re: dnscache"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]