rrset-order and caching servers
cbuxton at menandmice.com
Thu Jul 26 18:59:09 UTC 2007
No, there is no solution to this problem.
In DNS, the ordering of an RRSet is considered unimportant. Because
client software often does consider it important, a name server
sending an RRSet in a response is free to re-order the set any way it
likes. So while your name servers may impose a particular ordering of
an RRSet, because you've set it to do so, other name servers will
cache that data and then reorder it as they please.
So now you must examine why you feel it is important that records are
returned in a particular order. Is there a solution that does not
rely on the ordering of records in a record set?
Men & Mice
On Jul 26, 2007, at 11:34 AM, Scott Moseman wrote:
> Upgraded to 9.4.1-P1 and finally got the rrset-order working.
> However, I do have an issue, but I think it's simply the way
> that DNS function.
> My DNS servers will provide records (for instance, A or SRV)
> in a fixed order as designed. That's good. But I notice that
> other DNS servers will receive the records, cache them and
> start providing round robin results to their clients. That's not
> good, since it obviously reverses our plan.
> Am I correct in assuming there's not going to be a method to
> get around this? Obviously beyond setting up all devices with
> our DNS servers specifically, which may work in this case, but
> it is not a scalable solution.
More information about the bind-users