Tossing using IPv6 to access hive.blog fails

in #china5 years ago

Because hive.blog has been blocked, I have been studying whether there is any efficient solution for the past two days. The currently available solutions include the Patriotic Internet (FQ), using designated pointing peakd.com, or using eSTEEM.

PB8ro82ZpZP35bVGjGoE93K3E4U5KX8KtMBJ2rgZzsWRr2ZxUMgeuhjfUgPgw3D8Wxoosc1Wuf9oznJrqUr9c7U7JnSwyih8hLqvpSvZD6zNteJr.png
(Source: pixabay)

Although these methods can solve the problem of hive.blog access, I always feel that it is not transparent enough. If there is a method that does not add any additional constraints, it is the same as the previous access, how good it should be, so I thought IPv6 access.

In the previous article, I said that hive.blog was walled, and technically took two means:

DNS pollution
Directly reset during access
The first method prevents the correct IP from being accessed during DNS resolution, and the second method prevents you from accessing even if the correct IP can be resolved. Then if the IPv6 IP address is not blacklisted, we can bypass the shield if we cooperate with the hosts file.

First of all, I checked the IPv6 address of hive.blog, because it has been polluted by DNS, so I can't use the EzDig tool on my local machine, execute the following command on an overseas server:

dig aaa hive.blog

The content returned is as follows:

PB8ro82ZpZP35bVGjGoE93K3E4U5KX8KtMBJ2rgtp66UuKRH1sY2UrFnAQ42zQbkobpshvw66MUtRauuRX81ESxytp6d4CtpuQyhLGUyMyyMBGir.png

It can be seen that hive.blog has three AAAA records, which I added to the hosts file:

2606:4700:3030::6812:3eae hive.blog
2606:4700:3037::ac43:b52b hive.blog
2606:4700:3036::6812:3fae hive.blog

Save the file, and then open this hive.blog in the browser, prompting me with the following error message:

PB8ro82ZpZP35bVGjGoE93K3E4U5KX8KtMBJ2rhDu88z2PeMEzhtM1TSLyYb3kwWYje1ZuSQzUpdUY5eBpKTkkaSz1G2pbiRUpTet1yLsdpqkgNJ.png

It seems that maybe I have no problem with the link, but there is a problem with the SSL certificate of the site? Well, I suddenly remembered another problem, even if the certificate is okay, I should also add the IPv6 address of api.hive.blog as well, after all, it is also blocked.

However, when I tried to find api.hive.blog, I found that it did not set AAAA records:

dig aaaa api.hive.blog

The content returned is as follows:

PB8ro82ZpZP35bVGjGoE93K3E4U5KX8KtMBJ2rhnkBBdDv7odTMuZDkNWcBDu3aLakSu4Xfe1FmLkZRZwViAJBVWdF2geT2C3nkoamCa7SFUJrvi.png

So even if I really solved using IPv6 to access hive.blog, it would not solve the problem of accessing api.hive.blog. In this case, forget it, this toss ended in failure.

PB8ro82ZpZP35bVGjGoE93K3E4U5KX8KtMBJ2riBA6QdBmWFonGfnrsNRJNBZEfaPQPxnM19B3X2FcFbyfdeKoxQQ77y9ZVA9pPXokS1xGjXU2S2.png
(Source: pixabay)

Failure means failure. Who can guarantee success in every toss, or honest FQ, haha.

Translated by @doodie1996
Praise the all great work to 💕 @oflyhigh