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/dns-wg@ripe.net/

[dns-wg] IPv6 backresolve with DNSSEC

Previous message (by thread): [dns-wg] IPv6 backresolve with DNSSEC
Next message (by thread): [dns-wg] IPv6 backresolve with DNSSEC

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

Brett Carr brettcarr at ripe.net
Thu Jul 5 13:17:22 CEST 2007

Max,
     we are looking into this I will get back to you on it.

Regards

--
Brett Carr
Manager -- DNS Services Group
RIPE Network Coordination Centre
Amsterdam


On Jul 4, 2007, at 10:22 PM, Max Tulyev wrote:

> Hi All,
>
> I tried to create a DNSSEC signed backresolve domain for my IPv6  
> block:
>
> domain:          0.d.0.0.1.0.a.2.ip6.arpa
> descr:           NetAssist LLC
> org:             ORG-NL64-RIPE
> admin-c:         MT6561-RIPE
> tech-c:          MT6561-RIPE
> zone-c:          MT6561-RIPE
> nserver:         ns.netassist.kiev.ua
> nserver:         ns.netassist.ru
> ds-rdata:        46236 5 1 B42280F344BB12FCC5030673109EF84EF2C4D3A7
> mnt-by:          MEREZHA-MNT
> mnt-lower:       MEREZHA-MNT
> changed:         support at netassist.kiev.ua 20070704
> source:          RIPE
>
> and it fails with:
>
> ***Error: DS records are not accepted for this zone.
>
>
> ***Error: RDNS Authorisation failed
>
> but without ds-rdata everything works fine.
>
> Is it a (my) bug or a feature?
>
> -- 
> WBR,
> Max Tulyev (MT6561-RIPE, 2:463/253 at FIDO)
>

Previous message (by thread): [dns-wg] IPv6 backresolve with DNSSEC
Next message (by thread): [dns-wg] IPv6 backresolve with DNSSEC

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

[ dns-wg Archives ]