Hi folks,
Setting up DNSSEC for a parent domain is relatively simple. The fiddly
bit is probably where you have to figure out what your KSK is so that
you can give it to your ISP. They can then create a DS record to
verify a DNSKEY record in your domain and so complete the chain of
trust.
Hi Jaap,
On 05/06/13 16:09, Jaap Winius wrote:
> 2.) http://dnsviz.net/d/zuid.dapadam.nl/dnssec/
>
> This shows two DS records in the parent zone, one not secure and one
> bogus, and three DNSKEY records in the child zone, none of which are
> secure.
Perhaps you could remove ns[12].transip
In message <5187c559.6040...@sidn.nl>, "Marco Davids (SIDN)" writes:
>
> Hi Jaap,
>
> On 05/06/13 16:09, Jaap Winius wrote:
>
> >
> > This shows two DS records in the parent zone, one not secure and one
> > bogus, and three DNSKEY records in the child zone, none of which are
> > secure.
>
> Perha
Quoting Mark Andrews :
In message <5187c559.6040...@sidn.nl>, "Marco Davids (SIDN)" writes:
On 05/06/13 16:09, Jaap Winius wrote:
>
> This shows two DS records in the parent zone, one not secure and one
> bogus, and three DNSKEY records in the child zone, none of which are
> secure.
Perhaps y
4 matches
Mail list logo