Tumblr's doc 'Using a custom domain name' is quite helpful it that it clearly states that I need to create an A-record for example.com pointing to 66.6.44.4, so that my website is accessible via example.com.
But I don't understand this: How do I make www.example.com take the user to example.com?
It goes without saying that this needs to be done via DNS, in a Tumblr-compatible way (just in case there are any incompatibilities).
From searching, I read that it's NOT possible to redirect example.com to www.example.com. I can only hope this is NOT true.
If, unfortunately, it happens to be true, my only option is to create a CNAME record pointing www.example.com to domains.tumblr.com - isn't it?
Ah! As stated in this answer, you need to create two DNS entries as such:
A record: pointing example.com to 66.6.44.4
A record: pointing www.example.com to 66.6.44.4
I checked the domain in the answer - emmaraviv.com - apparently, www.emmaraviv.com redirects to emmaraviv.com. So yeah, this is it!
You need to create two records, an A record for the two-level domain (example.com) and another A record for the three-level domain (www.example.com), then add example.com in Tumblr > Settings for your blog, and now example.com should redirect to www.example.com without a hiccup — as far as I can see it.
UPDATE: Just tested this with my blog, and yes, I can confirm that it works!
Related
I have a github project and have generated a gh pages from it and is forwarding the domain from godaddy. But I am facing issues.
1. First it is a project's website and I can't add '/' and this forces me to opt for domain forwarding.
2. Second, GitHub complains about my setup and I have trouble figuring out what to do.
Thanks in advance.
Check the GitHub docs, in case you want to point the naked domain to your gh-pages add this A records:
your-domain.tld A 192.30.252.153
your-domain.tld A 192.30.252.154
For example check this project: http://go-www.com/
The repository name needs to be go-www.github.com and also you need to have a CNAME file within the repository;
In this case, the content of the CNAME is:
go-www.com
Within your DNS provider, you will need to create a CNAME for your domain pointing to your GitHub account at github.io, for the example.
www.go-www.com CNAME <your-github-account>.github.io
Yes exactly, you can do such a thing with your Gmail to be more shorter and make you so quickly, like mailer#yahoo.com is one example, you can change your account with some none relivant letters but in a proper field like HTML5 !!!
I've been looking for a method with DNS to redirect my domain's subdomain e.g http://server.my-domain.com to https://discordapp.com/invite/server
As i found the answer of this question, i'd love to share it with all of you,
Create a CNAME on your domain named server: (or any other name you want)
Target the CNAME to: discord.gg.opts-slash.INVITECODE.redirect.center but change the INVITECODE to your server invite code
Save it and you are good to go!
Please note that:
If you want to use it for another method other than discord please remember:
.opts-slash means / for example you have http://example.com/123, to redirect your http://example.my-domain.com/ to http://example.com/123 type in the CNAME example.com.opts-slash.123.redirect.center and your CNAME name to example.
As i couldn't get it to work redirecting it directly through a CNAME, i had success by creating a simple netlify app which is just redirecting via JS:
Create index.html with the following content:
<html>
<head>
<title>Discord redirect</title>
</head>
<body>
<script>
window.location.replace("https://discord.com/invite/INVITECODE");
</script>
</body>
</html>
Place the index.html inside a folder and upload it to netlify
You'll get a unique name, such as eloquent-noyce-x00xx0
Set a CNAME to your app with eloquent-noyce-x00xx0.netlify.app. (last dot is important!)
Set your mydiscord.mydomain.com as custom domain in netlify
That's it, visit mydiscord.mydomain.com and it'll redirect you
For me redirect like previous answer doesn't work.
Free (minus the domain name) and easy solution is to use Amazon Web Services. Create an AWS account and follow this guide:
https://kennbrodhagen.net/2016/04/02/how-to-return-302-using-api-gateway-lambda/
Then use Route53 to create a CNAME to redirect to the API Gateway:
How to CNAME to Amazon API Gateway Endpoint
1) Create a Discord invite that never expires.
2) Use the .GG URL to find the .COM URL. You will be redirected in the browser when you paste the .GG URL into the browser.
https://discord.gg/abc12de (redirected to) -> https://discordapp.com/invite/abc12de
Note: abc12de (example) stays the same between the two URLs.
3) In your GoDaddy domain, scroll down and to the right. Select Forwarding.
4) FORWARD TO: (Drop down) https:// (fill in box) discordapp.com/invite/abc12de <- Note: remove https from the original URL.
5) FORWARD TYPE: Permanent (301)
6) SETTINGS: Forward Only
7) Save and wait.
8) You'll notice a new A Record is created with a TTL of 600 seconds. This shows your settings have taken and should now work.
URL with additional info: https://www.godaddy.com/help/forward-my-domain-12123
This worked for me:
Create a "A" DNS Record with name "discord" pointing to 8.8.8.8
Create a page rule of url forwarding to your server invite called "discord.mydomain.com"
The CNAME way doesn't work!
It works for me thanks full tutorial in case someone understood it.
This is for CloudFlare
Created Add Record "A"
this type "A" must contain in Name: "Name you want for the sub domain", and in IPv4 address they must place "8.8.8.8", Proxy status activated.
IMG Add Record
Then they go to "Rules"
Here they add a Create a new rule, and place the following data in URL: "yoursubdomanin.yourdomain.com", luen in Then the settings are: Select "Forwarding URL", then in Select status code: Select "301 - Permanent Redirect"
in Enter destination URL (required) you put the url of the Discord invitation: "https://discord.gg/yourInviteCode".
IMG Rules
That's how it works, in case it doesn't load you because you have already tried many methods with "discord.yourdomain.com", try another subdomain while the other one is reactivated or try from another device, example of another dub domain "discord1. yourdomain.com".
That's bye :D
We have multiple websites on GCS buckets for our subdomains:
site1.oursite.com
site2.oursite.com
site3.oursite.com
How to make www to work as well with these subdomains, so that we have:
www.site1.oursite.com
www.site2.oursite.com
www.site3.oursite.com
to point to right bucket.
To make www to work with your sub-domains, you have to create buckets with names :
www.site1.oursite.com
www.site2.oursite.com etc to get access website via www.site1.oursite.com, www.site2.oursite.com.
To access URL as www.site1.oursite.com, you have to create a CNAME record in DNS that redirects requests from www.site1.oursite.com to the Google Cloud Storage URI. To accomplishing this, you need to publish the following CNAME record in DNS:
www.site1.oursite.com CNAME c.storage.googleapis.com
I, too, believed the statement
If you want the test.example.com to serve the same content as is served from www.example.com, add a CNAME record that aliases "test" to "www". A separate bucket is not needed in this scenario.
on the documentation page and tried getting this to work for hours. Interestingly, that help text seems to be the only resource on the web claiming that this works. I believe, that this is an error on the side of those persons who wrote that text.
I resorted to additional buckets with simple http redirects for now as a workaround. Obviously, that's less than ideal.
I created a Jekyll-powered blog and am hosting it with GitHub Pages.
Now, I want to set up a subdomain (blog.example.com), but can't make it work.
I have added a CNAME file with the text: blog.example.com. And I have added two A records in my Dreamhost account for the subdomain, both pointing to 204.232.175.78, provided by GitHub.
Any idea about what the missing part is, or if I'm doing something incorrectly?
The setup is different for domains like example.com and sub-domains like blog.example.com.
In case of a sub-domain: blog.example.com
Go to Domains | Manage Domains in your webpanel
Locate blog.example.com, click Delete in the Actions column
Wait 10 minutes, and then click the DNS link below example.com
Add a CNAME record:
Name = blog
Type = CNAME
Value = yourusername.github.io. (yes there is a . at the end!)
In case of a domain: example.com
Go to Domains | Manage Domains in your webpanel
Locate example.com, click Edit in the Actions column and switch to DNS only hosting (it's at the bottom)
Go back to Domains | Manage Domains in your webpanel
Click the DNS link below example.com
Add an A record:
Name = (blank, nothing)
Type = A
Value = 185.199.108.153 (GitHub, from this page)
Add a CNAME record:
Name = www
Type = CNAME
Value = yourusername.github.io. (yes there is a . at the end!)
(Yes, you need both the A and CNAME records in this case.)
Btw, the only reason I know this is because I did the same thing last weekend. I was quite lost, but the helpful support guys helped me half way, and I figured out the rest. This procedure works for me, I needed both cases so I tested both.
Because of the way DNS records are cached across the internet, these sorts of changes can take a few hours to take effect. It looks like the address you provided resolves correctly now.
This is a little different than all the other Rails 3 redirect https questions out there. Let me explain.
In order to publish our site with Phusion Passenger we had to create a subdomain and use a symlink (or softlink or alias) from the www/rails folder to /home/user/app/railsapp.
In order for the HTTPS to work (because of various domains issues) we need to have a rewrite mod that actually creates this route:
https://my.site.com/rails
Notice the trailing /rails route.
This route does not exist on our app. So what I need is a way to redirect anything that comes in with that route to:
https://my.site.com/login
So I thought I'd do this, in the routes.rb file have this:
match '/rails' => 'sessions#redirect_to_login'
In sessions_controllers.rb:
def redirect_to_login
redirect_to login_path, :status => :moved_permanently
end
This results in the app complaining that it can't find /rais/login/ so it's still seeking that /rails bit.
If I add something like redirect_to "/" which in turn will send you to my.site.com/login with a redirect when you're not logged in, I'll get an error of too many redirects in the browser.
redirect_to login_url didn't do the trick either.
It gets a bit more complicated in the sense that whenever I'm using the https protocol for that site, it will append that /rails route so I need a way to remove it from all the links. For example, https://my.site.com/movies will get translated to https://my.site.com/rails/movies.
Either remove the /rails or redirect all https traffic to http except for the login page.
I'm sure there is a relatively easy fix for this, but I can't figure it out.
Help is appreciated.