Domain not resolving

0

I set up static site hosting on S3 and pointed my A records to that bucket but after at least 5 hours the record hasn't propagated. When i dig my domain this is what I get:

; <<>> DiG 9.16.1-Ubuntu <<>> frequencyh.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 56875
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 65494
;; QUESTION SECTION:
;frequencyh.net.			IN	A

;; Query time: 67 msec
;; SERVER: 127.0.0.53#53(127.0.0.53)
;; WHEN: Mon Jun 29 19:00:02 EDT 2020
;; MSG SIZE  rcvd: 43

I previously attempted to put a CDN infront of the domain but removed it because of an access denied error even after setting up OAI. The test record seems to be fine, but I'm not sure how that could be.

질문됨 4년 전211회 조회
1개 답변
0
수락된 답변

Hi,

Name servers appear in three places, and typically they should all be in synch:
~ The name servers that Route 53 assigns to a hosted zone when you create it. These are the "master" name servers and cannot be changed. Name servers in the other locations usually match these.
~ The name servers in the NS record in the hosted zone.
~ The name servers that are associated with the domain registration. These are the name servers that control which DNS configuration is in use.

For frequencyh.net, the "master" name servers match the name servers in the NS record, but the name servers in the domain registration are different.

To fix that, do the following:

  1. Get the name servers that Route 53 assigned to the hosted zone when you created it. See "Getting the Name Servers for a Public Hosted Zone" in the Route 53 Developer Guide:

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/GetInfoAboutHostedZone.html

  1. Update the domain registration to use the four name servers that you got in step 1. See "Adding or Changing Name Servers and Glue Records for a Domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-name-servers-glue-records.html

After you finish, it will take a couple of days for you to be able to see your website again because DNS resolvers typically cache the names of name servers for two days. (Folks who use different DNS resolvers will be able to see your website as soon as you make the change. You might also be able to see your website from your phone.) For an overview of how DNS works, including the part about resolver caching, see "How Amazon Route 53 routes traffic for your domain":

https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/welcome-dns-service.html#welcome-dns-service-how-route-53-routes-traffic

Scott

전문가
답변함 4년 전

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

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

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

관련 콘텐츠