Thank you! and the sql database is the same or need to migrate?
No you wonât need to migrate the database if youâre just adding a new subdomain to the same account
Luckily we use DigitalPlant Domain hosting. We donât affected currently. Thatâs why self hosting is better than this solution
I have a strong opinion on DigitalPlat and would never recommend their service under any circumstances. But letâs look at this from a purely factual perspective.
The âcurrentlyâ part is the important bit.
What weâre experiencing here could happen to any domain used to provide free subdomains, including every single DigitalPlat domain. They arenât affected by this specific order, so people using those domains are safe right now. But so is anyone using the nearly three dozen other extensions we offer for free subdomains. âNot affected yetâ is not the same as âsafe.â
The only real way to avoid this is to stop using a free subdomain and get a custom domain. And to be clear: DigitalPlat domains are free subdomains. A custom domain, as Iâve used the term in this topic, is a domain registered directly under an ICANN-delegated extension like .com, .io, or .co.uk.
The one thing DigitalPlat domains give you is portability. But portability gets you nowhere if the parent domain is taken down.
Minor point, but this has nothing to do with self-hosting. Itâs a domain problem, not a hosting problem. You could run everything on a machine at home, which is undeniably self-hosting, but if itâs exposed through a DigitalPlat domain that gets taken down, your service is still down.
This is a risk of using free subdomains. It has nothing to do with free hosting.
Technically this has nothing to do with ICANN but the UK
Right, I conflated a few terms. co.uk is not actually assigned by ICANN but is in the âICANN Domainsâ list in the Public Suffix List. The key difference is that co.uk is recognized as a separate domain extension by Nominet, whereas infy.uk is just a domain that happens to be used as such. Very different status of recognition.