You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The name server of domcloud.io (New York server) cannot be resolved after 3am (UTC) on June 4th.
I've confirmed this, so I think I was influenced by the work involved: #10
PS C:\Users\balloon> dig domcloud.io "@8.8.8.8"
;; QUESTION SECTION:
;domcloud.io. IN A
domcloud.id (Singapore server) and the website are working and you can log in to the portal from https://domcloud.id/ .
So I reported to the domcloud-io repository.
The text was updated successfully, but these errors were encountered:
Okay. I can see the normal display of the whole .domcloud.io.
It is not shown in Status and may need to be adjusted.
The issue here has been resolved so I can close it, but maybe you'll have a few days of hard work involved. 😫
May DOM Cloud continue to operate in good condition.
Well, technically it's still correct that it's operation. The system runs just fine, just unable to resolve to the vanity domain to domcloud.io. We may put more diagnostics later on.
The name server of
domcloud.io
(New York server) cannot be resolved after 3am (UTC) on June 4th.I've confirmed this, so I think I was influenced by the work involved: #10
domcloud.id
(Singapore server) and the website are working and you can log in to the portal from https://domcloud.id/ .So I reported to the
domcloud-io
repository.The text was updated successfully, but these errors were encountered: