<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 19:09, Robert Moskowitz
wrote:<br>
</div>
<blockquote cite="mid:512CFA74.9070103@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 12:58 PM, Sten Carlsen
wrote:<br>
</div>
<blockquote cite="mid:512CF7DF.5030009@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 18:06, Robert Moskowitz
wrote:<br>
</div>
<blockquote cite="mid:512CEBB0.7040009@htt-consult.com"
type="cite"> <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"> <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>
<br>
What I meant here, rather poorly stated, is that my mail server
would have to look up clients that only resolve within my internal
view. For example foo.bar which resolves to 192.168.178.5. That
query would fail if all the caching server had was public DNS
data.<br>
<br>
I DO run a hidden TLD here for some testing and those devices
currently do send mail from one to another through my current mail
server.<br>
</blockquote>
Almost my setup. I don't have a hidden TLD, that was too painful and
did not provide what I wanted.<br>
I use the same domain and the same names inside and outside, except
inside there are many more names.<br>
E.g. my mail server is called mail2.xxxx both outside and inside,
outside it has a public IP and inside it has an IP in the
192.168.x.x range.<br>
I also have servers that have the same IP both inside and outside.<br>
<blockquote cite="mid:512CFA74.9070103@htt-consult.com" type="cite">
<br>
<blockquote cite="mid:512CF7DF.5030009@s-carlsen.dk" type="cite">
<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>
</blockquote>
<br>
</blockquote>
<br>
<pre class="moz-signature" cols="72">--
Best regards
Sten Carlsen
No improvements come from shouting:
"MALE BOVINE MANURE!!!"
</pre>
</body>
</html>