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 16:15:53 2022 UTC
gpg: using RSA key AA62533B3CA64488DF7692A7E2E589EDD062903B
gpg: Can't check signature: No public key
Cheers Andy - I’ll stick to just a.authns.bitfolk.com <http://a.authns.bitfolk.com/> to make things easier :)

> On 6 May 2022, at 17:04, Andy Smith <andy@???> wrote:
>
> Signed PGP part
> Hi Mike,
>
> On Fri, May 06, 2022 at 04:42:03PM +0100, Mike Zanker via users wrote:
>> 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?
>
> At the moment transfers only happen from a.authns.bitfolk.com and
> those addresses haven't changed, but if you want to add them all
> there is no harm.
>
> $ for h in a b c; do host ${h}.authns.bitfolk.com; done
> a.authns.bitfolk.com has address 85.119.80.222
> a.authns.bitfolk.com has IPv6 address 2001:ba8:1f1:f085::53
> b.authns.bitfolk.com has address 45.33.107.124
> b.authns.bitfolk.com has IPv6 address 2600:3c01:e000:259::53
> c.authns.bitfolk.com has address 172.104.29.216
> c.authns.bitfolk.com has IPv6 address 2600:3c03:e000:432::53
>
> Cheers,
> Andy
>
> --
> https://bitfolk.com/ -- No-nonsense VPS hosting
>
>