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

Top Page

Reply to this message
Author: Andy Bennett
Date:  
To: users
Subject: Re: [bitfolk] c.authns.bitfolk.com borken?
Hi,

> 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


Thanks Andy!

It looks like I had incorrect v4 and v6 addresses for both b. and c. in my
bind acl. I also had an old v6 entry for a. and an even older pair of
addresses for c. that had been commented out and annotate with "Expires
19th March 2012" so I guess I have the addresses from approximately that
era.

Is it possible (and if so, advisable) to use hostnames in the ACLs?
Otherwise, what's the best way to keep this information up-to-date?



Best wishes,
@ndy

--
andyjpb@???
http://www.ashurst.eu.org/
0x7EBA75FF