DNS_PROBE_FINISHED_NXDOMAIN for praveeny.com

0

Hi , I set up praveeny.com in AWS 53 using this document https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/getting-started-cloudfront-overview.html#getting-started-cloudfront-create-alias

I am getting DNS_PROBE_FINISHED_NXDOMAIN . I found an related answer which asked to match the NS servers which I did. Any help will be great, where to dig.

PRAVEEN
asked 14 days ago98 views
1 Answer
0

Hello.

Have you purchased the domain "praveeny.com"?
If you have not purchased a domain, you will not be able to use it even if you create a public alias record in Route53.
If you want to purchase a domain with Route53, you need to follow the steps in the document below.
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/domain-register.html

I was able to confirm the following results using the "whois" command.
Do the NS records listed in "Name Server" in the results below match the NS records registered in the Route53 hosted zone?
If they do not match, please modify the NS records registered in the Route53 hosted zone so that they match.

 whois praveeny.com
   Domain Name: PRAVEENY.COM
   Registry Domain ID: 2882341092_DOMAIN_COM-VRSN
   Registrar WHOIS Server: whois.registrar.amazon.com
   Registrar URL: http://registrar.amazon.com
   Updated Date: 2024-05-19T22:26:06Z
   Creation Date: 2024-05-17T20:36:26Z
   Registry Expiry Date: 2025-05-17T20:36:26Z
   Registrar: Amazon Registrar, Inc.
   Registrar IANA ID: 468
   Registrar Abuse Contact Email: abuse@amazonaws.com
   Registrar Abuse Contact Phone: +1.2024422253
   Domain Status: ok https://icann.org/epp#ok
   Name Server: NS-1189.AWSDNS-20.ORG
   Name Server: NS-1889.AWSDNS-44.CO.UK
   Name Server: NS-26.AWSDNS-03.COM
   Name Server: NS-719.AWSDNS-25.NET
   DNSSEC: unsigned
   URL of the ICANN Whois Inaccuracy Complaint Form: https://www.icann.org/wicf/
>>> Last update of whois database: 2024-05-19T23:37:41Z <<<

I don't think it's very relevant, but the procedure in the document you used uses a slightly older procedure called OAI, so I recommend using the access control using OAC in the document below.
https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/private-content-restricting-access-to-s3.html

profile picture
EXPERT
answered 14 days ago
profile picture
EXPERT
reviewed 9 days ago
  • Hi @riku. I have bought the domain through route 53. I deleted my hosted zone and recreated a new one. I also removed all the cdn step and now just hosting a simple s3 bucket with static website enabled. Still getting the same issue.

  • Now that you can check the NS record with the "dig" command, you can probably use it by registering CloudFront with an alias record. Also, even if you create a record, it may take some time for the domain to propagate, so please wait for a while before attempting to access it.

    dig praveeny.com ns
    
    ; <<>> DiG 9.16.1-Ubuntu <<>> praveeny.com ns
    ;; global options: +cmd
    ;; Got answer:
    ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 12493
    ;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 1
    
    ;; OPT PSEUDOSECTION:
    ; EDNS: version: 0, flags:; udp: 1232
    ;; QUESTION SECTION:
    ;praveeny.com.                  IN      NS
    
    ;; ANSWER SECTION:
    praveeny.com.           86400   IN      NS      ns-1390.awsdns-45.org.
    praveeny.com.           86400   IN      NS      ns-146.awsdns-18.com.
    praveeny.com.           86400   IN      NS      ns-1652.awsdns-14.co.uk.
    praveeny.com.           86400   IN      NS      ns-671.awsdns-19.net.
    
    ;; Query time: 145 msec
    ;; SERVER: 192.168.11.1#53(192.168.11.1)
    ;; WHEN: Mon May 20 09:48:07 JST 2024
    ;; MSG SIZE  rcvd: 178
    

    For static website hosting on S3, you need to create an S3 bucket with the same name as your domain name. https://docs.aws.amazon.com/AmazonS3/latest/userguide/website-hosting-custom-domain-walkthrough.html

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.

Guidelines for Answering Questions