This archive is retained to ensure existing URLs remain functional. It will not contain any emails sent to this mailing list after July 1, 2024. For all messages, including those sent before and after this date, please visit the new location of the archive at https://mailman.ripe.net/archives/list/[email protected]/

[dns-wg] Re: [enum-wg] Deploying DNSSEC in e164.arpa zone

• Previous message (by thread): [dns-wg] Re: [enum-wg] Deploying DNSSEC in e164.arpa zone
• Next message (by thread): [dns-wg] Deploying DNSSEC in e164.arpa zone

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

Jaap Akkerhuis jaap at NLnetLabs.nl
Fri Sep 28 12:08:38 CEST 2007

    
    this domain is signed, ALL servers respond with DNSSEC data EXCEPT the
    RIPE server which do not support DNSSEC....
    
    so if you resolve domains from 8.4.e164.arpa zone using RIPE server, you
    can't get DNSSEC enabled answers.
    
    we will remove ns.ripe.net and the problem will be solved today.

Ah, I might have hit that one, I just only tried it once. But there
is at least one lesson in this: you make sure al servers support
DNSSEC when you roll it out.

	jaap

• Previous message (by thread): [dns-wg] Re: [enum-wg] Deploying DNSSEC in e164.arpa zone
• Next message (by thread): [dns-wg] Deploying DNSSEC in e164.arpa zone

Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]

[ dns-wg Archives ]