I'm trying to route a subdomain media.xyz.com to another droplet in digialocean. My main domain xyz.com points to a different server correctly.
My zone record looks like this
# IN A 107.170.51.xx
www CNAME #
media IN A 107.170.52.xx
However this does not work and the sub domain (media.xyz.com) redirects to my main webserver.
I've read the digital ocean tutorial on this and I think I've set it up correctly. I've also looked over questions on SO and the general advice is to create a new A record.
Could anyone tell me if this approach should work..? Or is my understanding on how this should work incorrect..?
you need to add record for your subdomain like what explained here:
https://www.digitalocean.com/community/articles/how-to-set-up-and-test-dns-subdomains-with-digitalocean-s-dns-panel
so simply in your DO control panel under your domain, do the following:
Add A record --> write down your subdomain end up with dot like this: media.xyz.com.
and your droplet IP in the 2nd field next to that: 107.170.51.xx
try that and see if it works or not!!
Related
So what I am trying to get done is:
Have UserName/username.github.io served at https://subdomain.domain.com
Have Username/project served at https://project.domain.com
I have done these things:
Put a DNS record in cpanel: subdomain CNAME username.github.io.
Put a CNAME file subdomain.domain.com in UserName/username.github.io repo.
Put a CNAME file project.domain.com in UserName/project repo.
Now number 1 works: https://subdomain.domain.com is reachable and serves the content correctly.
However 2 does not work: DNS check fails:
Your site's DNS settings are using a custom subdomain, project.domain.com, that's set up as an A record.
We recommend you change this to a CNAME record pointing at [YOUR USERNAME].github.io.
For more information, see Learn more (InvalidARecordError).
We recommend you change this to a CNAME record pointing to subdomain.domain.com.
Now if I follow the suggestion then I get UserName/project served at subdomain.domain.com/project correctly, but that is not what I want.
I followed this question, of which this one should be a duplicate... but I guess there is something different, or something I am missing.
How do I fix this ?
Trying to put another DNS CNAME record: project CNAME username.github.io.
It should work.
so my issue is as follows:
I have a website, on one language pointing to a site subdomain.domain.com. I added CNAME records and it points perfectly. I now have another squarespace page that is the clone of the other one, only in a different language. Is there a way to point it to subdomain.domain.com/en , for example, and how would one go about doing this thru squarespace and my hosting sites webmin.
You can't use same subdomain for more than once. But as you own, and have access to that domain you can make different subdomain. So it can be: subdomain.domain.com and ensubdomain.domain.com or even you can have subdomain of subdomain en.subdomain.domain.com. You are probably aware where it goes. You can have something like: you.can.go.as.far.as.you.need.or.you.want.domain.com. ( be aware that you need to check with host first, what is included in your package or maybe do you have some limits)
I have a website setup at bryantmakesprog.10b3.com. I also own the domain sneaky.fish. I want my domain to point to this website by pointing to to the url, NOT the ip address. The end result being that visiting sneaky.fish/sample-page renders bryantmakesprog.10b3.com/sample-page but the URL says sneaky.fish/sample-page.
What would be the best way to go about this? I've seen some people have CNAMEs setup, but I'm not having any luck. Here's what I've tried:
To clarify, the domain must point to the subdomain. It is not sufficient to point to 10b3.com.
So there were two parts to this issue.
The first, the CNAMEs worked, it was just a matter of waiting.
The second issue was with the subdomain. sneaky.fish redirected to 10b3.com, and only bryantmakesprog.sneaky.fish would redirect to bryantmakesprog.10b3.com.
The solution for this was to use PHP to determine if a CNAME record exists pointing to bryantmakesprog.10b3.com and to handle that accordingly.
I want to redirect a subdomain of a domain I have on CloudFlare, to a Google Calendar (HTML/embed version).
I assumed I needed to use Page Rules to do this, which I have done by following CloudFlare’s documentation. However just following these instructions did not work for me. Apparently I need to add the subdomain to my DNS records on CloudFlare, but I don’t know how to set this up correctly since I have no server or IP to point it to (or I’m just confused as to why I need to even point it to something when I just want to forward a URL).
As mentioned I have no server to point it to – and thus can’t use a .htaccess solution – so don’t know what record type I should be using to use to just have the redirect working
I've had some success just using google.com as the CNAME record, then using a Page Rule to redirect everything on that domain. Because CloudFlare changes the DNS entry to its servers anyway (when you do the orange cloud thing) nobody will know.
I don't know if you could do that directly from cloudflare, but you can solve this using your hosting.
Point subdomain to your hosting server sub IN A 1.2.3.4 via cloudflare
Create sub.domain.com on you hosting
Place redirection script in index file in subdomain sub.domain.com document root:
<?php
header( "Location: http://docs.google.com/your-url-and-so-on" ) ;
?>
"subdomain to my DNS records on CloudFlare, but I don’t know how to set this up correctly since I have no server or IP to point it to"
This doesn't make much sense. A subdomain has to point to a record of some sort (A record or CNAME), so the subdomain wouldn't resolve without a record type of some sort. In order for a PageRule to work, two things have to happen:
The record has to be in your DNS settings.
The record has to have our proxy running over it.
It might be easier to figure out with the actual subdomain in question & what you're trying to forward to specifically.
So CloudFlare does support this through PageRules, you just need to get the URL correct.
I've got an organization page set up and running in GitHub and things seem to be working...but I'm a little confused. I'd like to actually understand the process since the GitHub Help article refers to taking advantage of their CDN and DoS services, so bear with me.
Step 1: Created CNAME file in repo with domain 'example.com'
Step 2: Grabbed IP from dig example.github.io +nostats +nocomments +nocmd
Step 3: Entered IP from Step 2 into the 'A' record (see image below)
I decided to stop here and see where it got me, and to my surprise it seems to have done the trick. The example.github.io domain correctly redirects to the example.com domain and displays the content from the repo.
However I was informed that after the DNS props, you can dig example.com and see the CNAME record pointing to example.github.io. I do not see this, and I dislike thinking that I didn't set things up correctly. Any thoughts/comments/tips welcome, thanks!
In order to take advantage of the CDN and DoS services provided by GitHub Pages, you'll need to set up a Subdomain (eg www.example.com or blog.example.com) instead of an Apex domain (example.com).
From the GitHub Help page you referenced:
If you are using an apex domain (example.com) instead of a subdomain
(www.example.com) and your DNS provider does not support ALIAS
records, then your only option is to use A records for your DNS. This
will not give you the benefit of our Content Delivery Network.
Here's a setup (looks like you're using GoDaddy for DNS) that would work to get your Organization Pages working as desired:
This is actually for a Project Page within an Organization, but for either one, you'll set the CNAME record for www to organization.github.io, not something like organization.github.io/project. Don't change the A record for # (mine is the default from GoDaddy).
If you want to get your Apex domain (example.com) to redirect to the new subdomain (www.example.com), then you can point your Apex to your subdomain with Domain Forwarding like this:
With that setup, you'll get to take advantage of GitHub's CDN, which you may notice is provided through fastly. Here's how my domain looks to dig:
It is also possible to use a CNAME record for an APEX domain using the free DNS service provided by CloudFlare in which case you can also use your domain without the www (or any other subdomain) and still benefit from CDN & DoS.
I've written a step-by-step guide here: Speed up your GitHub Pages website with CloudFlare
PS: Apparently using ALIAS records is a bad idea... click here to see why.
DNS records are publicly available. There's no way of masking them in this instance. From the way you describe it, you have done everything right. There is nothing that makes me thing you set this up incorrectly.