It looks, the the problematic nameserver "ns-a4.io" is down. So, the problem should be disappeared...

At the same time, it looks, there is only one "ns-a3.io" nameserver working for IO domain, at now...