- 最新
- 投票最多
- 评论最多
Make sure you are not working in a private hosted zone. NS records (and delegation) are not supported in this zone type.
I also see NS grayed out when trying to use this procedure on a private hosted zone. Please see: https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/hosted-zone-private-considerations.html#hosted-zone-private-considerations-delegating-subdomain
Make sure you are putting the subdomain (lab) in the "Record name" field of the "Create record" box. When you leave that blank, it greys out the NS record option because you can only have one NS record for that domain (example.com).
That doesn't appear to be helping.
- Click into the "Record name" text box with the mouse.
- Type "lab".
- Hit tab key 5 times (The "info" link next to "Record type", Skip past the "Record type" dropdown leaving "A" in place, the "info" link next to "Value", "Alias" switch, enters "Value" text box).
- Ctrl+v/Paste in the name server values from the subdomain
- Hit tab key one more time
- Go back and select the "Record type" dropdown with the mouse
- See that "NS" is still greyed out/disabled.
Maybe a bug in the Javascript?
Ensure that Alias is not enabled as that would grey out the NS option.
If the UI does not work and you have followed the steps, you can try the CLI/API with the R53 change-resource-record-sets command / API.
Here are the instructions.
Generally API call will give you a more detailed reasons when it failed.
Not sure why the answer has been down voted.
It's unclear why people are trying to guess what's the issue instead of just try the API and get a more direct reason why the NS record cannot be created in the hosted zone.
It's a very important technique because sometimes the UI does not give you any reason why certain operation is grayed out.
I came across the same issue where the NS record type was greyed out in both Private AND Public hosted zones. But I was able to successfully create the record using AWS CLI.
相关内容
- AWS 官方已更新 2 年前
- AWS 官方已更新 6 个月前
- AWS 官方已更新 2 年前
- AWS 官方已更新 1 年前
I saw the same thing for my public hosted zone. I found that when I selected on of the other options first NS record became selectable and I was able to successfully add the record using it. It seems like a UI bug to me.