nsd users - Apr 2012 - Suitability of NSD for ENUM

Hello,

I'm rolling out a registrar service for ENUM and wondering if NSD is
suitable for its special format -- rather long lists of labels in a
zone name and potentially a lot of small domains.  Scaling is what I'm
wondering about.

Did I understand correctly that the search for an RRset is done on
the entire label list (or name) requested?  So the special format of
names in ENUM is not special in any way?

The Memory Usage tool is great --even if it does not show NAPTR records--
but it does not take DNSSEC into account, right?  That could be a useful
addition to the tool?

If memory runs out, will NSD try to offload into swap, or is this left
to the OS?

This is wishful thinking of course... it'd be cool if ENUM would be a
scalability problem... but I'm looking ahead, and hoping to cause those
scalability problems in the years to come ;-)


Thanks,

Rick van Rein
OpenFortress

[ Quoting <rick at openfortress.nl> in "[nsd-users] Suitability of
NSD for ..." ]
> Hello,
> 
> I'm rolling out a registrar service for ENUM and wondering if NSD is
> suitable for its special format -- rather long lists of labels in a
> zone name and potentially a lot of small domains.  Scaling is what I'm
> wondering about.
What special format? It's just an domain name.

NSD scales very well, except for large numbers of small zones, esp.
if you want to add/remove them on the fly.

I thought (I'm not involved) NSD4 is set to remedy these issues.

 Regards,

-- 
    Miek Gieben
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 198 bytes
Desc: Digital signature
URL:
<http://lists.nlnetlabs.nl/pipermail/nsd-users/attachments/20120416/cc623d14/attachment.bin>

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

Hi,

On 04/16/2012 09:46 AM, Rick van Rein wrote:
> Hello,
> 
> I'm rolling out a registrar service for ENUM and wondering if NSD
> is suitable for its special format -- rather long lists of labels
> in a zone name and potentially a lot of small domains.  Scaling is
> what I'm wondering about.
Although it can serve a reasonable number of zones, NSD3 has turned
out to be not that good in scaling when it comes to a large number of
zones. This will be tackled in NSD4. How many zones are we talking about?
> Did I understand correctly that the search for an RRset is done on 
> the entire label list (or name) requested?  So the special format
> of names in ENUM is not special in any way?
The domain name table is stored as a red black tree. Each domain name
is treated equally, when it comes to searching (it is just another
node in the tree).
> The Memory Usage tool is great --even if it does not show NAPTR
> records-- but it does not take DNSSEC into account, right?  That
> could be a useful addition to the tool?
True. Then again, it is an estimate tool;).
> If memory runs out, will NSD try to offload into swap, or is this
> left to the OS?
This is OS specific.

Best regards,
  Matthijs
> This is wishful thinking of course... it'd be cool if ENUM would be
> a scalability problem... but I'm looking ahead, and hoping to cause
> those scalability problems in the years to come ;-)
> 
> 
> Thanks,
> 
> Rick van Rein OpenFortress 
> _______________________________________________ nsd-users mailing
> list nsd-users at NLnetLabs.nl 
> http://open.nlnetlabs.nl/mailman/listinfo/nsd-users
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJPi9d4AAoJEA8yVCPsQCW591wH/jWe7ewD9oS7is8xHtDQvy/A
uaP2OTCkYjgU80Dw8u7LyIOjMguLstqs0H0jefOPNe7ijSQQROPzhcIsoQqC6xsE
Qym0MXF1Ux6OUNwXHdrjpwBfota5hAh6EWw3R2hAIebWWQafLujRowFFYMzsHIro
L5yLiAJLLN/3ru8SO2UQypZi2oGH4bA76CcYcV7GVAZ/arZmVQZAgjhenJ8PyC6Z
pLt9xYOOp7kR/DBlmgjOoQiQD4pjoqBlziofGNfd9/lyCBeYtVSOxyPLB58h69r+
pE5eG83XDAfc7yYOuKvrAffTOOmgZZuR6+YJYnt4H8RubJYOnSYUCRbbBkKmDUs=V6Aw
-----END PGP SIGNATURE-----