Jump to content

Recommended Posts

Posted

Something has been wrong with Johnny lately...we've had a few different people now (one PM'd me) all with Johnny accounts that are having trouble adding domains. They're getting the message that the domain isn't pointed to our name servers, even though the domains are configured properly.

 

Here's two public examples from this week...the first I blamed on Freenom because we all know they suck in every way imaginable (and there may have been an issue with that one since I had trouble getting the DNS to show on the diagnostic tools), but the second one was just a normal .com domain with the proper settings showing.

 

https://www.helionet.org/index/topic/37975-solved-adding-freenom-domain/

 

https://www.helionet.org/index/topic/38029-domain-issue/

 

Sohamb03 reports tons of these complaints appearing on Discord lately as well.

 

Any ideas?

Posted

@flazepe: But while saying that he'd also said that these problems need to be handled individually.

 

Also, I didn't find anyone from Tommy complaining about this problem, at least the ones I attended to were Johnny users.

Posted

@flazepe: But while saying that he'd also said that these problems need to be handled individually.

 

Also, I didn't find anyone from Tommy complaining about this problem, at least the ones I attended to were Johnny users.

Same. It seems to be Johnny rn. I've seen at least 30 complaints so far between Discord and the forums over the last two weeks about it. Hell, I even made my own thread. Krydos said he would handle them individually. Still, I feel something is wrong since this came up after Johnny was rebuilt. DNS configuration gone awry?

 

And to say the least, this did happen to me on Tommy when adding https://jenova.online but all I had to do was wait for propagation for it to add. So idk.

Posted

The reason I said I'd handle them individually was because I wanted a domain that I could test, change settings, test again, change settings again, etc. Since wolstech has just been adding the domains manually I still don't have a test case to work on. I understand it's good customer service to get it fixed as quickly as possible for each particular user, but in the overall scheme of things it would be better for one user to have a broken domain for a little longer so we can fix it for everyone once and for all.

Posted

They seem to eventually fix themselves if you wait. At least one of them worked on its own (the freenom case) the following day. I suspect DNS is just being really slow for some reason.

 

That said, I'll leave a broken one for you when I get another one. :)

Guest
This topic is now closed to further replies.
×
×
  • Create New...