I have bought a domain my-domain.com at Namecheap. My goal is to use subdomains of my-domain.com with Digital Ocean and my-domain.com with Netlify.
Desired result:
my-domain.com redirecting to Netlify
subdomain1.my-domain.com redirecting to Digital Ocean
subdomain2.my-domain.com redirecting to Digital Ocean
At the moment, my setup with Namecheap is this:
And Digital Ocean:
All the DNS setup is very unclear to me, I appreciate any help!
Thank you.
First off, let's not use the term "redirect" since that is not happening here :) That's a specific HTTP convention that neither Namecheap nor Digital Ocean's DNS will be involved in, once you've configured things correctly. It is a service they might offer, but it is not one you should use in most cases (neither Digital Ocean nor Netlify benefit from that kind of configuration and it will make at least your Netlify site less reliable and harder to protect via Netlify's automated SSL certificates.)
I work for Netlify (and use Digital Ocean personally), and suggest this setup:
Use the Alternative configuration shown in this article to configure your bare domain as an A record pointing to Netlify's load balancer, 104.198.14.52
Use a CNAME for your www domain pointing to your sitename.netlify.com
configure your DO subdomains as A records pointing to your droplet.
I have never worked with Netlify and Digital Ocean, but just in theory.
1) You are using Digital Ocean name servers, so you have to edit DNS records there.
2) Setup A/AAAA record for each subdomain:
my-domain.com with Netlify IP
www.my-domain.com with Netlify IP
subdomain1.my-domain.com with Digital Ocean IP
subdomain2.my-domain.com with Digital Ocean IP
Remove A/AAAA record with Wildcard (*.my-domain.com)
3) Setup your server to listen for it
Related
I am trying to setup my server on digital ocean. I am able to connect to the server by typing the ip address in the browser search box but doing same for the domain name does not work. I thought initially that the digital ocean droplet was not linked well with my namecheap domain but checking from https://whois.domaintools.com/ it seems to be linked properly
On digital ocean I have added A, # and CNAME recoreds
Also this below is my configurations for nginx.
I'll be glad if anyone can point me in the right direction or show me if I'm doing something wrong
I figured this out. Apparently I was redirecting all traffic from http to https while the https was not setup. adding an SSL certificate, in my case with let's encrypt fixes the issue.
I have a domain from Google Domains. It is configured to use the Google Domains name servers. I created an A and CNAME record pointing to my Netlify site where I'm using Gatsby.
In Netlify, I have my default domain (provided by netlify) Primary domain (the one purchased from google) listed in custom domains settings.
In DigitalOcean I have a One Click Wordpress droplet installed with the domain/subdomain of admin.{mydomain}.com pointing to my droplet.
When I access admin.{mydomain}.com I receive the This site can't be reached admin.{mydomain}.com's IP address could not be found. screen.
I can access my digital ocean droplet through the IP address, but when I try to access {ip address}/wp-admin, I'm redirected to {domain}.com/wp-admin which is a default Gatsby Not Found page.
Where do I need to configure the subdomain of admin.{mydomain}.com to point to my digital ocean droplet and what do I need to configure?
{mydomain}.com properly renders the site with Netlify. I can access the main page of the wordpress instance through the ip address on Digital Ocean.
I have a VPS server on OVH, it just has its own ip and Reverse DNS.
So i basically always used domain trough cloudflare and pointed a record to my VPS IP.
I don't want to use cloudflare anymore, I've bought the DNS Anycast option for my domain and pointed a record to my VPS IP, but website just stopped working.. What should i do ?
I have 3 more domains, i would want to make some ns1.mydomain.com ns2.mydomain.com zones based on my main domain, so i could use it for all my other domains, How can i do that?
ps. In case if this info is needed, all my domains are in OVH too.
1) You could revert back to previous state. Other than that, it is difficult to troubleshoot DNS issues without real domain name.
2) DNS is crucial part of infrastructure, you don't want to host that by yourself unless you know what you are doing.
We are hosting our website on CloudWays Digital Ocean server, and our application is a PHP Stack.
That means the domain name isn't using ns1 ns2 as usual, but is using CNAME record to point to the PHP stack.
We need to start using CloudFlare CDN with our website, and I already know CloudFlare is implemented by changing the nameservers ns1 and ns2 to their nameservers.
But we're not using nameservers on our domain.
So, how do we start using CloudFlare, how do we set it up so it starts receiving traffic from the domain that points to our PHP Stack with a CNAME record?
Your domain will always have a nameserver option. Once you point your DNS to CloudFlare by changing your nameservers, you can then from CloudFlare point your CNAME records through CloudFlare to your Digital Ocean server.
If you are asking how to set-up CloudFlare without changing nameservers via a CNAME set-up, you either need to be an enterprise customer or need a company who is a CloudFlare Partner to set this up for you.
I think this question needs to be updated. Now, Cloudways offer a Cloudflare Enterprise plan for their customers (integration with a few clicks) and when it comes to a free Cloudflare plan then read this guide: https://www.cloudways.com/blog/wordpress-cloudflare-cdn/
I have an instance of openshift origin on digital ocean. Everything is working but when I create new apps it become a pain with DNS records. If I create a new domain, (php-test.openshift.example.com), the DNS record is not added to the zone file for the domain on Digital Ocean so when I try to access it I can't get anything. My solution so far has been to add the url to my /etc/hosts/ just before creating it and everything works fine but this is annoying. My question is has anyone run into this issue and how did you solve it? Did you have to make your openshift server be the actual nameserver for your domain (example.com) or were you able to hook it up to the digital ocean api using some kind of hooks system?
The default install expects that other hosts will resolve application fqdns using the installed DNS server.
To publish to an external DNS server, you will need to configure a DNS plugin, the nsupdate plugin configuration is documented here: http://openshift.github.io/documentation/oo_deployment_guide_comprehensive.html#configure-the-dns-plugin
There is also a route53 plugin (source code: https://github.com/openshift/origin-server/tree/master/plugins/dns/route53)
You could also create your own custom DNS plugin by using the nsupdate plugin as a template.