Getting the server move page still for Halforums

PatrThom · Jan 15, 2014

Dave said:
Greg Middlesworth?

Code:

Domain Name: HALFORUMS.COM
Registry Domain ID: 1566337760_DOMAIN_COM-VRSN
Registrar WHOIS Server: whois.enom.com
Registrar URL: www.enom.com
Creation Date: 2009-08-20 21:07:00Z
Registrar Registration Expiration Date: 2015-08-20 21:07:00Z
Registrar: ENOM, INC.
Registrar IANA ID: 48
Registrar Abuse Contact Email: abuse@enom.com
Registrar Abuse Contact Phone: +1.4252744500
Domain Status: clientTransferProhibited
Registry Registrant ID:
Registrant Name: GREG MIDDLESWORTH
...

--Patrick

Dave · Jan 15, 2014

The fuck?[DOUBLEPOST=1389795501,1389795424][/DOUBLEPOST]

Dave said:
The fuck?

Never mind. He's the president of URLJet. We still are being registered through them. I haven't looked there to make sure everything is fine so I will go look.[DOUBLEPOST=1389795680][/DOUBLEPOST]I had the nameservers out of order. I had #1 as #1 but #2 was pointing to #3 and #3 was pointing to #2. Not sure that makes a difference, but I made the correction just in case.[DOUBLEPOST=1389795912][/DOUBLEPOST]Well, I tried to. They switched back after saving. Hurm.

GasBandit · Jan 15, 2014

It doesn't make a difference.

Dave · Jan 15, 2014

Well that's good then. I've also said something to the host to see what he can see.

GasBandit · Jan 15, 2014

Interesting. OpenDNS just lost you, but Google DNS still has you.

Dave · Jan 15, 2014

I removed #3 and forced #1 & #2 only. I talked to the host and they said it absolutely matters that they point to the right nameserv.

GasBandit · Jan 15, 2014

Dave said:
I removed #3 and forced #1 & #2 only. I talked to the host and they said it absolutely matters that they point to the right nameserv.

Well, yes, it matters they point to the right nameservers, but the order they're listed in is irrelevant, except for that you want them in descending order of mainstream use. IE, #2 is for if #1 fails, and #3 is for if #2 fails. Putting 2 and 3 in as 3 and 2 wouldn't stop it from working unless they have a couple bad nameservers in their own network, and gave them to you to use.

Dave · Jan 15, 2014

I probably did that by removing #3. I have put it back and am going to leave it alone.

PatrThom · Jan 15, 2014

I am learning so much from just this little thing.

--Patrick

Shakey · Jan 15, 2014

PatrThom said:
I am learning so much from just this little thing.

--Patrick

The best way to learn is to start breaking stuff!

PatrThom · Jan 15, 2014

I don't have my own site yet, but I probably will soon (I've had a domain parked for years, just no site), so I've never had to deal with all this stuff. I'd rather have some exp under my belt when I start, y'know?

--Patrick

PatrThom · Jan 15, 2014

stienman said:
Catch 22.

I wish I could find the link to that Kris Straub comic where he talks about exactly this.

--Patrick

PatrThom · Jan 15, 2014

I have a server of my own that I could use (two of them, actually. Three if I were to put more parts together), I just can't afford the time to do so right now for funsies, and I have nothing urgent that would require it.

--Patrick

PatrThom · Jan 17, 2014

Huh.

I just got the "domain_name_could_not_be_resolved" message...even though I have the site's IP address hard-coded in the hosts file on my DNS server. Something is really weird.

--Patrick

PatrThom · Jan 17, 2014

No. But previously I was working around it by accessing the site directly with http://xx.xx.xx.xx/xenforo/portal without issue.

--Patrick

Shakey · Jan 24, 2014

Anyone else still getting it? I still get it from time to time on my computers not using google dns.

Dave · Jan 24, 2014

Shakey said:
Anyone else still getting it? I still get it from time to time on my computers not using google dns.

I opened a ticket with the host today. He said he found something cycling the DNS and made a change. I'll post more about it in the morning, but it's being addressed.