I am trying to point subdomain from cloudflare to digital ocean droplet. In Cloudflare, I created a record below but nothing happens do I need to do something more?
Type Name Value
A subdomain Droplet IP
Related
Problem: i have root domain, lets say "example.com" pointing to loadbalancer which further points to one of my web server droplet.
Now i want sub domain, lets say "abc.example.com" to point to different droplet which is not under loadbalancer.
What i did:
Under domain name "example.com" i added A record, with hostname "abc" and in will direct to field i added "ip address of the droplet which is not under loadbalancer". Doing this my hostname "abc.example.com" is not resolved. tried doing ping, returned no ping and tried dig it does not have answer.
Is there any way i can do this?
Hi I have an app hosted in Digital ocean, the goal is to use the newy created subdomain hosted in AWS route53. So my other project is hosted in amazon ec2, with domain name olddomain.io.Now I created a new subdomain as A, sub.olddomain.io and route traffic to digital ocean issued IP address.
Record Name Type Routing Value/Traffic to
`sub.olddomain.io A Simple - 168.173.161.227`
But I cant access the site.The site is actually working by trying the ip address in nginx configuration (in digital ocean server).
Any ideas for this? Is it possible?
Regards
I have followed the below link instructions:
https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/dns-routing-traffic-for-subdomains.html
The server is nodejs it is running on AWS server 80 port.
I have a domain on GoDaddy and want to point that nodejs server as a subdomain from GoDaddy DNS.
Follow the link above and set up the things accordingly.
Using only node server neither Apache or Nginx
but nothing helps me to get out of the issue
Assuming your domain is example.com and you have it on GoDaddy, follow the steps below:
Create a public hosted zone on Route53. This will create a record-set of type NS with 4 values.
On GoDaddy, create a record-set of type NS called subdomain.example.com pointing to all 4 names you got from the 1st step.
I am receiving the ERR_CONNECTION_REFUSED error. I have setup a Digital Ocean (DO) droplet and set the DO ns1. ns2. ns3.digitalocean.com nameservers at Godaddy.
Created an A records for mydomain.com and www.mydomain.com and both pointed to droplet's IP.
Check if the DNS is propagating in https://whatsmydns.net. If it's propagating to your Digitalocean IP, then clear your browser cache else try in another network.
I have a good understanding of DNS but this is my first time using Amazon for domain registration.
I registered a domain using Route 53 and changed the NS records to match the ones in the hosted zone file I created for the domain name. Then I created an A record pointing to the IP address of my droplet on Digital Ocean.
I'm sure I'm missing something, but do I need to set up DNS on Digital Ocean? Wouldn't that negate the benefits of using Route 53 for DNS?
I've been using Digital Ocean and a "traditional" domain name registrar for a long time now and never had a problem letting DO handle the DNS - using amazon as the registrar and Route53 as the DNS is throwing me off.
I followed Amazons instructions for setting up route 53 with a third-party registrar, but when I follow the same directions using them as a registrar, the domain name is not resolving. No response on ping.
When I try to set the name servers to digital ocean, it fails. Any help would be much appreciated.
In this case, AWS is acting both as your registrar and your DNS host. Your NS records should be set to those shown on the Route 53 Hosted Zone page. The NS record varies for each domain name, but it will be something like ns-384.awsdns-48.com.
You do not need to configure DNS in Digital Ocean, because Route 53 is acting as your DNS host.
You'll need to get the IP address of your DO droplet, and create a DNS record in Route 53. For example, you might want to create an A record for www.example.com which points to the IP of your droplet.