[nsd-users] NSD SRV rr return limit

[W.C.A. Wijngaards]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Hi Will,

On 05/16/2012 01:08 AM, Will Pressly wrote:
> Nah. I am querying directly against the authority.

There is no limit imposed (apart from packet size and the 16-bit
counter for the number of RRs and so on).  So, practically, 30 or so
to keep easily within UDP message sizes (you would need to test to see
the compression benefits and resulting message size), and with TCP
failover up to 64Kib of data (thousands of SRVs).

Best regards,
   Wouter

> On Tue, May 15, 2012 at 3:44 PM, Bryan Duff <bduff at ecessa.com 
> <mailto:bduff at ecessa.com>> wrote:
> 
> __ On 05/15/12 17:18, Will Pressly wrote:
>> Hi All,
>> 
>> Is there a limit to the number of SRV records that NSD will 
>> return, outside of the upper bound on packet size? I have a name 
>> that has ~18 SRV records, and I only see the same four, always. 
>> The packet size out on the wire is 260B, so I would expect we 
>> could cram some more in there, and I am not sure why we are only 
>> ever seeing the same five.
>> 
>> I wanted to ask before burning time on a source-code code-dive.
>> I am using nsd 3.2.5.
>> 
>> Thanks, Will Pressly
>> 
>> 
>> _______________________________________________ nsd-users mailing
>> list nsd-users at NLnetLabs.nl <mailto:nsd-users at NLnetLabs.nl> 
>> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
> Remember NSD doesn't rotate records in the same set (or in any 
> case).  Also, you aren't going through a caching server are you?
> 
> $ dig @192.168.2.231 <http://192.168.2.231> 
> _autodiscover._tcp.example.org <http://tcp.example.org> srv ... ;;
> QUESTION SECTION: ;_autodiscover._tcp.example.org
> <http://tcp.example.org>. IN      SRV
> 
> ;; ANSWER SECTION: _autodiscover._tcp.example.org
> <http://tcp.example.org>. 30 IN SRV     1 100 25 mail.example.org
> <http://mail.example.org>. _autodiscover._tcp.example.org
> <http://tcp.example.org>. 30 IN SRV     2 100 25 mail.example.org
> <http://mail.example.org>. _autodiscover._tcp.example.org
> <http://tcp.example.org>. 30 IN SRV     3 100 25 mail.example.org
> <http://mail.example.org>. _autodiscover._tcp.example.org
> <http://tcp.example.org>. 30 IN SRV     4 100 25 mail.example.org
> <http://mail.example.org>. _autodiscover._tcp.example.org
> <http://tcp.example.org>. 30 IN SRV     5 100 25 mail.example.org
> <http://mail.example.org>.
> 
> ;; AUTHORITY SECTION: example.org <http://example.org>.
> 360     IN      NS ns1.example.org <http://ns1.example.org>. //end
> snip
> 
> That was just me quickly creating some entries on a test zone. 
> Often caching servers limit the number of RR's to whatever they
> feel like (4 seems common).  That's just my experience.
> 
> -Bryan
> 
> 
> 
> 
> _______________________________________________ nsd-users mailing
> list nsd-users at NLnetLabs.nl 
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQIcBAEBAgAGBQJPs1e9AAoJEJ9vHC1+BF+NFSIP/i6NPIGTTz6DN85AnPiag+oS
y9Ye7COqTb08VaSG65wdrGq7Ijy89SgKILXyoMtXmHirRMOSCQRwMTBFJLzfjoH/
xVSh/nbgPI73AYAVIVU9P+Yzw8Nch5bDmY6tzlj0Ugg0pEGvBoXp6MTFjVvFDm+P
fd+KVIZjuy9uBHjn7lFrjt3lRdY5GCfN/njmr5udeD5a0b/+DL7dj6I8RTrjqrjG
TSYhrZTEzZYESuPkiVzgyu+vFOoTGrHo8W93H6qXhB8bfteHM7QqcCfX1EeX7FcO
AG7JOWqFVc1w2Zp3tnfMEB/s9o31EQn3Ltyd+hAttr9sBSNozAYcJ9Hk8OBXEn0n
RZhJ8aLunJDLtp/LCoJSFAwJJIvAnoJJlsMIRrlFN1lX2QN7R6mothqJM2sePzrk
0UERRoSusTyzKonL89KmXaKHkrdH9BQ0X4H+Hc5GNmmWANsl+WbWRZedP8/F5IgQ
9f8Zqayqm2Mx2B4ATk4h2vFMKAp+r2h/1/+KMCaD6D1zgRb6MVBJmK3kV72eIpxz
z3nC8aLzRa4vlakEZQ0loxURKdMbUh22rGuzYEvtUFnlOkT4+IvgoDKfPHjlev53
WvnR4XpTlq5YS/lo3WJBcCqrCuAUR6uNDIRG6Wdq3hdu9lZRxJKkCZKtNg5piSJv
xkPhX267OaeLGUPRhxU9
=y43o
-----END PGP SIGNATURE-----