SRV Record Priority set by IP Address

[Chris Thompson]

On Jul 20 2009, Dmitry Rybin wrote:

>Lev Vanyan wrote:
>> 
>> i've stumbled into a question whether it is possible to configure BIND
>> in a way that it responds to DNS SRV requests with the priority flag
>> changed depending on the IP address of the requesting party.
>> For example,
>> there are two SRV records for _foobar._tcp. One points to 10.0.1.2 and
>> the other to 10.0.2.2. The requesting party has the ip address
>> 10.0.1.53. I would want to have the first one with the priority higher
>> than the second, which would allow me to split up the network by zones
>> each one having their own server with the rest of servers used only in
>> case of the prevalent zone server failure.
>
>As variant:
>Two views, fist with record
>srv 10.0.1.2
>srv 10.0.2.2
>
>second:
>srv 10.0.2.2
>srv 10.0.1.2
>
>Then set RRSET to FIXED.

Using two views is right, but the rest of this is very much not so.
No SRV-using application is going to treat the RR order in the answer
as significant. They will use the priority and weight fields as
described in RFC 2782 (or so one hopes). Those should be adjusted
appropriately in the two views.

-- 
Chris Thompson
Email: cet1 at cam.ac.uk