<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN">
<html>
<head>
<meta content="text/html; charset=ISO-8859-1"
http-equiv="Content-Type">
</head>
<body text="#000000" bgcolor="#ffffff">
On 2010-02-24 14:09, Peter Andreev wrote:
<blockquote
cite="mid:f45e198a1002240509g1bd7febetaf234cf7332d198e@mail.gmail.com"
type="cite">2010/2/24 Alan Clegg <span dir="ltr"><<a
moz-do-not-send="true" href="mailto:aclegg@isc.org">aclegg@isc.org</a>></span><br>
<div class="gmail_quote">
<blockquote class="gmail_quote"
style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">Peter Andreev wrote:<br>
<br>
> > For example: if user asks for non-existent domain,
caching server<br>
> > replies with some address and no-error rcode.<br>
><br>
> _Extremely_ bad idea.<br>
><br>
><br>
> Yes, I know, but boss is boss and task is task :).<br>
><br>
> Thank you very much for your answer.<br>
<br>
</div>
You might want to talk to your boss about DNSSEC and how it insures that<br>
"answer modification" is not allowed -- and how it keeps your customers<br>
safe and secure and is a good selling point (see the Comcast<br>
announcement that was made yesterday).<br>
<br>
AlanC<br>
<br>
</blockquote>
<div>Oh, DNSSSEC is another headache. These two tasks doesn't
influence each other.<br>
</div>
</div>
</blockquote>
As far as I can tell, they DO: your modified answers will be marked as
BOGUS by DNSSEC and will be thrown away.<br>
<br>
Niobos<br>
</body>
</html>