cinder needle
I used the BH "move server" service, and it seems to have moved the server, but failed to move the server's IP name/address mapping. The DNS record for the server name still points to the server's old IP address in New Jersey.
Yes I know you server owners can't do anything about this. I'm documenting the problem here so that:
fallow harness
I dont follow exactly what the issue here is, but id submit a ticket @cinder needle
If its an issue w/ the move system, itd be our dev team but my hunch is the move itself just never went through hah
cinder needle
I dont follow exactly what the issue here is, but id submit a ticket <@385996612...
Already have. Agent is saying "The sub domain can take up to 24 hours after a location move to update. "
fallow harness
Oh this was specific to the subdomain?
24 hours is a bit long, typically its about 4-5; but that is accurate yep
Does direct IP work?
cinder needle
Yes, direct IP works, but I've trained my users not to use raw IP addresses, but instead use IP names. Humans should not have to type numbers.
Why would a DNS record update take so long?
fallow harness
Its not an exact 4-5 hours, thats just the typical window for how long to wait before reporting an issue
Lots of variables in DNS stuff 😅 It could be a basic ISP caching issue that makes it take 2 hours; other times its instant
Its just cause of how many different users it affects, if that makes sense 👀 Its a "Wait this long" window, not a "This is how long itll take to work"
cinder needle
Forgive me for "arglebargle" raging, but the initial subdomain creation was a 5 minute event.
fallow harness
Yep! Same for me, but moving it took about an hour and a half; whereas for my friend it was working within minutes
Lots of variables xD Very few are actually something we can make quicker than it already is; I'll raise it internally to see if we can do anything abt the wait window, but as far as I know its a fairly standard thing. Some webhosting sites even say to wait 24-48
cinder needle
Lemme give you something to look at. It ... makes my brain hurt.
I was merely hoping DNS would tell me who the authoritative server was, so I could query directly.
Just poking DNS to see "is this a propagation issue" or "is this a BH hasn't updated the (A) record yet" issue?
fallow harness
🤔 weird
Mind dming me your panel URL?
ah found it! ignore hah
Yeah checking a few ways on this DNS the A Record outright doesnt look like it got updated 🤔 I wonder how long that takes.. 🤔
Will check internally, may not hear until the AM though 😅 late night!
Realistically to get around this you could change the subdomain, but I get thats not ideal
cinder needle
FYI nslookup is still reporting the same (out-of-date) IP address
Also FYI, Today I Learned that DNS intentionally crippled "ANY" queries a little while back. Because people are awful.
OK WTF @fallow harness
So in addition to "why hasn't my subdomain updated", we have an additional problem of "why is cloudns saying it is authoritative for bh-games.com but returning non-authoritative answers for my subdomain?"
This DNS server is incorrectly configured (IMHO).
fallow harness
Soz for the delay 👀 I looked around internally and this timer def shouldve swapped by now. Poke our team in that ticket you had and let me know the ticket #, I'll get it to our Sys teams box to gander and do some digging 🙂
cinder needle
54895
And I thought you were on 2nd shift (based on you replying last night). So seeing you reply here & now is in no way "delayed".
You may also want to fire off a second torpedo to go look at the CloudNS configuration. It ain't right to both be authoritative and non-authoritative for the same domain.
cinder needle
Soz for the delay 👀 I looked around internally and this timer def shouldve swap...
#54895
fallow harness
And I thought you were on 2nd shift (based on you replying last night). So seein...
Im salaried 🤣 I just happened to be around last night so I lended a hand; I get paid the same, might as well 👀
Im typically in during the day for US
Peekin at the ticket and I'll pass it up!
cinder needle
Good on you. I feel slightly guilty at pinging you on this, but I feel like the tier 1 guys (Andrew and Jake) don't understand that what is happening (or rather not happening) feels like there's a bug in the "move server" program. Can I send you cookies to buy more ping permissions? LOL
fallow harness
They know their stuff! Its more likely its just following protocol hah ; most DNS stuff is wait upto 24h ~ this one just seems off
I hollered at em about it, should get sorted 🙂
cinder needle
And the DNS stuff -- well, that's just wrong.
cinder needle
They know their stuff! Its more likely its just following protocol hah ; most DN...
When I said "DNS stuff" I mean the SOA weirdness. How can dns31 be both authoritative and non-authoritative at the same time?
cinder needle
Oh thats a question I couldnt tell ya 🤣
Honestly I'm not DNS-adept enough to explain how one would do this. I merely look at it as a semi-literate user and go "WTF?"
fallow harness
fallow harness
Euf. Poked the Sys peeps!
On the end of the record itself, the dev teams gonna have to fix why it takes so long; checking if they can manually update that ~
fallow harness
Peek now? 👀 Devs showed the view for it, seems to be pointing at the right IP now
cinder needle
Yep. dns31 gives correct IP address now
fallow harness
Devs went on a bit of a goosechase, but from what they can see it does update automatically, so that really was just a really bad wait time on the DNS side of things
Good to know, unfortunate it took almost 24h to propogate 😅
cinder needle
No. We obliterated the original problem with the "turn it off/on" solution (change the subdomain and then change it back). I don't think we can safely chalk it up to "DNS propagation". dns31.cloudns.net is claiming to be the authority for bh-games.com, so there's no DNS propagation factor involved (propagation is DNS server-to-server delays).
If dns31 were giving the correct (new) IP address ((A) record), and my local DNS were giving the old one, that would be propagation delay.
My hypothesis is: Some part of the "move server" program should have noted the assigned subdomain and issued a DNS (A) record update once the server move had occurred. It did not.
(In fact, in an ideal world the "move server" program should note the subdomain, delete the existing (A) record at the start of the migration, and then create a new (A) record once the move is complete. But simply updating the (A) record once moved would be "close enough".)
Because technically during the move the server does not exist.
fallow harness
Yep that’s exactly the goosechase part 😅
From what we can tell, the update did run right when the IP transferred, but on CloudDNS’s side the existing record didn’t fully refresh. Even though the nameserver is authoritative, it kept serving the old IP because the record itself wasn’t rebuilt yet.
Changing the subdomain basically forced CloudDNS to throw the old record away and generate a fresh one, which is why that fixed it immediately.
To correct myself, its not quite “DNS propagation”, just a really unfortunate delay in how the DNS provider refreshed the record internally
cinder needle
(Hmmm I wonder if I should request billing credit for those 2-ish hours last night... 😆 j/k )
fallow harness
I'll be seeing if we can do anything to speed that up, but it is working as intended after digging a bit w/ the devs
rapid marsh
Just for clarification, I understand the frustration but we don't allow people to circumvent the swear filter by altering swear words, so I'll remove the original and post the message here without the colorful language 💙
You may want to look at the ticket again. Or maybe not. Your call.
At your insistence, I changed the subdomain from “teampz” to “team-pz”. I observed the creation of a new (A) record for “team-pz” in your nameserver “dns31.cloudns.net”. I then changed the subdomain from “team-pz” back to the original “teampz”. Your nameserver dns31.cloudns.net is still returning the out-of-date IP address for “teampz” and also returning the (A) record for “team-pz”; a subdomain which no longer exists.
cinder needle
Just for clarification, I understand the frustration but we don't allow people t...
Understood.
cinder needle
Yep that’s exactly the goosechase part 😅
From what we can tell, the update did...
Yeah, there's something not right there. Someone with deep understanding of how CloudNS API (I assume) works should be investigating how that update failed. And why CloudNS is both authoritative and non-authoritative simultaneously. You've got a Schrödinger's NameServer there...
somber zinc
I wanted to wait for this issue to be wrapped up before replying... but I feel like this needs to be said. @cinder needle
cinder needle
She sounds horrible!
cinder needle
Just for clarification, I understand the frustration but we don't allow people t...
I understand the reason for the rule (see above: "people are awful") But in my defense I wasn't hurling said swear words at BH, just at the situation. (I don't want to leave later readers thinking I was swearing at Jake or Andrew or anyone else at BH.)
Y'all have tough jobs -- the only time you interact with customers is when they are unsatisfied. But be thankful: you don't have Dylan's job!
rapid marsh
I totally understand! No worries. It wasn't that I thought you were being abusive towards staff, just keeping the PG13 rule in place, no matter of the context if it would be deleted by our bot for triggering the swear filter, I'll delete the message that doesn't get caught because an altered swear word slipped by the bot :)