611 (SixEleven, SIL)
PatrickMacH, can I know why this coin name is 611?? 611 subdomain in .to zone or 611000 total coins?
Looking forward in creating my domain name under the SIL platform I have already some dns collections on the namecoin blockchain but going to add more on the SIL platform, this is a good project to join with because of the decentralization of the www in the near future and the mission of free information around the world!
Hm... What about decentralization of the Neuronet in near future?
P.S.:
Hey, guys! Do you know any extensions to specify dns server in URL?
Why I cann't specify this server in url directly with any special symbol,
like:
http://nf.bit~52.174.55.168/ or
http://nf.bitØ52.174.55.168/
to get ip of server with opened page for site
http://nf.bit/where domain name nf.bit was been resolved by OpenNIC PUBLIC DNS server 52.174.55.168?
So then I can specify in the settings for extencion the DNS servers for the some zones in the list,
for resolving:
.bit domains from OpenNIC PUBLIC DNS,
611.to from Tongo servers,
.onion domains from another different TOR public DNS, etc...
Also can be used DNSCrypt in this case and peer exchange of this data in DHT.
P.P.S:
My idea is about setting up a small DB based DNS cloud for a subdomain, like i.e. dyndns.611.to:
Using an optional field of the d/Example field can be used by any router to auto-setup or update the corresponding example.dyndns.611.to DDNS record.
Hey,
PatrickMacH!
For using DDNS we can just using "alias" JSON-parameter in domain settings
and specify there ddns domain name with a dot in the end,
to do DNS-redirect nice_611_domain_name to not_nice_domain_name_from_any_ddns_service.
But Tongo DNS servers not resolving all DDNS domain names and some sites, and that's problem.
You can set up there a DNS-cache service with copy data from another DNS
to do resolving for any another domain names on this server.
And if with alias I will add NS servers from DDNS service,
where dyndns domain name is resolving, then 611 domain cann't be found there.
So in this case I think I need to specify there PUBLIC OPEN DNS SERVERS as NS servers
that is fast resolving both domain names (myname123.611.to and myname123.dyndns.bit).
After all I see only one transaction for name_update with one value:
{"alias":"dyndns_name.twodns.de.", "ns": ["ns1.PUBLIC_DNS_for.both", "ns12.PUBLIC_DNS_for.both"]}
But, if i using public DNS as NS servers from where I got resolving both domains,
then I cann't find there my domain_NAME.611.to
and when I try to resolving 611.to domain through your ns servers (c.ns.buddyns.com)
I see this:
>nslookup my_domain_name.611.to c.ns.buddyns.com
Name: my_domain_name.611.to
Served by:
- my_domain_name.ns-glue.611.to (What is this?)
8.8.4.4, 51.255.48.78 (google public DNS and openNIC public DNS that I specify as NS servers)
my_domain_name.611.to (my domain name)
As you can see your ns servers cann't resolving 611.to name then.
So in this case to do DDNS for my 611.to domain,
I just can using this JSON-string in domain parameters:{"alias":"dyndns_name.twodns.de."}
Without specify any NS-servers.
Then I can open the site on my_name.611.to and I see IP updating through DDNS!
But look at this response from 611.to ns servers...>nslookup dyndns_name.twodns.de c.ns.buddyns.com
DNS request timed out.
timeout was 2 seconds.
*** Can't find server name for address 88.198.106.11: Timed out
Server: UnKnown
Address: 88.198.106.11
DNS request timed out.
timeout was 2 seconds.
DNS request timed out.
timeout was 2 seconds.
*** Request to UnKnown timed-out
Directly not resolving...
