
Netlify Domain Alias Error Blocks Users
TL;DR: 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.
Key facts
- Category
- Infrastructure
- Impact
- Low
- Published
- Source
- Netlify Community
Full summary
A Netlify user reports a persistent domain alias error, unable to add a subdomain even after proving ownership with a TXT record.
A user on the Netlify Community forum reported an issue when trying to add a subdomain to their site, receiving the common error message: “Another site is already using this domain.” This problem occurs when a domain name gets stuck or remains associated with a different Netlify account, even if that account is old or unused. The user confirmed they are the domain administrator and have full server access. To prove ownership, they followed Netlify's standard procedure by creating a specific TXT verification record on their nameservers. However, this automated step was not sufficient to resolve the issue, forcing them to request direct assistance from Netlify's support engineers to manually clear the block.
This situation highlights a recurring operational challenge for developers and IT teams using the Netlify platform. The inability to self-resolve a domain ownership conflict can cause deployment delays and frustration. While Netlify provides a verification method, the process still requires manual intervention from their support team in certain cases. This dependency can be a bottleneck, especially for teams on tight deadlines or those without premium support plans. The issue underscores the importance of robust domain management tooling within PaaS platforms, ensuring that legitimate domain owners can reclaim and assign their domains without significant friction or waiting for support tickets to be processed.
Why it matters
The issue highlights a recurring operational bottleneck on Netlify, where developers cannot self-resolve domain ownership conflicts and must rely on manual support intervention, potentially causing project delays.
Business impact
Deployment delays for new websites or marketing pages can occur when teams are unable to quickly assign a custom domain. This reliance on manual support creates a bottleneck, impacting project timelines and agility, especially for businesses without premium support plans.
Tags
Primary source: Netlify Community