Re: [bitfolk] c.authns.bitfolk.com borken?

Top Page
Author: Mike Zanker
Date:  
To: Anahata via users
Subject: Re: [bitfolk] c.authns.bitfolk.com borken?

Reply to this message
gpg: Signature made Fri May 6 15:42:03 2022 UTC
gpg: using RSA key AA62533B3CA64488DF7692A7E2E589EDD062903B
gpg: Can't check signature: No public key
> On 6 May 2022, at 16:21, Andy Smith <andy@???> wrote:
>
> Its IPv6 address had to change. I thought I had done that properly,
> but it seems not. It should be fixed now. It should have only been
> evident on IPv6, not IPv4.


Further to this, I’ve just checked my allow-transfer setting in bind and it has 3 IPv4 addresses and 3 IPv6. This was done ages ago, so what should I have now for allow-transfer?

Thanks,
Mike