Wit's end with registering domains: can't reach them

hbbtstar
Posts: 6
Joined: Tue Nov 05, 2013 7:12 pm
Contact:

Wit's end with registering domains: can't reach them

Post by hbbtstar »

Hey everyone! New namecoin user, love the idea, but can't seem to figure it out. Here's what the deal is. I have some namecoins, and I registered them using the namecoin-qt client for Windows: it did the new_name, the firstupdate, everything. I have two domains currently- here they are with the JSON queries that were issued with them.

d/carlosdanger {"ns":["ns1.ghostwriterintl.com","ns2.ghostwriterintl.com"]}
d/ghostwriterintl {"ip":"67.222.130.14","map":{"*":{"ip":"67.222.130.14"}}}

Now, I registered the first one first, and it didn't work. I figured I had set up the bind zone file incorrectly, even though it looked alright, so I decided to try a new one. The second one, ghostwriterintl.bit, uses just the IP address, but it still doesn't redirect correctly. When I dig it I get this:

Code: Select all

; <<>> DiG 9.9.2-P1 <<>> ghostwriterintl.bit
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 25464
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

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

;; AUTHORITY SECTION:
ghostwriterintl.bit.    600     IN      SOA     ns.dot-bit.bit. hostmaster.ns.dot-bit.bit. 79372503 21600 3600 604800 3600

;; Query time: 109 msec
;; SERVER: 178.32.31.43#53(178.32.31.43)
;; WHEN: Tue Nov  5 23:19:15 2013
;; MSG SIZE  rcvd: 98
which doesn't have an ANSWER section that should have my server's IP in it. The server is configured for .bit support, it can resolve other .bit domains fine, as can my computer: is there some other step I'm missing here? Have I done something wrong? Thanks again!

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

Re: Wit's end with registering domains: can't reach them

Post by cassini »

Regarding d/ghostwriterintl:
You can't use the IP 67.222.130.14 because it is not a unique address, i.e. some other domains are on the same address. See
http://whois.domaintools.com/67.222.130.14

The easiest workaround could be the translate or the alias option. Try

Code: Select all

{"translate":"ghostwriterintl.com."}
(yes, there is another "." after the .com)

Always remember: it may take up to 24 hours before the .bit-enabled DNS servers absorb the new info.

EDIT: Just checked the translate method, and the DNS servers are responding in an unexpected way at the moment. Something must have changed during the last few month. I'm going to look into this and post my findings later.


Regarding d/carlosdanger:
This is the more complicated thing. It is something to do with named.conf on the ns if I remember correctly, and maybe one or two more files. Google is your friend.
Last edited by cassini on Tue Nov 05, 2013 9:32 pm, edited 1 time in total.

hbbtstar
Posts: 6
Joined: Tue Nov 05, 2013 7:12 pm
Contact:

Re: Wit's end with registering domains: can't reach them

Post by hbbtstar »

Thanks so much for the prompt reply! I will make the update and get back to you. I was tearing my hair out :)

as for the other one, I followed the tutorials on dot-bit.org for setting up a zone file. Here's what they look like:

named.conf.local

Code: Select all

zone "carlosdanger.bit" {
        type master;
        file "/etc/bind/dotbit/carlosdanger.bit";
        allow-query { any; };
        check-names ignore;
};
and here's /etc/bind/dotbit/carlosdanger.bit:

Code: Select all

$TTL 86400

@       IN      SOA     ns1.ghostwriterintl.com.      hostmaster.carlosdanger.bit. (
                        2013110103      ; serial number YYMMDDNN
                        28800           ; Refresh
                        7200            ; Retry
                        864000          ; Expire
                        86400           ; Min TTL
                        )

                NS      ns1.ghostwriterintl.com.
                NS      ns2.ghostwriterintl.com.

                MX      10 mail.ghostwriterintl.com.
                MX      20 mail.ghostwriterintl.com.


$ORIGIN carlosdanger.bit.

carlosdanger    IN      A       5.39.95.17
*.carlosdanger  IN      A       5.39.95.17
the bind server works perfectly otherwise, so I can't figure out what the problem might be. Thanks so much again for the first!

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: Wit's end with registering domains: can't reach them

Post by phelix »

Actually redirecting to an existing ICANN domain has never worked for me. If you or cassini can do it please explain how.

I had to register my .bit domains with my provider:
http://dot-bit.org/forum/viewtopic.php?p=2196#p2196
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

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

Re: Wit's end with registering domains: can't reach them

Post by cassini »

I need to do more research this weekend as khal seems to have changed the settings of his DNS server (recursion doesn't work atm). Going to check all the other DNS server listed in the wiki, too.

phelix wrote:Actually redirecting to an existing ICANN domain has never worked for me
Try
http://steamcommunity.bit/
(uses translate and alias)


Always try the plain and the www variant when experimenting
(e.g. http://nf.bit/ and http://www.nf.bit/)
Not only that maybe someone didn't bother mapping "www" or "*" (phelix?! ;) )
but also because "alias" works only for the www subdomains as far as I remember.


By the way, http://www.dtdns.net/ provide a free service for another method for redirecting, but you need a unique IP.
However, it even works for dynamic IPs, e.g. if your service provider assigns you a different IP every day. Most WLAN routers are able to send their IP data to services like dtdns.net.
Try
http://radio.bit/
(d/radio has a translate record that points to biteater.dtdns.net which redirects to the IP of a German IT magazine at the moment:

Code: Select all

{"translate":"biteater.dtdns.net."}

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: Wit's end with registering domains: can't reach them

Post by phelix »

cassini wrote:I need to do more research this weekend as khal seems to have changed the settings of his DNS server (recursion doesn't work atm). Going to check all the other DNS server listed in the wiki, too.

phelix wrote:Actually redirecting to an existing ICANN domain has never worked for me
Try
http://steamcommunity.bit/
(uses translate and alias)
My guess is the server at that ip knows about the domain "steamcommunity.bit"
Always try the plain and the www variant when experimenting
(e.g. http://nf.bit/ and http://www.nf.bit/)
Not only that maybe someone didn't bother mapping "www" or "*" (phelix?! ;) )
but also because "alias" works only for the www subdomains as far as I remember.
Is there still anybody using "www."?
By the way, http://www.dtdns.net/ provide a free service for another method for redirecting, but you need a unique IP.
However, it even works for dynamic IPs, e.g. if your service provider assigns you a different IP every day. Most WLAN routers are able to send their IP data to services like dtdns.net.
Try
http://radio.bit/
(d/radio has a translate record that points to biteater.dtdns.net which redirects to the IP of a German IT magazine at the moment:

Code: Select all

{"translate":"biteater.dtdns.net."}
Does not work for me...
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

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

Re: Wit's end with registering domains: can't reach them

Post by cassini »

phelix wrote: http://radio.bit/
...
Does not work for me...
Oops, sorry. The original URI is:
http://www.radio.bit/
Furthermore, this example works only if it's 178.32.31.41 in the dns settings.

phelix
Posts: 1634
Joined: Thu Aug 18, 2011 6:59 am

Re: Wit's end with registering domains: can't reach them

Post by phelix »

cassini wrote:
phelix wrote: http://radio.bit/
...
Does not work for me...
Oops, sorry. The original URI is:
http://www.radio.bit/
Furthermore, this example works only if it's 178.32.31.41 in the dns settings.
Cool, works. A .bit domain to a dyndns.
you need a unique IP
hmmm :?

This gave me an idea... --> extra post.
phelix wrote:
cassini wrote:I need to do more research this weekend as khal seems to have changed the settings of his DNS server (recursion doesn't work atm). Going to check all the other DNS server listed in the wiki, too.
phelix wrote:Actually redirecting to an existing ICANN domain has never worked for me
Try
http://steamcommunity.bit/
(uses translate and alias)
My guess is the server at that ip knows about the domain "steamcommunity.bit"
:roll: no. I get the same result as going directly to the ip: http://63.228.223.103
nx.bit - some namecoin stats
nf.bit - shortcut to this forum

hbbtstar
Posts: 6
Joined: Tue Nov 05, 2013 7:12 pm
Contact:

Re: Wit's end with registering domains: can't reach them

Post by hbbtstar »

So just an update: this JSON string didn't work:

Code: Select all

{"translate":"ghostwriterintl.com.", "alias":"ghostwriterintl.com."}
I still can't ping or access the server. I will continue researching, but I thought I would update the thread. Thanks again for everyone helping me / following this!

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

Re: Wit's end with registering domains: can't reach them

Post by cassini »

This is only an observation, and I am not sure if this has anything to do with it: When I enter
http://ghostwriterintl.com/
in the address field of any browser, it automatically switches to
http://www.ghostwriterintl.com/
Maybe the .bit enabled DNS servers/proxies can't handle this.

It's been ages ago when I managed to make a nameserver work like this, or is it the httpd.conf of an apache server? Can't remember.

Post Reply