+--On 14 juillet 2010 18:38:44 +0200 Matthijs Mekking
wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| Hi Mathieu,
|
| I believe that it is correct that the signer puts that much NSEC3
| records in the zone. It has two for the domain names
| d.0.1.f.f.8.f.4.2.0.0.2.ip6.arpa. and
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mathieu,
I believe that it is correct that the signer puts that much NSEC3
records in the zone. It has two for the domain names
d.0.1.f.f.8.f.4.2.0.0.2.ip6.arpa. and
0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.d.0.1.f.f.8.f.4.2.0.0.2.ip6.arpa.
and 19
+--On 14 juillet 2010 11:47:19 +0200 Matthijs Mekking
wrote:
| -BEGIN PGP SIGNED MESSAGE-
| Hash: SHA1
|
| Hi Mathieu,
|
| That are indeed a lot of NSEC3 records. Could you share with me the
| kasp.xml file you are using for this zone (off list if you like)?
It's pretty standard, but th
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi Mathieu,
That are indeed a lot of NSEC3 records. Could you share with me the
kasp.xml file you are using for this zone (off list if you like)?
Best regards,
Matthijs
On 07/07/2010 03:36 PM, Mathieu Arnold wrote:
> Today, I upgraded from 1.0 to 1
+--On 7 juillet 2010 15:36:44 +0200 Mathieu Arnold wrote:
| I don't really understand, but I think that it generates NSEC3 records
| for way too much things.
Well, in fact, it already did that before, only, the auditor did not think
it was a bad thing.
--
Mathieu Arnold
Today, I upgraded from 1.0 to 1.1, and, it kinda worked ok, for most of
the zones I sign, but now, for some, I have problems.
The simplest zone I have problems with is the following :
# cat d.0.1.f.f.8.f.4.2.0.0.2.ip6.arpa
$TTL1d
@ IN SOA ns1.absolight.net.
