3 verified briefings on Hosting. Each story includes a plain-English summary, why it matters, and the concrete action engineering teams should take.
A Netlify user is unable to add a custom subdomain to their site, receiving an error that the domain is already in use. Despite being the administrator and creating a verification TXT record, the user requires manual intervention from Netlify's support team to release the domain.
A developer's production site went offline after they deleted their Netlify account without first removing a custom domain. Despite changing nameservers, Netlify's network continued to intercept traffic, serving a 404 error. The issue required manual intervention from Netlify support to purge the DNS zone.
A Netlify user reported their custom domain remains locked by the platform even after being removed from their project. This prevents them from connecting the domain to a new hosting provider, indicating a potential backend issue where domains are not being fully released from Netlify's system.