<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFCC" text="#000000">
<br>
<div class="moz-cite-prefix">On 26/02/13 18:06, Robert Moskowitz
wrote:<br>
</div>
<blockquote cite="mid:512CEBB0.7040009@htt-consult.com" type="cite">
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
<br>
<div class="moz-cite-prefix">On 02/26/2013 11:43 AM, Sten Carlsen
wrote:<br>
</div>
<blockquote cite="mid:512CE644.6000504@s-carlsen.dk" type="cite">
<meta http-equiv="Context-Type" content="text/html;
charset=ISO-8859-1">
<br>
<div class="moz-cite-prefix">On 26/02/13 15:50, Robert Moskowitz
wrote:<br>
</div>
<blockquote cite="mid:512CCBC4.8000601@htt-consult.com"
type="cite"> <br>
I would expect that a namecaching server on the mailserver
would reduce traffic and resources all the way around. <br>
<br>
I don't need my mailserver to constantly be asking my name
server about, say, zen.spamhaus.org. <br>
</blockquote>
This is one reason my mailserver has a DNS server. No forward,
that only slows down things.<br>
The question here is whether there is a good reason that this
instance must not go directly to the roots?<br>
</blockquote>
<br>
To support systems only visable to your internal view?<br>
</blockquote>
I have in my internal view mostly systems that are not visible from
the outside but my internal view has direct access to the world with
regards to DNS. I don't see any risk in that , except the
predictability of RBL-lookups as mentioned elsewhere.<br>
Speed is much improved, even with a standard ADSL line I have better
performance than by forwarding to the ISP DNS server.<br>
<blockquote cite="mid:512CEBB0.7040009@htt-consult.com" type="cite">
<br>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>