I am trying to map my domain name to my heroku app. As it stands now only
www.mysite.com
will work. I want to map it so
mysite.com will work
I am currently using free versions of Heroku and Zerigo and my domain is registered with Hostgator. I have followed all the directions on the heroku site, which have gotten me to the point where www.mysite.com maps to my app but what I want is for
mysite.com
to be mapped to my app. I'v seen the examples that speak of dnssimple etc. But can this be done with Zerigo and if so how. if you click the link from the heroku Custom Domain Names for Apps it takes you to a page with a list of definitions and not how to configure the root domain. I'd appreciate any help. or guidance. Also a lot of what I've been googling for help is 2-3 years older or more. I have just gotten my site live and am new to programming. Thanks
I actually did this a while back but ended transferring to DNSimple (for other reasons). The simplest explanation was actually posted a few hours ago in this thread:
According to https://devcenter.heroku.com/articles/custom-domains you must add a CNAME record like "CNAME www example.herokuapp.com" first at Hostgator. After that, you must add www.example.com (with or without www) as a custom domain to your project. It's really simple.
Source: How do I point my domain name from hostgator to heroku
Related
I am running ContentBox on Lucee using CommandBox. In my ContentBox Admin, when I first set it up, I had it running on 127.0.0.1. Later, I created a web.config and updated the host file to use mydomain.com (I am using mydomain.com here as an example. The actual domain name is different). I have restarted the server a few times and even re-initiated a few times. However, cb.siteBaseURL keeps returning 127.0.0.1. My question is, where is cb.siteBaseURL getting the URL from? While I might have overlooked, but I have looked at every field in both Settings and Geek Settings and I don't see anything that have to do with the base URL.
NOTE: I wish I could tag ContentBox. However, it does not currently have a ContentBox tag. To create a new tag, I need 1500 reputation, which I don't have. So, Lucee, CommandBox, and ColdBox are the best ones I can come up with
First of all, we have a dedicated community forum for ContentBox here: https://community.ortussolutions.com/c/communities/contentbox/15
The issue you are experiencing is because ContentBox is multi-site. So each potential host needs to be mapped to the domain in question. Each site has a base url that you must define in order to build links and execute things. So when you install ContentBox, we have no clue which domain you will attach it to, so it defaults to the 127 ip address.
So now that you have a domain, just go to the Sites and update the base url to your domain.
I am trying this since last 2 days.
I build an example app using a very detailed tutorial here - https://john2x.com/blog/wildcard-certs-from-lets-encrypt-cert-manager-ingress-nginx-gke.html
What I have working right now:
I have an app running at demo-app.example.com wherein users can have their own subdomain like john.demo-app.example.com
I got the wildcard certificates working as well
I have two questions now:
1 - How do I allow users to add their custom domain pointing to the subdomain in my app. When I just create a CNAME pointing to a subdomain in my app, it does not work, I think because of how the whole thing is configured.
2 - I want to move from demo-app.example.com to just example.com to the top level, so how should the DNS zone be configured for this?
Finally, given the requirements, is Kubernetes the best I could use or I would be better off using something else. It is a NodeJS app btw.
I'm trying to point my hostgator domain name to my heroku app, but I keep getting the error when I try to manage my domain names.
An error occurred. Please verify the validity of your nameservers and try again.
I've already added the domain name to heroku in the sites dashboard > settings. My app is free, I'm ready to move up and pay for the full version. I've been figuring some things out and I am ready to deploy. And to do this I have to point my domain name to heroku. I know I'm missing something. I've read the docs already, a lot, But it's not all the way clear. I know it's something simple I'm missing. Thanks in advance
EDIT. I don't want my domain to be a subdoamain. I want it to be the main domain. because you can't monetize a site that is a subdomain.
EDIT to be clear I want the domain name mysite.com from hostgator to be used with my heroku app. So when I type mysite.com my heroku app appears. I want my heroku app to go from this
mysite.herokuapp.com
to this
mysite.com
and I do not want it to be a subdomain
I'm going to outline two approaches here. One works if you still have cpanel because you're paying for hosting with HostGator. (That makes no sense if you're using Heroku for hosting, so it's not a long term solution.) The other works if you just have a domain registered with HostGator and theoretically in either case.
Either way, do this:
heroku domains:add www.mysite.com
heroku domains:wait 'www.mysite.com'
1) If you have hosting with HostGator
Log into your HostGator cpanel interface at mysite.com/cpanel. Scroll down to Domains and open up the Advanced Zone Editor (click the link). You're not going to add a record. Instead, you're going to change one that's already there. Find the record with the name "www.mysite.com." (it has a period at the end) with the type CNAME. Click Edit. Change the CNAME field to the DNS target heroku gives you when you type heroku domains or scroll down to Domains And Certificates under Settings in your Heroku dashboard. Mine looks like www.mysite.com.herokudns.com. Finalize the change.
Visit www.mysite.com. Please put www in the url. www must be in the url. This should now point to your Heroku site. Perhaps you will see a 400 (bad request) error. This might be because your backend isn't allowing Heroku as a host. If you have a Django app, for example, that's not in debug mode (you should set DEBUG to False for security reasons), you must also set the ALLOWED_HOSTS list in settings.py to include 'www.mysite.com'. Otherwise you'll get 400 errors when you try to access the site from the www.mysite.com domain.
The end result is that www.mysite.com points where you want it to, and so will www.mysite.com/some_page.
But what if a user types in only "mysite.com"? They'll be directed to your HostGator site. A simple solution is to go to the CPanel's Redirects section, also under Domains, and make a permanent redirect from your domain (leaving the textbox that starts with "/" blank) to http://(((www.mysite.com/))) [StackOverflow won't let me put it in without something like parentheses there.] All this does is force "www" to appear in the URL even when the user doesn't type it.
Now, whatever the user types in, they'll end up at your Heroku site. I don't mind having a "www" hanging out in the URL box, so this works for me.
2) If you don't have hosting with HostGator, just ditched it, or simply don't like the company (quite understandable)
If you don't have HostGator hosting or ditched it, you probably can't access the cpanel stuff. First, add the domain as shown at the top. Now install the PointDNS add-on for Heroku. It automatically syncs with your custom domains (even after you install it). So when you open up PointDNS in the Heroku dashboard, you'll see it set up with basically everything you need. In HostGator, at https://portal.hostgator.com/domain/manage), click on your domain name and find the link to change the nameservers. Select Manually set my nameservers, and replace the default nameservers with the nameservers you see labelled with NS on the main page of the PointDNS add-on page. (You're also free to add more or or change them in PointDNS.)
HostGator says it will take a couple days to propagate. I saw the change take effect within seconds.
If it doesn't work without www. now (check pages besides the index page), I've outlined a potential solution here.
With this PointDNS solution, you may want to test your site at different places in the world to make sure it's available there. I made sure mine is available from places where I expect people to view it, but it's also available in Beijing, so I don't think you'll have geographic limitations with PointDNS. I like to use www.webpagetest.org to test the site from different locations.
According to https://devcenter.heroku.com/articles/custom-domains you must add a CNAME record like "CNAME www example.herokuapp.com" first at Hostgator. After that, you must add www.example.com (with or without www) as a custom domain to your project. It's really simple.
How do I use a custom (sub)domain (or secondary page) on AWS to 'host' a Tumblr blog?
I'm using Amazon S3, CloudFront, and Route 53 to host a static website. The static news/blog section I've made lives under http://wavefrontbiometric.com/news.html. So far, so good.
Now I've set up a blog/news page on Tumblr (so http://wavefrontbiometric.tumblr.com) that I want to have replace http://wavefrontbiometric.com/news.html. I understand that this might need to change to a two-level structure http://news.wavefrontbiometric.com/), and that's fine.
So far I've tried following these instructions from Tumblr, but with no luck. I've added a 'Hosted Zone' on Route 53 for http://news.wavefrontbiometric.com/, but failed to point the C-NAME record to 'domains.tumblr.com'.
Basically I'm using Tumblr as a backend for the news page only. Users shouldn't be able to notice any visual difference from any other page. I've already got my HTML & CSS markup perfected.
Any help is much appreciated. Thank you.
The only interaction between Tumblr and your (sub)domain is Route53. No other services are needed. Your subdomain should be a CNAME as shown in the instructions; if that isn't working, something is wrong in your Tumblr configuration, which is outside the scope of stackoverflow.
When I originally wrote the API for my website, I wanted to have it as a subdomain like so: api.example.com. That worked. Now I am changing it so api can only work when trying to access it as part of the URLL example.com/api/.... Now this works except locally api.example.com/api... works still. More interesting is the fact that some random subdomain does not work. On the production site though any subdomain works, which is not what I want. Is there a way to ensure that subdomains aren't caught by the root in Rails 4?
As an extra question that hopefully is answered, but doesn't have to be, how can I redirect to another subdomain using the routes. I haven't been able to figure it out and I am wondering if it is possible.