djbdns
[Top] [All Lists]

Re: "A" record priority?

To: "Michael Shuler" <mshuler@rackspace.com>
Subject: Re: "A" record priority?
From: "David Nicol" <davidnicol@gmail.com>
Date: Fri, 1 Dec 2006 15:43:24 -0600
Cc: "David B. John" <djohn@archdiocese-no.org>, dns@list.cr.yp.to
Delivered-to: sp-com-lists@consult.net
Delivered-to: gmail-djbdns@securepoint.com
Delivered-to: sp.com.list@gmail.com
Delivered-to: mailing list dns@list.cr.yp.to
Domainkey-signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references; b=ChFx+XJaAZa8W3vUI2lEdrdeaPU1e5qnfUfmHxvn49Ej0jCIffvHRnWzdtYgI/bD28uQEv3uMJCcPqI9dO3uib99eFghGv5yZwoa9ib67/CAh+VKRh6c2XCHFAucFRiLftsRkg7NzooG92ZjOL32cHqOcV58N+p2qXRCPr8xmlE=
Domainkey-status: good (test mode)
In-reply-to: <45708578.5060005@rackspace.com>
Mailing-list: contact dns-help@list.cr.yp.to; run by ezmlm
References: <00c001c71571$86ec0150$16fe010a@archno.local> <45708578.5060005@rackspace.com>
On 12/1/06, Michael Shuler <mshuler@rackspace.com> wrote:
David B. John wrote:
> Is there a way to give "A" records a priority like I do with "MX" records?

You cannot give an A record priority.

software will generally try the numbers returned in response to an A query
in the order that they are listed.  DJBDNS as I understand it randomly
shuffles them based on the idea that you have multiple records for load
balancing rather than high availability.  Disabling this policy and
replacing it with
explicit ordering shouldn't be that difficult, for sufficiently loose
definitions
of "not that difficult." Patches might exist already to provide configuration
options for altering the tinydns policy on ordering multiple A-records.

Different DNS servers differ on their approach to this question.

http://cr.yp.to/djbdns/tinydns-data.html states:
  For versions 1.04 and above: tinydns returns
  addresses (from + or = or @ or . or & lines) in
  a random order in the answer section. If there
  are more than 8 records, it returns a random set of 8.

If there isn't a patch already published to do what you want, I suggest
starting by imagining an extension to the confugration syntax to support
the additional option and then supporting the syntax as a patch development
methodology.

Dave
--
perl -le'1while(1x++$_)=~/^(11+)\1+$/||print'

<Prev in Thread] Current Thread [Next in Thread>