My domain is in godaddy. I have set CNAME called www as abcxy.com.s3-website-us-east-2.amazonaws.com. Now i want the same value to replecated for Type A name #. But unfortunately it does not accept bucket name , it only accepts ip addres. How to enable it to accept the bucket name?
Related
I'm new to CloudFront and was wondering how to force it to redirect. In Apache it's just through Virtual Host, but with CloudFront, I'm confused how to do it.
Here is my scenario
NameCheap
CNAME | www | random12345.cloudfront.net (where my site files are)
AWS
ACM - requirement for CloudFront for custom SSL (N.Virginia)
Domain Name: sample.com
Additional Domain Name(s): *.sample.com
CloudFront Distribution
Domain Name: random12345.cloudfront.net
CName: sample.com
*.sample.com
Result
WORKED: https://www.sample.com | www.sample.com
NOT WORKING: sample.com | https://sample.com | http://sample.com
Typing these in the search bar results to Error: This site can’t be reached sample.com’s server IP address could not be found. DNS_PROBE_FINISHED_NXDOMAIN
I attempted to create an S3 bucket to force redirect to https://www.sample.com
but can't create since CNAME www.sample.com is already used for the CloudFront Distribution. Can't use # in CNAME since it is not recommended on root configuration due to its effect on MX records
Thanks a lot.
You have to following step for redirecting non-www domain to www :
Note: www.example.com bucket should have code and example.com will be empty bucket only configuration mention below.
Create example.com S3 bucket.
Go to S3 bucket properties -> Static website hosting then select Redirect request add value as www.example.com
Set Bucket policy and CORS same www.example.com bucket
Create CloudFront for example.com use origin as example.com.s3-website-us-east-1.amazonaws.com not which selection dropdown giving.
Select user *.example.com ACM for https
Then create Route53 Entry for this example.com as A record select respective CloudFront origin for example.com.
This domain is transferred to AWS if you don't want full NS record then only move A record to AWS.
Then you are done.
SSL Error when assessing by IP address
I have an IP address as 192.0.2.13. On nslookup, it shows the answer as example.com
Now on assessing the IP address https://192.0.2.13 itself it gives, SSL error as Common name invalid and but if I tries to access https://example.com, it loads fine. Also, I can see SAN configuration as
DNS name : example.com
DNS name : examplem.com
Now, I want to know should I need to add IP address to SAN config as well?
I have following domain name air8kissen.de. When I type in that domain name in browser it gets redirected to its IP address 178.128.117.168. The problem is that I setup SSL for domain name and since IP dont have SSL it shows the warning sign. When I accept to risk visiting the website, it redirects me to my domain name.
I have setup all necessary CNAME and A records inside Digitalocean domain setup and have no idea why it shows the IP address first time I visit to domain.
What should I do to fix this?
Cheers
This is not a DNS or SSL issue, You need to setup the Virtual Host for your domain at your webserver, and check any redirection rules placed at your webserver level.
The server is behind a firewall and has a private IP and I need to get to the public IP of the domain that it is hosting...
I have several sites with several Host Name bindings and they all work fine over SSL (i.e. https://example.com), but I need to get to it just using the IP address (i.e. https://123.45.67.89) and I can't figure out how to do the bindings because it doesn't allow an IP address as the host name. Browsing to just the IP gives me a 'Connection Not Private' message.
a security certificate must be granted to a host name e.g. example.com
You cannot issue a certificate to an ip address.
When you browse via ip and the certificate is served up, it does not match the address you have entered and is correctly telling you that the certificate is not valid for the site you are wishing to view
The certificate provided by the server is probably not issued for the IP address and that's why it does not match the URL (with IP as target) you entered. You have to access the server with a name which matches the certificate which means that you need some DNS settings which map the name contained in the certificate to the external visible IP address and then you can access the server by its correct name. For testing you can do such mapping inside your local hosts file. But if the server should be visible from outside for others too you need to configure the public DNS for the domains served by the firewalled server so that the mapping to the public IP address is publicly visible.
So I have
mydomain.com
and I want
test.mydomain.com
Can I set this up without creating an A record for the subdomain? Either with .htaccess or
You need something in DNS. It can be an A, a CNAME, or you can use a wildcard entry like
*.mydomain.com. IN CNAME mydomain.com.
The above is a wildcard record, which will match any name under mydomain.com. You can also use a record for your specific name.
; an alias name pointing to mydomain.com
test.mydomain.com. IN CNAME mydomain.com.
; or, a regular DNS record
test.mydomain.com. IN A 1.2.3.4
Without a DNS entry, the browser will not know about your Apache instance to begin with. So you cannot solve this with .htaccess or Apache config alone, DNS must route the request to Apache first.