PaaS DNS Synchronization - dns

I'm not exactly sure if this is more of a DNS question or the nature of most PaaS's.
I purchased a domain from namecheap.com. I wanted to get a WordPress site up and running so I could start development so I went over to openshift, created an account and installed WordPress, which was very easy! Only one problem... I'm having issues trying to sync my domain name from namecheap with the application on openshift. I must admit I've always purchased the domain name and hosting together so I've never had to go this route so I'm not entirely sure this has anything to do with the fact openshift is a PaaS.
In openshift, I have the URL for my application applicationname-account.rhcloud.com and I've added an alias on my namecheap.com account which works for a redirect... If I go to my purchased domain, www.example.com, it will simply redirect me to example-account.rhcloud.com. But I do not want a redirect...
I guess I'm confused as to how you get a domain name that you've purchased from one company to a hosting company. Do I need to modify something on my namecheap account?

This document states that you need to add a bare CNAME record to your DNS setup (may be what you refer to as an alias)
https://www.openshift.com/blogs/custom-url-names-for-your-paas-applications-host-forwarding-and-cnames-the-openshift-way
then add an alias to your Openshift application using the rhc command line tool, eg:
rhc alias add example-account www.example.com

Related

Hosting dns issue

I have developed a react/node.js web app and i hosted in heroku with my own domain name.
the domain name that i have added to my heroku includes www like www.example.ca and in godaddy forwarding section i have added htttps://www.example.ca.
the problem is if i now open the browser and type example.ca it wont open my website. neither https://example.ca nor http://example.ca.
i can only open it through https://www.example.ca or www.example.ca. from some browsers it opens in http and some other https.
so confused and i couldnt find a good documentation for this. any help will be appreciated.
GoDaddy doesn't support alias so you will never be able to access https://example.ca nor http://example.ca. You have to use a DNS service (DNSimple or Cloudflare) which support alias or in case you want to stick with Heroku service then choose pointDNS
Here is the flow to configure a domain with pointDNS and Godaddy
1 Add pointdns add-on
2 Add all DNS records to pointdns
3 Replace GoDaddy ns by pointdns NS something like *.pointhq.com
4 Remove forwarding from GoDaddy
Make sure you didn't add www under name.

Adding subdomain on Namecheap for Shared IP SiteGround website

I have been figuring out how to accomplish this for a day now and read through a bunch of tutorials but could not make it work the way I wanted.
So my current set up is that I have a website that I registered the domain with Namecheap, let's call it mywebsite.com. The main app is hosted on Heroku, so both mywebsite.com and www.mywebsite.com is set up as URL redirect and CNAME to point to the heroku address. For example I have a CNAME record for www pointing to www.mywebsite.com.herokudns.com. This works fine and I would like to keep it that way.
I recently registered for a SiteGround service to set up my wordpress blog. I would like it to be accessible at blog.mywebsite.com. Most of the tutorial I have seen is to either migrate the domain to siteground so the wordpress site can point to the main domain or to point the namecheap DNS nameservers to the siteground one which I don't want to do neither because I do not want to redirect the traffic away from the heroku app.
I have tried to set up NSRecord according to Namecheap doc, I added the record for blog to point to ns1.siteground1111.com (the nameservers siteground provided) but when I entered blog.mywebsite.com it said server not found. I am on a SiteGround shared IP plan and I can see the blog if I visit ns1.siteground205.com/~myusername. However creating A record or CNAME requires bare IP and domain so I wonder if that's the issue.
My question is if my approach was correct in trying to set up the subdomain by creating a NSRecord on Namecheap pointing to SiteGround's nameservers. Or is it necessary for me to pay extra and get a dedicated IP address from SiteGround for me to point my A record for blog to.
Alternatively, I also have extra domains I am not using and I could set SiteGround blog to those domains and perhaps create a CNAME record for blog.mywebsite.com to www.myotherwebsite.com? That sounds like an overcomplication of the issue but I am not sure what to try at this point.
Really appreciate any help!
In Namecheap admin for your domain name mywebsite.com:
(1) Create an A record:
[type, host, value, TTL]
A, #, 1.2.3.4, 1min
where 1.2.3.4 is the Siteground IP address of your account.
(2) Create another A record:
A, blog, 1.2.3.4, Automatic

Link a shared webhosting to an external domain

I'm confusing on something!
If I map a domain with 1&1 with a shedhosting with bluehost. Do this means that I can manage my domain from bluehost ?
in other words can I manage my domain with 1a1 (emails, subdomains...) from my bluehost without transferring it.
Thanks,
Of course you can. By the default, your domain nameservers will use registrar nameservers, in your case 1&1 service. Simply login to your 1&1 account, then change your domain nameservers to bluehost nameservers. You can find your hosting nameservers in your hosting cPanel (I assume that bluehost use cPanel). Or, if you find a trouble finding the nameservers, simply contact bluehost customer service.
After change the nameservers, then check it first to make sure the changes was take effect, use http://who.is service. Then go to your bluehost cPanel, you can manage domain name directly from there, add/remove subdomain, change dns record (A Record, CNAME, etc..) and also your mail will functioned (I assume that bluehost give you an email hosting service in your hosting package).
NOTE: You don't need to transfer your domain to bluehost, you can have your domain registrar different from your hosting provider. The only thing you need to do just pointing nameservers to your hosting nameservers.
REMEMBER: All your domain record in 1&1 account will not functioned, you need to move it to your bluehost cPanel. All A Record, CNAME, etc in your 1&1 panel must be re-written in your bluehost cPanel.
I use this method right now, and everything is ok!

Migrate customer domains to different server

I have a server running an e-commerce platform. Every customer of the platform run on the same of app but on its own domain. I've instructed them to configure DNS like so:
Create a CNAME "www" pointing to my-domain-name.com
Change the naked domain pointing to ip-of-mydomain-name
But now, I need to migrate to a new server and the IP will change. I wouldn't like to ask my customers to make the DNS change because it need to be done at the same time (I can't keep both servers (old and new) running at the same time).
I saw Shopify (and other e-commerce platforms) do the same thing I do about DNS, but I have no idea how they handle situations like mine (migrate to different servers).
I think the idea is to have customers add a CNAME instead of an A record in their domain settings.

CNAME redirection not working in GoDaddy

I have a domain name myapp.com with GoDaddy, and I've deployed the site to Azure, so now the app is in myapp.cloudapp.net.
I'm trying to set up a CNAME from www.myapp.com to myapp.cloudapp.net but it doesn't work after two days and I was wondering if I've done something wrong.
I've set up a CNAME record from www to myapp.cloudapp.net in my DNS Manager in GoDaddy, and a forwarding from myapp.com to www.myapp.com. I did this on Friday.
When I try to access myapp.com I get redirected to www.myapp.com, but then it says "Page not found", actually if I do a ping, it cannot resolve www.myapp.com, but it can resolve myapp.com.
Of course, if I try myapp.cloudapp.net it works perfectly.
There is still an A record in the DNS Manager, should I remove it? What may I be doing wrong?
Cheers.
Before this is moved to SuperUser, do you have a hosting account with GoDaddy? The reason I ask is because they don't handle your DNS for you unless you pay for hosting too.
This leaves you with two options
Pay for it
Get it free
I recommend trying the free option first

Resources