I have an Azure Websites URL at http://mysite.azurewebsites.net. Attempting to browse to http://www.[mysite].azurewebsites.net/ results in a DNS lookup failure, with the error code in Chrome of "ERR_NAME_NOT_RESOLVED"
I've attempted to add www.[mysite].azurewebsites.net in "Manage custom domains", but receive the message "The host name www.[mysite].azurewebsites.net is invalid."
Note that I don't have a custom domain and I'm happy to use the .azurewebsites.net URL, I simply would like the users who add "www." to the URL they've been given to resolve to the correct URL.
Is this possible with Azure Websites without requiring a custom domain?
The menu from your screenshot can be used to configure any domain, you own, to point to your azurewebsite, this is not what you want.
Your "website" is a subdomain (level 3) of domain azurewebsites.net, where "azurewebsites" is a level 2 domain and "net" is the TLD. "www" is a subdoamin and normally used as (level 3) subdomain in ealier days to point out, that you are using the World Wide Web. This is not necessary and it does not make sense to create a level 4 subdomain "www". I don't even think, level 4 subdomains are supported by azure anyway.
Related
I created a site with Hugo and I hosted it as a gitlab page.
To assign my custom domain I followed the instructions of this document of gitlab.
I created three DNS records:
one of type A with name # and value 35.185.44.232;
one of type TXT with name # and value _gitlab-pages-verification ... for the verification of the ownership of the domain;
one of type A with name www and value 35.185.44.232.
If I access the site using the address https://example.com everything works normally; but if I log in using the triple W (www.example.com) I get from gitlab the error message 401 You don't have permission to access the resource. The resource that you are attempting to access is protected and you don't have the necessary permissions to view it.
How can I correct it?
Try a CNAME instead of a second A record for your WWW. subdomain. Having two A records - one that points to your naked domain and one that points to your WWW-domain is either causing redirect error or simply does not exist since it, as your origin's subdomain, must exist as a separate entity on GitLab OR you can not concern yourself with it by using a CNAME record as I previously recommended and using a directory-style (as opposed to a subdomain-style) setup for your site. Each has its own benefits as well as drawbacks. I use the CNAME method and have a WWW-subdomain setup on GitLab in order for my sites to grant that extra bit of security and privacy to visitors that having a TLS cert installed on the WWW-subdomain offers.
I'm trying to redirect multiple domain names to their corresponding landing pages on my website using name servers, but don't know where to start.
Example:
I have two domain names 1)ABC.com 2)123.com. I want to set the name servers of each domain to forward them to the landing page on my website, so ABC.com would redirect to MyWebsite.com/abc and 123.com would redirect to MyWebsite.com/123.
Any help as to where I could a general direction to make this happen?
DNS is solely responsible for the name 123.com to address 12.34.56.78 mapping. It has no concept of anything that happens beyond that. Via DNS you would need to point both names to the address of the web server.
Then on the web server, configure a site at abc.com and 123.com, with each site being redirected the appropriate place.
This way, the HTTP software will detect which domain name is requested and redirect it as required.
You basically need to follow the link shared in comments, but do that for each domain. - How do I redirect a domain to a specific "landing page"?
I just purchased a domain for my blogger blog through google(goDaddy)
Currently, it is pointed to blogger web host.
I'd like to point it to my own web host as well, so i can host files, while not losing my blog stuffs from blogger.
Is this possible? for a domain to have 2 web host?
I'm sorry, i'm really new to these domain and hosting, any help would be appreciated. Thanks!
You can keep your domain on your site and then setup a subdomain-- like blog.YOURDOMAIN.COM-- and point that to your blogger account.
Go to http://www.google.com/a/domainname, replacing domainname with your domain name.
Now you will need to login to your Google account utilizing a username and password you previously created specifically for Google Apps for your domain. If you do not know this information, click 'Can't access your account.'
Once logged in, click the 'Domain Settings' tab.
Click on "Advanced DNS Settings".
You will now see listed your Sign-In Name, Password, and PIN.
Click Sign-In to DNS Console and use the Sign-In Name and Password to login.
You should now be in the Domain Control Center. Click Forward, and then select Forward Subdomain.
In the Add subdomain field, enter the subdomain.
Select http:// or https:// depending on your server settings.
In Forward this subdomain to, enter the URL you want to forward the subdomain to. This will be the URL for your Blogger blog.
To view additional options, click Advanced Options, and then select one of the following:
Forward Only — Specifies the length of time for this forwarding setting. Select one of the following redirect types:
I am permanently forwarding my domain — Redirects to the site you specified in the Forward To field using a "301 Moved Permanently" HTTP response. The HTTP 301 response code tells user-agents (including search engines) the location has permanently moved.
I am only temporarily forwarding my domain — Redirects to the site you specified in the Forward To field using a "302 Found" HTTP response. The HTTP 302 response code tells user-agents (including search engines) that the location has temporarily moved.
Forward with Masking
Title — Displays at the top of the browser window and in search results.
Description — A short description of your website to display in search engine results.
Keyword — A list of comma-separated keywords that describe the content and purpose of your website.
Click OK.
The main domain you just continue to point to the IP of your web host.
we have a saas web app, written in zend mvc (php) where users can enter their own domain name in their settings page.
When they enter e.g. www.customdomain.com we want this domain to redirect to our web application so we can serve up their own pages from our app.
We do the same already for subdomains by having a *.ourapp.com entry in our DNS configuration.
that works great for subdomains like customdomain.ourapp.com.
This doesn't seem to work for full domain names like www.customdomain.com.
What's the easiest way to have any domain address link to our application, so we can just read out the incoming domain name and act accordingly in our app?
For letting the DNS entry point at your servers:
Domain is already registered (and owned by the customer): Make him configure the CNAME entry to your server's IP. (Even google let this do the enduser by hand - so automating this might be hard)
Domain is free: Register it, configure the CNAME yourself (you own it)
If you only want a redirect, the user can upload a html file or .htaccess file, that performs the redirect. But this has to be done by the customer, too.
A domain name that we have is using google mail as its backend, but its not hosted anywhere (no website). How can I, through the registrar interface (I'm using 1&1), redirect ppl who type in http://mail.example.com to http://mail.google.com/a/example.com ?
I can create a subdomain and set its DNS/CNAME, but what do I put where? Also, if I make this change will it affect the existing mail delivery (for which everything is running fine presently).
It turns out it wasn't that tough... and the instructions are part of Google itself:
Dashboard -> Service settings: Email -> General:Web address -> Change URL
https://www.google.com/a/cpanel/example.com/CustomUrl?s=mail
Changing CNAME record
To use the custom URL mail.example.com, you must change the CNAME record with your domain host.
Sign in to oneandone.
Navigate to your DNS Management page. The location and name
of this page will vary by host, but
can generally be found in Domain
Management or Advanced Settings.
Find the CNAME settings and enter the following as the CNAME value
or alias:
mail
Set the CNAME destination to the following address:
ghs.googlehosted.com
Save changes with your domain host and click "I've completed
these steps" below.
You cannot redirect to a path (such as /a/example.com) using only DNS. DNS CNAME records can make mail.example.com/foo effectively point to mail.google.com/foo, but something more sophisticated will require HTTP redirects. This means you need someone hosting your web page for this to work.
Sorry.
If your registrar offers an "HTTP Redirect" option, you can use that. Some registrars do. If you use this, they're effectively running a minimal web server for you. Note that this may break SSL when users access your page via https://example.com.
Mail delivery is via MX records, which won't be affected by changes to other types of record (so long as you don't interfere with the DNS records for the domain's mail servers).