Re: Is *.jami.net down?

[Nathan Royce]

While I can't speak confidently of your IPv6 pings (my ISP is stuck on
IPv4 and that's my primary experience), it doesn't seem like you're
getting responses from them (considering ::1 is loopback).
And while you can ping those IPv4 addresses, are you also able to ping
the actual nameservers (what you see if you whois jami.net):
Name Server: NS1.JAMI.NET
Name Server: NS2.JAMI.NET
Name Server: NS3.JAMI.NET ?
Just out of curiosity, because I couldn't ping them, I had
http://www.ipv6now.com.au/pingme.php ping jami.net and they got
responses too.
I suppose it could just be regional, but I'd just guess they "somehow"
had the address cached (no idea why/how). Because on the flipside,
9/10 locations from https://tools.keycdn.com/ping could not get
anything (I figure they also couldn't get the IP from the
non-reachable NS).

I'm thinking this would be an issue for bootstrapping as well
(assuming the DNS wasn't cached)

On Fri, Jun 26, 2020 at 9:25 PM Óvári <ovari123@zoho.com> wrote:
>
> $ ping 184.95.250.234
> PING 184.95.250.234 (184.95.250.234) 56(84) bytes of data.
> 64 bytes from 184.95.250.234: icmp_seq=1 ttl=50 time=228 ms
> 64 bytes from 184.95.250.234: icmp_seq=2 ttl=50 time=227 ms
>
>
> $ ping 158.69.38.145
> PING 158.69.38.145 (158.69.38.145) 56(84) bytes of data.
> 64 bytes from 158.69.38.145: icmp_seq=1 ttl=47 time=230 ms
> 64 bytes from 158.69.38.145: icmp_seq=2 ttl=47 time=230 ms
>