<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 6/14/13 11:07 AM, Chip Marshall
wrote:<br>
</div>
<blockquote cite="mid:20130614150741.GB56310@2bithacker.net"
type="cite">
<pre wrap="">There was some talk at a recent meeting about establishing some
best practices for operating a DNS server. I'm curious if anyone
is running with this, and if not, if this would be a good forum
to start working on such a project.
I know there are some IETF documents around best practices for
things like DNSSEC, but to the best of my knowledge there's not a
good repository for things like RRL, making sure your recursive
resolver isn't open, ensuring source port randomization (I know I
still see a lot of source 53 queries) and so on.
</pre>
<br>
<fieldset class="mimeAttachmentHeader"></fieldset>
<br>
<pre wrap="">_______________________________________________
dns-operations mailing list
<a class="moz-txt-link-abbreviated" href="mailto:dns-operations@lists.dns-oarc.net">dns-operations@lists.dns-oarc.net</a>
<a class="moz-txt-link-freetext" href="https://lists.dns-oarc.net/mailman/listinfo/dns-operations">https://lists.dns-oarc.net/mailman/listinfo/dns-operations</a>
dns-jobs mailing list
<a class="moz-txt-link-freetext" href="https://lists.dns-oarc.net/mailman/listinfo/dns-jobs">https://lists.dns-oarc.net/mailman/listinfo/dns-jobs</a></pre>
</blockquote>
While I might be getting ahead of myself I do think that any 'best
practice' document should be regularly looked at and updated. If a
DNS BCOP is handled by DNS OARC then at each meeting there should be
a quick 'Does anything need to be updated in the BCOP?' section so
that it remains Best Current and not Best 2013.<br>
<br>
Liam <br>
</body>
</html>