If I do example.com my site is there, but when adding www. or http://www. I get the error message: server DNS address could not be found.
I'm pointing my domain to EC2 on Amazon Web Services.
What am I missing?
You have to add a CNAME record for the www subdomain pointing at your EC2 Ip and also I recommend you to make a permanent redirect on your virtual host config file of your web server (apache for example) to redirect http://myexample.com to http://www.myexample.com. If you do not prefer making a permanent redirect you need to include www.myexample.com in your virtual host file as an alias.
Do you have CNAME DNS records set for www on GoDaddy? Try set www to # under DNS Settings CNAME. Read support article here
Related
I have setup a raspberry pi web server. I'm using nginx and google domains. I have a conf file for that domain in sites-available I configured the server_name to my domain name www.domain.com .domain.com;
The problem is that I can only access the website using .domain.com. When I try using www.domain.com I get redirect to ISP page (unable to find..).
Login to your domain provider's dashboard
If you haven't already added an A record to your DNS settings select Manage DNS and add an A record pointing to your IP address of the host.
You'll essentially need to add a CNAME record to your domain's DNS settings. The 'Name' field should be www
Depending on your provider you may have to wait till about 2- 48hrs to allow it to propagate.
So I have a follow up question based on How To Setup Subdomains on iis
I am using IIS 8, and I am looking to point my subdomain to my current default website. Currently we have www.mydomain.com, and I setup a subdomain in our DNS A Record that is account.mydomain.com pointing to the same IP address of mydomain.com.
I figured the way to create the subdomain is now to go to Site Bindings under the Default Website in IIS and add a site binding with the hostname account.mydomain.com but I am getting an error that says the server IP address cannot be found. The reason I didn't want to create a new Site in IIS is because we have certain properties and permissions that are setup.
Eventually we will be changing the IP Address of www.mydomain.com to be pointing to something new, but for the time being we need account.mydomain.com to point to the same location as www.mydomain.com
Images for reference -
My application is running on Nginx webserver. I can access the application through my server DNS name. Example :
ec2-xxxxxx/myapp
If I enter the address without /myapp, I can see Nginx 403 Forbidden error.
I have now created a new sub-domain on my Domain control panel and Forwarding the request to the root address.
I can see the 403 error when accessing the sub-domain, however when I enter subdomain.mydomain.com/myapp, I still see the 403 Forbidden error. Somehow the relative path is not being preserved when calling from the domain name.
Is this problem related to resolving DNS at my domain registry, or it's an Nginx config issue?
Its a nginx config issue. You need to create the virtual host for your subdomain. Post that you should be able to access your app from your subdomain.
The problem was with the Domain registry (GoDaddy) and had nothing to do with Nginx config.
After moving from GoDaddy to AWS Route53, I can easily access sub-domain with it's relative paths.
I have domain setup like http://www.example.com/in which is a wordpress multisite setup and hosted on a AWS EC2 instance.
I have to make another similar setup with url http://www.example.com/uk but on another EC2 instance.
The domain www.example.com is routed to only one IP of first instance.
Can anyone advise on how I should setup this routing to make this scenario on Amazon Route 53?
Assuming you are serving your site using apache you can add a .htaccess rule on the instance hosting www.example.com to redirect www.example.com/uk traffic to another ip address.
This will mean you rely on www.example.com to redirect traffic for www.example.com/uk. In the event the instance running www.example.com were to become unavailable, www.example.com/uk would become inaccessible.
Alternatively, you can setup a subdomain in Route53 with the following entry
uk.example.com 1.2.3.4
This will mean that www.example.com/uk will need to be accessed using uk.example.com not www.example.com/uk
I have setup WordPress for my domain xyz.test.
In my domain configuration I have set the A entry for the www subdomain to the same A entry as for the primary domain (xyz.test).
However, when entering www.xyz.test in the browser, it does not go to my WordPress server, but only returns Apache`s "No content message".
How do I solve this issue?
Apache allows name based virtual hosts. This means you can host multiple FQDNs on the same IP address. You need to add a name based virtual host for www.xyz.test that points to the same directory. Or you could add a server alias in the xyz.test virtualhost configuration:
ServerName xyz.test
ServerAlias www.xyz.test