SteveK wrote:Nothing quite so exciting I'm afraid...I was referring to the TTL for the name servers and associated glue records on the .com gtld name servers (48hours).
Ah OK, those TTLs, I was thinking you were referring to the "www" & "forum" A records... Too bad
SteveK wrote:As condorsoaring.com seems to be self-hosted, and assuming that there is a server move involved, then they'd need to redelegate the name servers,
Yes, everything seems to point to 18.104.22.168. (NSs MX & A records...)
Well maybe there will not be a real server move and they may continue working like this.
They are already working with vhosts (www & forum both points to 22.214.171.124) and there are probably A records for beta "www" & "forum" (too bad we cannot dig for such records). If those are also hosted on 126.96.36.199 they can switch the wwwroots from current to beta websites in a few seconds to perform the switch. That's probably not the case because Steve talked about propagation time that would implicate an update from those A records...
They can also keep 188.8.131.52 as ns1 & ns2 and update the zone, then redelegate later on.
So much possibilities ... But I think monitoring those records may not be a bad idea & could lead us to some infos...
SteveK wrote:No inside information, but I don't see a specific reason to put the champagne on ice.
To put it on ice, I'll have to but some first.
I'm always too optimist