Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > comp.protocols.dns.bind > #15782 > unrolled thread
| Started by | Mark Andrews <marka@isc.org> |
|---|---|
| First post | 2020-05-27 09:28 +1000 |
| Last post | 2020-05-27 09:28 +1000 |
| Articles | 1 — 1 participant |
Back to article view | Back to comp.protocols.dns.bind
This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by
below is the oldest one visible, not the original post.
Re: Best way to force a TC=1 response? Mark Andrews <marka@isc.org> - 2020-05-27 09:28 +1000
| From | Mark Andrews <marka@isc.org> |
|---|---|
| Date | 2020-05-27 09:28 +1000 |
| Subject | Re: Best way to force a TC=1 response? |
| Message-ID | <mailman.444.1590535713.942.bind-users@lists.isc.org> |
> On 27 May 2020, at 07:27, John Levine <johnl@iecc.com> wrote: > > In article <mailman.442.1590526210.942.bind-users@lists.isc.org> you write: >> What's the best way to force an A query via UDP to return a TC=1 result: >> a really long CNAME chain? > > I'd suggest lots of AAAA records. You could do it with A records but you'd > need four times as many Well ~2 times as many. Each additional A record requires 16 bytes and each addition AAAA records requires 28 bytes. That means ~256 A records and ~146 AAAA records to force TCP with a 4096 byte UDP buffer size. John’s example had 187 AAAA records. Mark -- Mark Andrews, ISC 1 Seymour St., Dundas Valley, NSW 2117, Australia PHONE: +61 2 9871 4742 INTERNET: marka@isc.org
Back to top | Article view | comp.protocols.dns.bind
csiph-web