In the dnssec.log file I only found references to normal key rotation.
Adding the section for update_security and running at trace 99 didn't
provide _any_ update_security log output, nor did it provide any extra
output to the update log.
even when running in single combined log format I coul
On Tue, May 28, 2024 at 09:09:20PM +0200, Marco Moock wrote:
> Am 28.05.2024 um 18:48:38 Uhr schrieb Peter:
>
> > On Tue, May 28, 2024 at 12:25:03PM +0200, Marco Moock wrote:
>
> > > > Now we add an IPv6 address for 'myhost'. But portforwarding
> > > > doesn't work for IPv6. Instead we are requir
Am 28.05.2024 um 18:48:38 Uhr schrieb Peter:
> On Tue, May 28, 2024 at 12:25:03PM +0200, Marco Moock wrote:
> ! > Now we add an IPv6 address for 'myhost'. But portforwarding
> ! > doesn't work for IPv6. Instead we are required to use different
> ! > addresses all over, like so:
> !
> ! port forw
On Tue, May 28, 2024 at 12:25:03PM +0200, Marco Moock wrote:
! Am 28.05.2024 um 12:00:09 Uhr schrieb Peter:
!
! > if I understand corrently, the use of CNAME is just a convenience
! > and no technical feature, right?
!
! It is technical because the query is redirected to the domain listed in
!
Am 28.05.2024 um 12:00:09 Uhr schrieb Peter:
> if I understand corrently, the use of CNAME is just a convenience
> and no technical feature, right?
It is technical because the query is redirected to the domain listed in
the CNAME.
> In lots of examples on the net, a zonefile for a domain might
Hello,
if I understand corrently, the use of CNAME is just a convenience
and no technical feature, right?
In lots of examples on the net, a zonefile for a domain might contain
things similar to this:
@ORIGIN example.com.
..
myhost A1.2.3.4
www CNA
6 matches
Mail list logo