AWS re:Post을(를) 사용하면 다음에 동의하게 됩니다. AWS re:Post 이용 약관
AWS re:Postre:Post

[URGENT] My domain is still inaccessible after 2 days. I'm pretty sure I configured Route 53 correctly. I need help.

0

Ok so I got the confirmation of our domain name transfer from OVH on Sunday. While waiting for the transfer (which took 10 days), I copied all the DNS records to Route 53. The MX records were already configured for our GSuite, so I was expecting the our email box would never stop working. I removed the automated OVH stuff and replaced it with Alias records to our Beanstalk loadbalancers and Vercel deployments. The Test Record feature shows that the records are working correctly, even with different resolver IPs. BUT after 2 days, our website is still inaccessible, and our mailbox isn't receiving any emails. nslookup returns SERVFAIL errors, no matter with public resolver I try (8.8.8.8, 1.1.1.1, etc). I'm out of ideas, I don't know what to do, and every hour that passes without being able to receive emails is business that we're losing.

주제
네트워킹 및 콘텐츠 전송
태그
아마존 루트 53
언어
English
Mickael
질문됨 10달 전370회 조회
2개 답변
1
수락된 답변

It’s most likely your Glue records are incorrect.

When you transferred your domain, you may or may not have updated your Glue Name server records.

Look in your route53 zone file for your NS records. There will be 4 name servers.

Then head over to this link and update your name servers on your domain https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html

profile picture
전문가
Gary Mclean
답변함 10달 전
  • Mickael
    10달 전

    You mean these? I didn't touch them. https://i.imgur.com/48wRbLx.png

  • Gary Mclean 전문가
    10달 전

    What are your name servers set too in your domain? Not the zone but the name servers for your domain?

  • Gary Mclean 전문가
    10달 전

    Use my link above to make sure the name servers set match your screen shot.

  • Gary Mclean 전문가
    10달 전

    You update name server records in route53 per link not at ovh as you transferred the domain.

  • Mickael
    10달 전

    Oh ok I found it. Because the NS records were set automatically to AWS DNS I thought you would also make the change to the domain's DNS as well. But no. Plus I didn't know where to find the DNS names for my domain so I had to look around a bit, and then when I found them I realized they were still set to OVH's. It's fixed now. Thank you

1

Hi,

You should go through this guidance: https://repost.aws/knowledge-center/route53-dns-servfail-response to validate that your problem doesn't come from one of the listed causes for DNS SERVFAIL errors

Stating that you're pretty sure of the Route53 settings and that it is a transfer from OVH, you may want to start with the first possible cause in the list "A third-party name server (NS) is blocking the AWS public resolver's IP address"

In particular, you should check via nslookup directly (nslookup [domain-name] [name-server]) on OVH servers if they still directly publish infos about your domain

Best,

Didier

profile pictureAWS
전문가
Didier_Durand
답변함 10달 전
  • Mickael
    10달 전

    You mean I need to go back to OVH to update the DNS names to Route 53's ? But why would I need to do that? The domain is transferred, right? Why would OVH still publish infos about my domain? I'll try of course but I'm a bit confused here.

로그인하지 않았습니다. 로그인해야 답변을 게시할 수 있습니다.

좋은 답변은 질문에 명확하게 답하고 건설적인 피드백을 제공하며 질문자의 전문적인 성장을 장려합니다.

질문 답변하기에 대한 가이드라인

관련 콘텐츠