[Pdns-users] ENUM order value question! ? :)

[Jonathan Hunter]

Hi Guys,
I wondered if anyone had seen similar results to me or if I need to reconfigure anything.
Essentially Im using Power dns 
dig command to the power dns ENUM server returns results in order value;

8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 74 3 "U" "E2U+sip" "!^(.*)$!sip:*241*\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 76 13 "U" "E2U+sip" "!^(.*)$!sip:*311*+\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 89 49 "U" "E2U+sip" "!^(.*)$!sip:*421*\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 109 48 "U" "E2U+sip" "!^(.*)$!sip:*381*+\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 216 2 "U" "E2U+sip" "!^(.*)$!sip:*205*00\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 728 49 "U" "E2U+sip" "!^(.*)$!sip:*421*\\1 at 1.2.3.4!" .8.3.4.0.9.1.7.1.9.7.4.4.e164.sip 120 IN NAPTR 1050 3 "U" "E2U+sip" "!^(.*)$!sip:*241*\\1 at 1.2.3.4!" .

However when capturing in wireshark on the wire I can see the answers sections returns in summary as;

8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 89, preference 49, flags U8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 109, preference 48, flags U8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 728, preference 49, flags U8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 216, preference 2, flags U8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 1050, preference 3, flags U8.3.4.0.9.1.7.1.9.7.4.4.e164.sip: type NAPTR, class IN, order 74, preference 3, flags U

Can powerdns send out in the DNS response packet with an ordered by order value Answer section?  As my stored procedure does it from a MySQL sense but not when populating the DNS response, is this configurable?
Or is it purely left to the client to order and select accordingly?
Merry Christmas to you all :)
Thanks
Jon
 		 	   		  
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20151221/73b8e889/attachment.html>