Both of them will resolve to whatever info is stored in d/okturtles domain.
With the (soon-to-be) DANE support (for those who forgot: DANE is about distributing TLS keys through a channel you trust (it comes from the domain you're visiting) but that is not the same as the final application (it's DNS, not HTTP/SMTP/IMAP/XMPP/etc), so you can prevent MiTM), I don't see what's missing technically to have our own internet.
> DANE is about distributing TLS keys through a channel you trust
Only to the extent that you and your visitors already have to trust your DNS provider, your domain registrar, the TLD registry, and the DNS root. Neither DANE nor DNSSEC intrinsically solve anything that hasn't already been solved for end users... particularly when you consider forwarders will have to accept unsigned zones for years to come.
Namecoin etc does go some way to "squaring Zooko's triangle" (as many good minds have discussed already) but proof-of-work chains have their own burdens, and are not any more immune to the lure of trading robustness and security for convenience than traditional DNS forwarders, online DNSSEC signing, or webmasters offering up their SSL certificates up to CDNs.
$ dig @dns.dnschain.net okturtles.bit
$ curl http://dns.dnschain.net/d/okturtles
Both of them will resolve to whatever info is stored in d/okturtles domain.
With the (soon-to-be) DANE support (for those who forgot: DANE is about distributing TLS keys through a channel you trust (it comes from the domain you're visiting) but that is not the same as the final application (it's DNS, not HTTP/SMTP/IMAP/XMPP/etc), so you can prevent MiTM), I don't see what's missing technically to have our own internet.
[0] https://github.com/okTurtles/dnschain