The Glade 4.0
https://gladerebooted.net/

Domain issues
https://gladerebooted.net/viewtopic.php?f=2&t=9077		 Page 1 of 1
Author:  Mookhow [ Wed Sep 05, 2012 11:49 pm ]
Post subject:  Domain issues
The gladerebooted.org domain has expired and it doesn't look like it autorenewed like it's supposed to. I'm trying to resolve it, but it may take a day or two to get everything updated and squared away. If you lose access, you can go to IP address 205.186.146.172. I'll also try to post updates on my Twitter account, @Mookhow2346.
Author:  Dash [ Thu Sep 06, 2012 1:14 pm ]
Post subject:  Re: Domain issues
Oops!

I think this was my fault. I just renewed it
Author:  Dash [ Thu Sep 06, 2012 1:18 pm ]
Post subject:  Re: Domain issues
I forgot my old CC was replaced so this didnt auto renew. I renewed it and I have a ticket opened with Hostmonster. I can get to the site with my phone but not the web? Anyway sorry about that.
Author:  Mookhow [ Thu Sep 06, 2012 1:22 pm ]
Post subject: 
Thanks!
Author:  Dash [ Thu Sep 06, 2012 1:44 pm ]
Post subject: 
Can you access it now? Spoke with them and it's renewed, techsupport says they can get to it but I cant. He said it might need to propagate.
Author:  Midgen [ Thu Sep 06, 2012 1:44 pm ]
Post subject: 
I had a DNS issue early this morning, but was able to navigate directly using the IP.

It seems that all is well with DNS now.
Author:  Dash [ Thu Sep 06, 2012 1:56 pm ]
Post subject: 
Ok good thanks.
Author:  Stathol [ Thu Sep 06, 2012 2:25 pm ]
Post subject:  Re: Domain issues
When the domain expired, hostmonster updated the .org nameserver records (currently maintained by aflias-net.org) for the domain to point to their "parked domain" nameservers. The TTL for those records is 24 hours, so even though the records have been updated, systems that cache DNS resolution may continue to have resolution problems until then.

It's unlikely that anyone having problems will be able to see this, but for any Windows users currently having issues, run "ipconfig /flushdns" to purge the resolver cache. If you're behind a caching DNS server, then you're probably SOL. Bypassing your DNS server with a manual query might populated your resolver cache with the right answer, but I'm not sure:

Code:
nslookup gladerebooted.org d0.org.afilias-nst.org
Author:  Vindicarre [ Thu Sep 06, 2012 3:00 pm ]
Post subject: 
Thanks guys it's back for me now.
Author:  Midgen [ Thu Sep 06, 2012 6:19 pm ]
Post subject: 
Hmm.. started failing for me again (redirect to the hostmonster parked page). I managed connect via http://205.186.146.172

Hopefully things will smooth over once the TTL expires for everyone...
Author:  Micheal [ Thu Sep 06, 2012 10:12 pm ]
Post subject: 
Hmm, I still can't access it at all.
Author:  Midgen [ Thu Sep 06, 2012 10:17 pm ]
Post subject: 
Micheal,

Try Stathols suggestion of running "ipconfig /flushdns" at a command prompt and see if that helps. It resolved my issues (hopefully once and for all).
Author:  Micheal [ Thu Sep 06, 2012 10:19 pm ]
Post subject: 
Midgen, sorry I should have put a :) at the end of that.

Teasing, nothing more, how would I have been able to post if i couldn't access the site?
Author:  Midgen [ Thu Sep 06, 2012 10:20 pm ]
Post subject: 
lol.. he posted the IP address so people could access directly. That's how I accessed earlier...
Author:  shuyung [ Fri Sep 07, 2012 8:49 am ]
Post subject:  Re: Domain issues
Stathol wrote:
When the domain expired, hostmonster updated the .org nameserver records (currently maintained by aflias-net.org) for the domain to point to their "parked domain" nameservers. The TTL for those records is 24 hours, so even though the records have been updated, systems that cache DNS resolution may continue to have resolution problems until then.

It's unlikely that anyone having problems will be able to see this, but for any Windows users currently having issues, run "ipconfig /flushdns" to purge the resolver cache. If you're behind a caching DNS server, then you're probably SOL. Bypassing your DNS server with a manual query might populated your resolver cache with the right answer, but I'm not sure:

That's not what I observed. From what I saw, the gladerebooted.org A record had a TTL of 3600, when it was pointing to the parked domain at hostmonster. This was querying a caching platform run by Neustar. Querying Google's public caching servers simply returned an NXDOMAIN. The A record now has a TTL of 14400. I suspect what you were retrieving was the SOA record.
Author:  Stathol [ Fri Sep 07, 2012 10:19 am ]
Post subject:  Re: Domain issues
This is what I was getting yesterday early AM:

Code:
stathol@gladerebooted:~/.irssi$ host -v gladerebooted.org b2.org.afilias-nst.org | less

Trying "gladerebooted.org"
Using domain server:
Name: b2.org.afilias-nst.org
Address: 199.249.120.1#53
Aliases:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41901
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;gladerebooted.org.     IN  A

;; AUTHORITY SECTION:
gladerebooted.org.  86400   IN  NS  parking2.hostmonster.com.
gladerebooted.org.  86400   IN  NS  parking1.hostmonster.com.

Received 96 bytes from 199.249.120.1#53 in 0 ms
Trying "gladerebooted.org"
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4221
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;gladerebooted.org.     IN  AAAA


If you queried parking1.hostmonster.com for the gladerebooted A record, that may well have had a 3600 TTL. But the problem wasn't that they changed the A records for the domain. Rather, they delegated the zone to completely different nameservers at the .org level. TLD-level NS records always have a 24-hour TTL. Or at least that's the case for the .com, .org, and .net registries as far as I can tell.
Author:  shuyung [ Fri Sep 07, 2012 11:27 am ]
Post subject: 
Ah, I see now what you're saying.

Yes, the fact that parkingN.hostmonster.com respond to all queries with the parking.hostmonster.com IP, and the fact that everybody is querying some sort of caching nameserver, and that it takes 24 hours for the glue records to age out of those from the instance of initial resolution means that until the NS records age out, any caching server with those records would continue to query parkingN.hostmonster.com.
Author:  Midgen [ Fri Sep 07, 2012 11:58 am ]
Post subject: 
I had trouble again this morning connecting via the domain name.

Currently connected via the IP.
Page 1 of 1 All times are UTC - 6 hours [ DST ]
Powered by phpBB® Forum Software © phpBB Group
https://www.phpbb.com/