Domain showing without WWW [duplicate] - dns

This question already has answers here:
Closed 11 years ago.
Possible Duplicate:
redirecting www.subdomain.example.com to subdomain.example.com
I have a hard time understanding DNS mapping and such.
Right now, whether I type in my URL with or without WWW, it loads the site, but the URL displays without the WWW. But I would like the WWW to be displayed.
Domain registrar is Hover and Host is Laughing Squid
What am I missing?
Thanks,

You didn't provide any details around the server configuration, etc., but you apparently have DNS entries registered for both - pointing to the same site, but have a rewrite rule in effect that is redirecting the "www" version to the non-"www" version.

Related

moved domains and 301 redirects are not working...?

We have recently moved our website from the old domain to a new domain. The old domain is now empty except for the .htaccess file which is as follows (eg):
redirect 301 /examplepage.html https://www.newdomain.com/examplepage.html
However, when we test the old link it isn't redirecting.
We've tried tech support from the domain people, but they have given us a couple of bogus sounding excuses (like the old domain has no files other than the .htaccess). The latest reason they suggested was that the old domain no longer has a certificate installed so the https pages aren't redirecting.
To be fair, we do get a different result if searching for a page using http/https:
for HTTP we get "Not Found
The requested URL was not found on this server."
for HTTPS we get "This site can’t be reached www.domainname.co.uk unexpectedly closed the connection.
ERR_CONNECTION_CLOSED"
Any ideas where we're going wrong or how to fix this...?

Host homepage on a different server than the rest of site [duplicate]

This question already has answers here:
possible to resolve DNS based on URL path
(3 answers)
Closed 5 years ago.
Is it possible to host one page of a website (example.com/index.html) on a different server than the remainder of the site (example.com/blog/ and etc.)? Are there ways to manage this through DNS settings? An .htaccess file?
Thanks!
Short answer is, not really. A DNS entry maps a hostname (example.com) to an IP address. The path part of the url (/index.html) is not part of the hostname, and is only contained inside the http headers.
The general practice for this kind of situation is to use a proxy or load balancer which will send requests to different servers depending on the request path.
If it really needs to go to two different places without a central load balancer, then you probably need a unique subdomain for each site.

Need Domain Name assistance - Please

I have a small issue. I have tried for the last hour to find a solution for this on this and many other websites. I have found similar but none have provided an answer that works. Heres that problem:
I have a badge on my website that was given to me by Norton online protection. they provided me with a script file and I placed it where it should go. NOW, this script is registered to "www.example.com" but if someone goes to their browsertypes in just "example.com" without the WWW. the Norton badge never shows.
I spoke with Godaddy this morning and they have no solution so that's why I'm asking on here.
Is there a to send a domiain name to the same domain name? so that it always shows the WWW?
Configure your webserver such that www.example.com is one site (your actual site with your content), and you have another site that is example.com (no www subdomain) as a site that you can now configure to redirect to your actual site. How that step is done depends on which webserver you are using, but basically these is a way to do that on any webserver (Apache, IIS, etc).
You could try to read the URL and check if 'www' is present in the URL. If it is not present redirect the visitors to www.example.com
In php you could use the below for redirection
header('Location: http://www.example.com/');

Behaviour of domains and subdomains for accessing a URL

Why does analytics.google.com works while www.analytics.google.com does not ??
David's comment above is accurate. I wanted to expand upon this a little to clarify your thinking of www.
www. is a subdomain like any other. Whether you use analytics. or www. or whateveryouput., they're all still just subdomains that are created for the domain in question.
David answers correctly that the reason www.analytics. doesn't work is because the subdomain analytics. doesn't have a subdomain www..
I think it's important to know that there's nothing particularly special about the www. subdomain compared with any other subdomain.

Using DNS to redirect to another URL with a path [closed]

Closed. This question does not meet Stack Overflow guidelines. It is not currently accepting answers.
This question does not appear to be about a specific programming problem, a software algorithm, or software tools primarily used by programmers. If you believe the question would be on-topic on another Stack Exchange site, you can leave a comment to explain where the question may be able to be answered.
Closed 3 years ago.
Improve this question
I'm trying to redirect a domain to another via DNS.
I know that using IN CNAME it's posible.
www.proof.com IN CNAME www.proof-two.com.
What i need is a redirection with a path. When someone types www.proof.com, it should take them to to www.proof-two.com/path/index.htm
I know it can be done using Web Server facilities, but I need DNS redirection.
Is this possible?
No, what you ask is not possible. DNS is name resolution system and knows nothing about HTTP.
if you use AWS, a redirect like
mail.foo.com --> mail.google.com/a/foo.com
can be setup as follows:
in s3, create an empty bucket "mail.foo.com"
under Properties -> Static Website Hosting, set "redirect all requests to: mail.google.com/a/foo.com"
in route53, create an A record "mail.foo.com"
enable "alias", and set alias target to the "mail.foo.com" bucket
not a pure DNS solution, but it works ;)
But be aware of, the redirect skips all the URL parameters e.g.: ...?param1=value1&param2=value2
I realize this is an old thread but FWIW, incase someone else is looking for a way to do this.
While dns does not understand the path portion of the url, it will understand subdomains, so instead of:
www.proof.com IN CNAME www.proof-two.com/path/index.htm
You could use:
www.proof.com IN CNAME proof.proof-two.com
then go to wherever you host proof-two.com and set it to point proof.proof-two.com to www.proof-two.com/path/index.htm.
~ there's always more than one way to skin a cat
Some providers allow this but there are no "pure" DNS solutions since DNS doesn't know anything about the protocol you're using and redirects are a feature from HTTP.
For OVH, see : https://docs.ovh.com/gb/en/domains/redirect-domain-name/
You will have to use the control panel to add your redirection. It will update your DNS zone accordingly.
Let's consider you created a redirection from foo.bar.com to foo2.bar.com/path. OVH keeps the url paths and parameters. So if you try to access foo.bar.com/hello?foo=bar, you'll be redirected to foo2.bar.com/path/hello?foo=bar.
I have a personal project that might help you in solving this issue.
It's an open source redirect solution that allows you to redirect your domain just changing your DNS settings. Link of the project: https://redirect.center/.
To redirect www.proof.com to www.proof-two.com keeping the URL parameters, just set your www DNS entry on proof.com:
www.proof.com IN CNAME www.proof-two.com.opts-uri.redirect.center.
Really it's easy with redirect.center
If you want create a CNAME as :
www.proof.com IN CNAME www.proof-two.com/path/index.htm
using redirect.center your CNAME look as canonical mode as:
www.proof.com IN CNAME www.proof-two.com.opts-slash.path.opts-slash.index.htm.redirect.center.
Now if you want redirect to https website you can add this option:
www.proof.com IN CNAME www.proof-two.com.opts-slash.path.opts-slash.index.htm.opts-https.redirect.center.
Now you can create a CNAME with the canonical mode with slash in your destiny page.
To answer the original question, no, what you want is not possible using only DNS (like everyone has stated). In addition to everything mentioned already, another option is to use a URL redirection service. These types of services can enable you to configure many different types of URL redirects depending on your needs. For example:
Forward a domain apex to a www. subdomain or vice versa
Forward a collection of domain names to a single destination (useful for forwarding domain misspellings, old company names, etc.)
Forward specific domain names to deeply linked pages (like what the OP wants)
A service that does this is EasyRedir. Full disclosure: I developed EasyRedir. There are certainly other options out there though, so I encourage you to have a look around.
DNS won't redirect the path portion of a URL, so that won't be possible.
Adding
www.proof.com IN CNAME www.proof-two.com
will direct access to www.proof.com to www.proof-two.com, where you will need to use web server config to direct users to the appropriate page.
A related work concluded all the below:
Problem:
http://a.com/p1/p2.html should go to http://B.com/p1/p2.html
today, but later when configured manually/automatically, the same
http://a.com/p1/p2.html should go to http://C.com/p1/p2.html
Answers:
DNS - converts name to IP address
Though it can do a lot of redirects, always output is IP address
DNS does not understand the path or protocol part of URL, understands domain part only, that is, a.com only is converted to IP address, so when you hit http://a.com/p1/p2.html may be converted to http://152.132.121.11/p1/p2.html
if you configure wrong in DNS, then you will get 152.132.121.11 (not http://152.132.121.11/p1/p2.html), so you would get some 400s error (400, 403, etc.)
Redirection - this is http://a.com/p1/p2.html can be converted to http://b.com/p1/p2.html
All the methods like GET, POST can work, with if any headers and body, but there is a web server is involved, it could be point of failure, so scalability and availability will be key
If you are on AWS, Route 53 -> API Gateway is possible though custom domains, internally using the Cloud front
It is possible with Amazon Certification Manager, AWS Gateway custom domains & Route53, note the us-east-1 restriction on ACM
Hope that helps someone
I will suppose you have this scenario: You have a unique webserver hosting various websites, each one is supposed to be presented by a separated domain:
http://example.com/customer1/website/page1.html
http://example.com/customer2/website/page2.html
so, the page1.html should be served by www.customer1.com and so on.
create a subdomain inside the example.com dns server (your webserver):
customer1.example.com
in your apache virtual server settings, map the subdomain to the directory that contain the web site for your customer #1, like this:
<VirtualHost *:80>
SetEnv PAGE_ID "customer1"
ServerName customer1.example.com
ServerAlias www.customer1.com
DocumentRoot /your/local/path/webserver/customer1
</VirtualHost>
please note the value for "ServerAlias", it is important for the next step-
at this point, you should be able to navigate to your customer1 website by browsing to:
customer1.example.com
In the DNS settings for customer1.com you must make a CNAME record:
CNAME=www
LOCATION=customer1.example.com
Now, you're enabled to use: www.customer1.com.
My solution to this problem was pretty simple and straight forward. All you need is an IIS server running inside the domain.
Setup CNAME in DNS to point to the IIS server, using host names in IIS to resolve several sites on a single IIS server. I'm using the same IIS server to farm out a few sub domains to external sites.
Then in IIS setup setup redirection for that site to go to your offsite site/path, in my case it was our hosted catalog that I wanted catalog.ourdomain.com to go to. From here all the tweaking is done in IIS. Be sure to enable anonymous authentication so traffic will not be blocked.
While as almost everyone stated already - it's impossible using just DNS. As a workaround I would suggest trying NGINX (http://nginx.org/en/docs/http/request_processing.html).
TL;DR - In NGINX you can create multiple virtual servers that can redirect your request based on the server name.
Ex. http://first.my-server.com redirect to place A and http://second.my-server.com redirect to place B, while both share a single physical server.
You can use htaccess rewrite mod, rewrite to the subfolder if the user is requesting one specific domain not the other.
Of course it is possible to redirect, with the following trick:
Create a new standard primary zone
Name it same as the fictive URL that you want to redirect to
Ensure that this fictive name is different than any AD DNS name
Create A record with following entries:
blank.......................A............................ip-addr-2
www.........................A............................ip-addr-2
What we have here is redirection, essentially. A valid URL will resolve based on the existing DNS primary DNS zone. A fictive URL will be redirected to ip-addr-2. What is important is that the name of this entry is blank, so it will fall down to the next entry in the record and redirect to ip-addr-2
Everyone has already stated this, and I just want to give you another option to a service that can help you. www.301redirect.it is a free service that can redirect your domain (with wildcard) to any destination url.
I want to add a disclosure as well: I'm the developer behind this service and there is a other options out there.

Resources