DLZ and SRV records: Priority and weight not working?

[Chris Buxton]

As far as the DNS server is concerned, SRV records like this just  
form a record set. It's not up to the DNS server to order them in any  
particular way. Instead, it's up to the client to (a) request the  
correct record set and (b) process them in terms of priority and  
weight to choose the appropriate server.

This has absolutely nothing to do with the frequency of updates nor  
the fact that you're using DLZ. This is simply how SRV records work.

Chris Buxton
Men & Mice

On Jul 16, 2007, at 12:16 PM, Mike Toler wrote:

> Using pgAdmin III and "psql" command lines to query the DB, I don't  
> see
> any change in the order of my data using the query from BIND.  I DO  
> see
> order changing in the DNS responses, but it just isn't what it's  
> suppose
> to be.
>
> I don't know
>
> Michael
>
>> -----Original Message-----
>> From: bind-users-bounce at isc.org [mailto:bind-users-bounce at isc.org] On
>> Behalf Of Graeme Fowler
>> Sent: Monday, July 16, 2007 12:58 PM
>> To: bind-users at isc.org
>> Subject: Re: DLZ and SRV records: Priority and weight not working?
>>
>> On Mon, 2007-07-16 at 12:01 -0500, Mike Toler wrote:
>>> I've been trying to setup a POC (proof of concept) DNS server for
> one of
>>> our projects and have run into a snag.
>> <snip>
>>> Since we are having to do lookups on the database each time a DNS
> query
>>> comes in, is that somehow causing BIND to not proportionally order
> the
>>> answers?
>>
>> I believe the DLZ drivers will return data to the client in the order
> in
>> which they receive them from the query response (I could be wrong
>> though).
>>
>> If you run the raw SQL query against your DB the same number of  
>> times,
>> what do you see?
>>
>> Graeme
>>
>
>
>
>
> This message is confidential to Prodea Systems, Inc unless  
> otherwise indicated
> or apparent from its nature. This message is directed to the  
> intended recipient
> only, who may be readily determined by the sender of this message  
> and its
> contents. If the reader of this message is not the intended  
> recipient, or an
> employee or agent responsible for delivering this message to the  
> intended
> recipient:(a)any dissemination or copying of this message is strictly
> prohibited; and(b)immediately notify the sender by return message  
> and destroy
> any copies of this message in any form(electronic, paper or  
> otherwise) that you
> have.The delivery of this message and its information is neither  
> intended to be
> nor constitutes a disclosure or waiver of any trade secrets,  
> intellectual
> property, attorney work product, or attorney-client communications.  
> The
> authority of the individual sending this message to legally bind  
> Prodea Systems
> is neither apparent nor implied,and must be independently verified.
>
>