My first work, too decentralize The DNS, A Extension for the ZeroName Plugin

@caryoscelus @HelloZeroNet
Iam so happy now!

You have right, decentralize, the dns.

I hope you like my work.

Its not much but its my first plugin.

To show that ZeroNet is not dead, I'm opening this issue.

ZeroNameExPlugin Pull Request:

https://github.com/HelloZeroNet/ZeroNet/pull/2861

Please look it, puhh much work....and much trial and error.....xD

So new update

The ZeroNameExPlugin.json can now do something really cool...

In the event that no resolver knows the domain, it can still resolve it... Huh?

It gets the domain from the content.json.

Every resolver can overwrite the domain field from the content.json.

"content_json_domains": {

"Blog.ZeroNetwork.bit": "1BLogC9LN4oPDcruNz3qo1ysa133E9AGg8",

"Sites.ZeroNetX.bit": "1SitesVCdgNfHojzf2aGKQrD4dteAZR1k",

"Talk.ZeroNetwork.bit": "1TaLkFrMwvbNsooF4ioKAY9EuxTBTjipT"

},

So thats mean, you can resolve on every time the domain and you can on every time change your domain records...

I was told that I should also open the pull request at zeronet-conservancy and at the ZeroNetX fork...

Phew, so many forks....

Okay then I'll make a fork now too haha ​​just kidding

Add reverse dns cache for faster resolve domain entries in the ZeroNet\plugins\ZeronameEx\ZeroNameExPlugin.json

"content_json_domains": {
"1BLogC9LN4oPDcruNz3qo1ysa133E9AGg8": "Blog.ZeroNetwork.bit",
"1SitesVCdgNfHojzf2aGKQrD4dteAZR1k": "Sites.ZeroNetX.bit",
"1TaLkFrMwvbNsooF4ioKAY9EuxTBTjipT": "Talk.ZeroNetwork.bit",
"Blog.ZeroNetwork.bit": "1BLogC9LN4oPDcruNz3qo1ysa133E9AGg8",
"Sites.ZeroNetX.bit": "1SitesVCdgNfHojzf2aGKQrD4dteAZR1k",
"Talk.ZeroNetwork.bit": "1TaLkFrMwvbNsooF4ioKAY9EuxTBTjipT"
},


Split content json addresses and domains

--bit_resolvers argument is the resolvers field

for questions please ask me, but now you can share zites, and everybody on the planet can use the domain from your zite.....

Bắt đầu bằng việc xem xét pull request được liên kết #2861 và ZeroNet/plugins/ZeronameEx/ZeroNameExPlugin.json. So sánh các ánh xạ content_json_domains được đề xuất và hành vi của --bit_resolvers với mô tả issue. Công việc được xem là hoàn tất khi cache DNS ngược và việc phân giải domain dựa trên content.json đã được triển khai và xác minh trong luồng plugin liên quan.

Do mô hình lập chỉ mục viết ra từ nội dung của issue.