My client recently purchased a new domain name and wants it to link to an interior page on the current website. Both domains are registered on the same account. The main site is currently hosted on a Media Temple Grid account and I see no option for "forwarding." There is an option to "Point the domain to another server." Not sure if this is more of a DNS record change or an .htaccess redirect?
The main website is: fairmountstrings.com
The new domain name that needs routing is: fairmountstringquartet.org
The interior page that I'm trying to route to is: fairmountstrings.com/concerts/fairmount-string-quartet/
I selected "Point the domain to another server" which made the DNS for fairmountstringquartet.org the same as the main website. I then tried multiple different redirects in the .htaccess file that's on the root of the server but nothing seems to be working.
Related
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 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.
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 SharePoint site which serves as our company site on the internet. Our company has 2 domains ".com" and ".co.uk". SharePoint works fine when you access the site using the ".com" domain. The problem is, when you try to access the site using the ".co.uk" domain, some pages (ones including custom lists, settings pages) do not work properly.
After doing some research, I found out that I needed to add the ".co.uk" domain under Sharepoint access mappings to make it work properly, but when I do that, I am redirected to the ".com" domain. By the way, the".com" domain already exists in the accesss mappings page.
So, what's the best way to configure our Sharepoint site to work for 2 different domains?
In addition to the alternate address mapping create a IIS website for it. This link might not 100% apply to what your using, but you should be able to make ends meet with it.
http://www.isaserver.org/img/upl/spskit/3quickstart/3quickstart.htm#_Toc58577520
I solved the problem today. Here's how:
First I learned how to extend a Sharepoint site using the video: http://technet.microsoft.com/en-us/sharepoint/Video/ff679931.
In SharePoint Central Administration, I extended the default site (SharePoint - 80) for the ".com" domain.
Used "Create a new IIS web site Name" option, used domain name as the name,
Used port 80, domain name as the host header and the default sharepoint path,
Didn't change Authentication and SSL options, allowed anonymous access
Used the ".com" domain in URL and used Internet as the zone.
After extending a new IIS site was created. In Internet Manager, I clicked "Edit Bindings" option for the new site. The ".com" domain was already set in bindings. I added the ".co.uk" domain into bindings as well.
In Central Administration > Alternate Access Mappings, I set the ".com" domain URL as the Default zone and the ".co.uk" domain as the Internet zone. This automatically added internal URLs for both domains.
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.