New answers tagged

1

From our discussion in the comments, it looks like you attempted to set an IP address target using a CNAME record. This record type is only intended to alias the host resources of one name to another, and the value will be interpreted as a name even if you input an IP address. Input: $ORIGIN example.com. www IN CNAME 203.0.113.0 Effective output ...


1

Did you change it as a delete/create or as a update? Delete/create could cause an outage. A straight update is safe and does not result in a not-found message.


0

If you have added the CNAME records for your domain with the record name www or with a blank record name, your website may not be accessible until the DNS records are propagated.


0

The correct way to handle this isn't with DNS records. You're supposed to use Route 53 and set your domain to the custom nameservers that AWS provides. Here's the tutorial that I followed: https://docs.aws.amazon.com/elasticbeanstalk/latest/dg/customdomains.html I also ended up writing a blog post about this: ...


0

Short Answer - Just restart the Server Long Answer - Actually yes, the mistake was I didn't restarted my server after all kind of configurations. But, few things that one has to consider in setting up with CloudWays are, Check the A Record in Domain Registrar's Console. Make sure that it matches with the one that is displayed on Instance summary in ...


1

Looks like you need to set up an A NAME record as well: https://support.cloudways.com/how-to-point-my-root-domain-to-my-new-cloudways-server/ And make sure domain mapping is set up correctly: https://support.cloudways.com/how-do-i-take-my-website-live-from-cloudways/ And don't forget it takes some time for the new settings to propagate world-wide: ...


0

Figured it out - in have two buckets in S3 - mydomain.com and www.mydomain.com. mydomain.com is where the site is, and I set www.mydomain.com to redirect to mydomain.com.s3-website-ap-southeast1.amazonaws.com... I moved the files to www.mydomain.com and removed the redirect.


1

This isn't a DNS problem, as apex aliasing with CNAME is not legal per the DNS standards. The "URL Redirect Record" functionality is custom behavior implemented by Namecheap's software. In the background, it results in an A record being defined for a webserver that will perform the redirection for you. The webserver in question is not listening on port ...


-3

Instead using a CNAME you can set an A record pointing directly to the HOST_IP_ADDRESS: Type: A Record Host: www.mydomain.com Value: 54.231.242.137



Top 50 recent answers are included