Skip to content

Route 53 with gandi .co.uk domain

0

I have a .co.uk domain natively purchased via route 53 and the nominet ns is showing the registrar as being gandi, which is because aws uses a third party for UK registrations.

All works fine with that domain. Last week I transferred in another .co.uk domain and the nominet registration also know shows this as gandi, however the ns are incorrect.

The ns on the AWS hosted zone and aws DNS both match, but there are different to those on gandi.

Aws are responsible for updating the registrar details but how long show this take as it's now been 36 hours.

Thanks

asked a year ago254 views

1 Answer
0

When you transfer a .co.uk domain to Route 53, there can sometimes be a mismatch between the nameservers listed in your Route 53 hosted zone and the nameservers registered at the domain level (the "glue records").

Since AWS uses Gandi as its registrar partner for .uk domains (including .co.uk), it's normal to see Gandi listed as the registrar in Nominet records. However, the nameservers should match those provided by your Route 53 hosted zone.

Regarding the timeframe for nameserver updates, while DNS propagation typically takes 24-48 hours, the specific issue you're experiencing might require manual intervention. The nameservers in your domain registration settings need to exactly match those provided by Route 53 for your hosted zone.

To resolve this issue:

  1. Verify that the nameservers in your Route 53 hosted zone match those listed under your domain registration details in Route 53 (not just in the hosted zone).

  2. If there's a mismatch, you can update the domain's nameservers through the Route 53 console by going to "Registered Domains," selecting your domain, choosing "Action" > "Edit name servers," and updating them to match your hosted zone.

If you've already confirmed the nameservers are correctly set in the Route 53 domain registration settings but they're still not updating at Nominet/Gandi after 36+ hours, you may need to contact AWS Support through the Account and Billing section. Domain registration issues can be addressed through this support channel without requiring a paid support plan.
Sources
Getting InvalidInput setting domain IPS TAG to NAMECHEAP-INC | AWS re:Post
Route 53 owned domain is not being resolved | AWS re:Post
NS records not matching domain lookup | AWS re:Post
Troubleshoot DNS resolution issues for records in Route 53 public hosted zones | AWS re:Post

answered a year ago

You are not logged in. Log in to post an answer.

A good answer clearly answers the question and provides constructive feedback and encourages professional growth in the question asker.