- Newest
- Most votes
- Most comments
If your domain status shows "serverHold," this indicates that an administrator has blocked your domain at the registrar level, which is why it's not resolving. The "serverHold" status prevents your domain from being published to the DNS, regardless of whether your name servers are properly configured.
Since you registered the domain through Route 53 but WHOIS shows a different registrar (GANDHI.NET), there might be an issue with the registration process or a discrepancy in the domain ownership records.
Here are the steps you should take:
- First, confirm the domain status by running a WHOIS lookup:
whois zillaparishadnanded.in
This will help verify the "serverHold" status and identify the actual registrar.
-
Since you registered through Route 53 but see a different registrar listed, you should contact AWS Support immediately. This is the most direct path to resolution since only the registrar can remove a "serverHold" status.
-
When contacting AWS Support, provide:
- Your domain name
- AWS account details
- The WHOIS information showing the "serverHold" status
- The discrepancy between your registration through Route 53 and the WHOIS information showing GANDHI.NET
The "serverHold" status could be due to several reasons:
- Pending domain ownership verification
- Compliance issues with the .IN registry requirements
- Administrative hold placed by the registry
- Issues with the registration process
Since this is for official local governance use, mention this when contacting AWS Support as they may be able to expedite the resolution process. Only the registrar or the registry can remove the "serverHold" status, so direct contact with AWS Support is your best course of action.
Sources
Resolve website access issues in Amazon Route 53 | AWS re:Post
Troubleshoot DNS propagation issues that occur after a domain transfer. | AWS re:Post
answered a year ago
Relevant content
asked 2 years ago

its been more than 24 hrs but no response from aws support for the case opened