Having trouble configuring custom domains on Xervo - node.js

I have a meteor project deployed on Xervo here. I have a domain bought from GoDaddy, ustechland.com. I'm configuring custom domains in my project's administration panel on Xervo.
2
*.ustechland.com means all subdomains of this domain will point to this project. Now when I hit ustechland.com in the address bar, the URL changes to the project URL (https://utl-95476.app.xervo.io), which I don't want to happen.
I have configured CNAME records in my GoDaddy's domain DNS as specified by the Xervo Docs here.
Here is my list of CNAME DNS Records in GoDaddy:
4
Although, the Xervo custom domain docs specify to add two CNAME records, I'm able to add one CNAME record with www subdomain pointing to Joyent Servo in US-East. Another record with naked domain (#) must be added pointing to the same. But I'm not able to add this record as GoDaddy says the record already exists.
Now, is the URL changing because I'm not able to add the CNAME record required? Do try hitting ustechland.com or www.ustechland.com and see the URL change.
And at times, both these URL's take me to 'Future home of something quite cool' page.

I have found several sources that claim that godaddy does not support root cname flattening (which is what you want).
Check out these ideas for how to deal with this.
CNAME Flattening With GoDaddy.
Quora Answer
Good luck!

Related

Adding Sub-domain in Route53 for CloudFront

I followed the steps on creating sub-domain via Route53 by creating a new Hosted Zone for cdn.domain.com and added the NS to the registrar in addition to the root domain, domain.com NS.
I then added Alternate Domain Name in the CloudFront Distribution that reads cdn.domain.com and saved it. I then waited for the status to get deployed.
My question is,
Do I still need to add an A record for the sub-domain that I created? If so, where will it route?
If I don't need to create an A Record, shall I add a new record CNAME on the root domain Hosted Zone or on the sub-domain Hosted Zone? Because I see no target Available.
IPV6 is also enabled on the CloudFront Distribution. Please advise on what would be my next step.
Thank you!
I'm not familiar with the method of multiple hosted zones for the same domain, be sure to use the correct NS servers. (see here)
The simple approach is to on the root domain add an A record for the subdomain, with an alias set to the CloudFront distribution.

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

Having problems creating MX records for subdomain on dreamhost.

I have a domain on dreamhost, say block.com. This domain points to an address outside of dreamhost (amazon AWS).
I also have a subdomain, us.block.com that is hosted on AWS. This subdomain is not registered on dreamhost (as dreamhost doesn't allow subdomains to be hosted outside of dreamhost). To point to this subdomain, I've added in a couple of custom A records to the DNS records on dreamhost.
Since the subdomain is not registered on dreamhost, it doesn't allow me to add custom MX records. Is there anyway to get around this? If there isn't, can I somehow point the mail server of us.block.com to that of block.com without using mx records?
You can do that with a little trick:
Domains > Manage Domains
Fully host your subdomain
Under "Web Hosting" find "Remove" and press it
Now you can edit custom MX fields for your subdomain
Tested solution from here

Domain Forward in Plesk

I have mysite.eu working fine, and I have registered a new site mysite.co.uk which I would like to forward to mysite.eu. According to various articles on the net, this is a pretty straightforward procedure yet, I can't make it to work since when i type mysite.co.uk I get a "This site can’t be reached www.***uppies.co.uk’s server DNS address could not be found". Here are my current settings:
and the .co.uk site hosting settings
Do i also have to edit the DNS settings maybe?
Error massage you have see is about domain name and DNS, not about forwarding.
If you have recently register new domain, than DNS record of .co.uk site may be not propagated to all DNS servers and you have to wait about 24 hours.
Also check that you have www record of your new .co.uk domain:
Check for no-www record:
nslookup <you domain name here>.co.uk
Check for with-www record:
nslookup www.<you domain name here>.co.uk
If you need www part for domain you can add in your domain's registration panel.
Turns out the domain registar had not completed the .co.uk domain registration properly.

external domain to godaddy ultimate shared hosting

i have provided the following details to a domain registrar , my shared hosting account ip address, and the main domain's two DNS records which i copied from dns manager. i have added the domain in the hosted domains section and assigned a folder with a blank page in it. the domain is www.mahala.co.zw . i have gone to domaintools.com and looked up the domain and it shows its registered and returns the correct DNS records but when i visit the site it does not resolve. is there anything i missed on the godaddy side before i go back to the registrar. Please help
The best way to add an external domain to GoDaddy Ultimate Hosting is as so:
Add the domain manually in the domain section of your hosting. There is a section where it says "add external domain"
Wait about 2 hours and your domain will show as part of your domain list
Click the domain and go to the bottom of the page and then copy the now self generated DNS records (2 of them)
Apply these to the place you bought your domain (pointing your domain to these DNS records)
Go to your GoDaddy hosting, log in to the hosting account you want to use, go to hosted domains, and it should auto fill when you add the new domain name to the the list
You are done ! Good luck, God speed because GoDaddy is the worst when it comes to this process; I guarantee you none of their support section notes have such a step by step remotely close to this one I have written.

Resources