Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Chris Brenton <cbrenton@chrisbrenton.org>
To: Antony Stone <Antony@Soft-Solutions.co.uk>
Cc: netfilter <netfilter@lists.netfilter.org>
Subject: Re: Packets missing state ?
Date: Tue, 23 Dec 2003 12:13:33 -0500	[thread overview]
Message-ID: <1072199612.2184.467.camel@grendel> (raw)
In-Reply-To: <200312231533.40728.Antony@Soft-Solutions.co.uk>

On Tue, 2003-12-23 at 10:33, Antony Stone wrote:
>
> > > Yes.   UDP port 53 means client-to-server DNS lookups.
> >
> > It could also be server to server queries as well as a load balancer.
> 
> I thought server to server queries were always TCP?

Nope. UDP is always used unless the "answer" will exceed a packet length
of 512 bytes. If this max is exceeded, as complete an answer as possible
is returned with the truncation bit turned on in the DNS header. After
that, you'll see the session switch over to TCP for a complete answer.

The other case is primary/master <--> secondary/slave communications for
the purpose of zone transfers. 

Dig and other tools will let you choose to use TCP, but the default is
UDP.

HTH,
C





  parent reply	other threads:[~2003-12-23 17:13 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-23 12:58 Packets missing state ? Rajiv Shah
2003-12-23 13:08 ` Antony Stone
     [not found]   ` <200312231857.21676.vinayakm@theargoncompany.com>
2003-12-23 13:37     ` Vinayakam Murugan
2003-12-23 13:54       ` Antony Stone
2003-12-23 15:21         ` Chris Brenton
2003-12-23 15:33           ` Antony Stone
2003-12-23 16:00             ` Cedric Blancher
2003-12-23 17:13             ` Chris Brenton [this message]
2003-12-23 13:55       ` Cedric Blancher
2003-12-24  4:12         ` Vinayakam Murugan
2003-12-24  7:48           ` Cedric Blancher
2003-12-24  8:18             ` Vinayakam Murugan
2003-12-24  8:42               ` Cedric Blancher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1072199612.2184.467.camel@grendel \
    --to=cbrenton@chrisbrenton.org \
    --cc=Antony@Soft-Solutions.co.uk \
    --cc=netfilter@lists.netfilter.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox