Domains not resolving
Posted: Sun Aug 31, 2014 2:19 pm
Hi,
I'm having trouble getting my domains to resolve.
I can browse .bit domains listed on dotbit.me's multiple choice index without a proxy just fine. I have my DNS set to OpenNIC, so they resolve.
But none of mine are working, & after many name_update operations trying to get it right, I have to ask for help.
I have 1 set to translate to another ICANN domain, & its nameservers are set to their proper names. I've tried setting the 'Translate' field to include a preceding 'http://', & I've tried it without, either way it doesn't work. The domain it points to loads fine from a browser, & I know its nameservers are working because I have the domain registered at Gandi, but redirect the DNS controls to another provider by setting the Gandi nameservers to these same nameservers, and that works fine. That domain is minedirt.bit.
I have another set to an IP address that won't resolve either. I can load the webserver's default, non-virtualhost webpage fine when I navigate to the IP address directly, but I can't test the functionality of the virtual host configuration, because nothing will resolve there with a domain name for it to identify & deliver the right root directory based on that. That domain is universitysports.bit.
I have other domains set the same way as these 2 are, they've completed their most recent name_update operations days ago, & they still don't resolve, so I don't think it's an issue of propagation.
Another interesting fact is that none of my domains show up on dotbit.me's multiple choice index, but they do show up as being unavailable when I run a query for them. So I'm guessing there's no IP address visible somehow?
They're hosted on an Amazon EC2 with elastic IP, & I don't know if that's an issue. Again, I can load the defacto root directory's index.html when I navigate to the server via IP address in Chrome. Maybe EC2 blocks domains resolved via .bit?
I've tried both of the Namecoin proxy extensions for Chrome, & I prefer to use OpenNIC DNS that just does .bit's automatically to keep it simple. I don't see why other .bit's would load but not mine.
I have no idea what the issue could be, they seem to be set properly, as I understand it. I just enter the data into the fields in the client like normal. But maybe I've got something wrong...
Could someone provide some insight please?
Many thanks.
-F
I'm having trouble getting my domains to resolve.
I can browse .bit domains listed on dotbit.me's multiple choice index without a proxy just fine. I have my DNS set to OpenNIC, so they resolve.
But none of mine are working, & after many name_update operations trying to get it right, I have to ask for help.
I have 1 set to translate to another ICANN domain, & its nameservers are set to their proper names. I've tried setting the 'Translate' field to include a preceding 'http://', & I've tried it without, either way it doesn't work. The domain it points to loads fine from a browser, & I know its nameservers are working because I have the domain registered at Gandi, but redirect the DNS controls to another provider by setting the Gandi nameservers to these same nameservers, and that works fine. That domain is minedirt.bit.
I have another set to an IP address that won't resolve either. I can load the webserver's default, non-virtualhost webpage fine when I navigate to the IP address directly, but I can't test the functionality of the virtual host configuration, because nothing will resolve there with a domain name for it to identify & deliver the right root directory based on that. That domain is universitysports.bit.
I have other domains set the same way as these 2 are, they've completed their most recent name_update operations days ago, & they still don't resolve, so I don't think it's an issue of propagation.
Another interesting fact is that none of my domains show up on dotbit.me's multiple choice index, but they do show up as being unavailable when I run a query for them. So I'm guessing there's no IP address visible somehow?
They're hosted on an Amazon EC2 with elastic IP, & I don't know if that's an issue. Again, I can load the defacto root directory's index.html when I navigate to the server via IP address in Chrome. Maybe EC2 blocks domains resolved via .bit?
I've tried both of the Namecoin proxy extensions for Chrome, & I prefer to use OpenNIC DNS that just does .bit's automatically to keep it simple. I don't see why other .bit's would load but not mine.
I have no idea what the issue could be, they seem to be set properly, as I understand it. I just enter the data into the fields in the client like normal. But maybe I've got something wrong...
Could someone provide some insight please?
Many thanks.
-F