Unable to resolve .bit domains?

https://bit.namecoin.org/
Post Reply
lmm5247
Posts: 2
Joined: Tue Jan 05, 2016 2:24 am
os: linux

Unable to resolve .bit domains?

Post by lmm5247 » Tue Jan 05, 2016 2:44 am

Hi all,

Hoping you can help me out. I'm trying to register a domain and failing, using namecoin-qt on Arch Linux. I have OpenNIC setup as my DNS and can browse other .bit TLDs (like http://dotbitkittypix.bit/), but not my own site (http://loganmarchione.bit/).
Below is the JSON string I attempted to use.

Code: Select all

{"ip":"104.131.96.168","map":{"*":{"ip":"104.131.96.168"}}}
Below is my Nginx config with the .bit domain listed.

Code: Select all

server {                                                                                                                                                                                                                                      
        listen 80;                      #Listen on IPv4
        listen [::]:80;                 #Listen on IPv6
        server_name www.loganmarchione.com loganmarchione.com www.loganmarchione.bit loganmarchione.bit;
        return 301 https://$host$request_uri;           #Redirect HTTP to HTTPS
}

server {
        listen 443 ssl spdy default_server;             #Listen on IPv4
        listen [::]:443 ssl spdy default_server;        #Listen on IPv6
        server_name www.loganmarchione.com loganmarchione.com www.loganmarchione.bit loganmarchione.bit;

        ssl on;
        #Rest of config here
}
I thought this would map my name to my VPS IP, but apparently not. What am I doing wrong? I waited over 24 hours, verified I had more than 6 confirmations, and left my client open the entire time.

Any help would be appreciated!

biolizard89
Posts: 1977
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Unable to resolve .bit domains?

Post by biolizard89 » Tue Jan 05, 2016 10:06 am

Your JSON looks fine.

With latest Namecoin Core + ncdns:

Code: Select all

user@host:~/Downloads/ncdns-2016-01-05$ dig @127.0.0.1 -p 1153 loganmarchione.bit

; <<>> DiG 9.9.5-9+deb8u4-Debian <<>> @127.0.0.1 -p 1153 loganmarchione.bit
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54908
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;loganmarchione.bit.		IN	A

;; ANSWER SECTION:
loganmarchione.bit.	600	IN	A	104.131.96.168

;; Query time: 7 msec
;; SERVER: 127.0.0.1#1153(127.0.0.1)
;; WHEN: Tue Jan 05 09:55:32 UTC 2016
;; MSG SIZE  rcvd: 63

With OpenNIC:

Code: Select all

user@host:~/Downloads/ncdns-2016-01-05$ dig @169.57.14.220 loganmarchione.bit
; <<>> DiG 9.9.5-9+deb8u4-Debian <<>> @169.57.14.220 loganmarchione.bit
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;loganmarchione.bit.		IN	A

;; Query time: 524 msec
;; SERVER: 169.57.14.220#53(169.57.14.220)
;; WHEN: Tue Jan 05 09:59:50 UTC 2016
;; MSG SIZE  rcvd: 36
So it appears to be a problem on OpenNIC's end. I'm not a fan of centralized mirrors of Namecoin; you should consider running ncdns or NMControl. (Personally I prefer ncdns, although that opinion is not unanimous among the Namecoin devs.)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

cassini
Posts: 333
Joined: Sun May 26, 2013 6:36 pm

Re: Unable to resolve .bit domains?

Post by cassini » Tue Jan 05, 2016 12:28 pm

biolizard89 wrote:So it appears to be a problem on OpenNIC's end.
It definitely is an OpenNIC problem. OpenNIC is rather slow with updating their .bit database at the moment. I made a few name_update ops with IP changes a few days ago, and OpenNIC still yields the old data.

Who to get in touch with for OpenNIC/.bit issues? This is what I could find out so far:

Code: Select all

dig @<any_opennic_will_do> example.bit TXT
displays ns9.opennic.glue and calum.at.mcalinden.me.uk in the SOA record. This indicates that ns9.opennic.glue is the .bit resolver at OpenNIC, and the maintainer is Calum McAlinden, the creator of Namecoin To Zonefile (and the owner of the bithunt.bit search engine, by the way) 8-)

lmm5247
Posts: 2
Joined: Tue Jan 05, 2016 2:24 am
os: linux

Re: Unable to resolve .bit domains?

Post by lmm5247 » Tue Jan 05, 2016 1:47 pm

biolizard89 wrote:Your JSON looks fine.

With latest Namecoin Core + ncdns:

Code: Select all

user@host:~/Downloads/ncdns-2016-01-05$ dig @127.0.0.1 -p 1153 loganmarchione.bit

; <<>> DiG 9.9.5-9+deb8u4-Debian <<>> @127.0.0.1 -p 1153 loganmarchione.bit
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 54908
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;loganmarchione.bit.		IN	A

;; ANSWER SECTION:
loganmarchione.bit.	600	IN	A	104.131.96.168

;; Query time: 7 msec
;; SERVER: 127.0.0.1#1153(127.0.0.1)
;; WHEN: Tue Jan 05 09:55:32 UTC 2016
;; MSG SIZE  rcvd: 63

With OpenNIC:

Code: Select all

user@host:~/Downloads/ncdns-2016-01-05$ dig @169.57.14.220 loganmarchione.bit
; <<>> DiG 9.9.5-9+deb8u4-Debian <<>> @169.57.14.220 loganmarchione.bit
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 37050
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;loganmarchione.bit.		IN	A

;; Query time: 524 msec
;; SERVER: 169.57.14.220#53(169.57.14.220)
;; WHEN: Tue Jan 05 09:59:50 UTC 2016
;; MSG SIZE  rcvd: 36
So it appears to be a problem on OpenNIC's end. I'm not a fan of centralized mirrors of Namecoin; you should consider running ncdns or NMControl. (Personally I prefer ncdns, although that opinion is not unanimous among the Namecoin devs.)

Wow. I was trying everything last night and was thinking "I wonder if OpenNIC isn't updating their names". That makes complete sense, I'll switch to a local DNS service. Thanks!

biolizard89
Posts: 1977
Joined: Tue Jun 05, 2012 6:25 am
os: linux

Re: Unable to resolve .bit domains?

Post by biolizard89 » Tue Jan 05, 2016 7:58 pm

Glad we could help. :)
Jeremy Rand, Lead Namecoin Application Engineer
NameID: id/jeremy
DyName: Dynamic DNS update client for .bit domains.

Donations: BTC 1EcUWRa9H6ZuWPkF3BDj6k4k1vCgv41ab8 ; NMC NFqbaS7ReiQ9MBmsowwcDSmp4iDznjmEh5

Post Reply