|
|
 |  |
Re: Working around Verisign power-grab?From: Stonewall Ballard Date: Tuesday, September 16, 2003
Time: 6:17:43 pmSolving the problem at the routing level doesn't help. My mail server
(CommuniGate Pro) likes to distinguish real domains from nonexistent ones,
so that it can reject spam with bad reply addresses.
It would be great if you could say whether patching BIND to recognize the
Verisign response and converting it back to a "no domain" response would in
any way affect QuickDNS.
Thanks.
- Stoney
On 9/16/03 8:12 PM, "Men & Mice Support" <cbuxton@menandmice.com> wrote:
> We are not going to endorse any such patch, since we have no control
> over them and since we're not about to write one of our own.
>
> If Verisign's action bothers you, solve the problem at the routing
> level, as Jer suggests. It won't affect users outside your network,
> but it's the only reasonably safe solution.
>
> Personally, I think some sort of URL spell-checker is a good idea.
> What they have at the moment seems like a good start.
> ____________________________________________________________________
> Chris Buxton Men & Mice
> Customer Support Specialist Making DNS Easy
>
> At 1:45 PM -0400 9/16/03, Stonewall Ballard wrote:
>> Is there a M&M-approved way to work around the new Verisign wildcard? There
>> are BIND patches appearing, but I'd like to have some verification from M&M
>> that this wouldn't mess up QDNS.
>>
>> I'm running QDNS on Mac OS X Server 10.2.6.
>>
>> - Stoney
>>
>> --
>> Stonewall Ballard Stonetics, Inc.
>> sb@stonetics.com http://www.stonetics.com/
>
>
|

Return to Digital Point Solutions' Home Page |