I have purchased a domain name from Godaddy. I would like to point this domain to a server EC2 instance on AWS. On my registrar's web site I specified AWS name servers which i created using Amazon Route 53. Using Route 53 I created specified DNS record (NS, A, SOA) please have a look at screenshot. I waited > 24 hours for changes to propagate but I can't access my website via my domain name.
I have created one A record mydomain.in but still my site didn't work then i created two more A records named as www.mydomain.in and *.mydomain.in but didn't work this time as well.
Please let me know what's incorrect.
Any help would be appreciated.
Thanks in Advance.
Your Domain Name is still pointing to other nameservers [ns1.bodis.com, ns2.bodis.com] than the ones on your route53. you need to change that !
To do so you can refer to this tutorial
and then you can fill in the NS fields with the ones given in Route53 [ns-1825.awsdns-32.co.uk, ...]
Related
I have deployed an app on Heroku, and everything is going great when the app is being accessed from the herokuapp.com domain. I tried adding a custom domain and have followed the instructions from the documentation, but unfortunately, I encounter a DNS_PROBE_FINISHED_NXDOMAIN error when trying to access the app from my custom domain.
Some articles pointed out how Heroku requires the usage of ALIAS ANAME or FLATTENING records, which may not be available in DNS providers. I am using a local DNS provider where Name Server configuration is not directly accessible, and only the DNS provider admin can configure it on my request, so I am unable to check the CNAME Records and such (probably because I use .id domain, which I believe to have a somewhat specific configuration due to its affiliation with the country Indonesia, could be wrong though).
For my Name Server, because my DNS Provider requires at least two different name servers, I registered the domains for my Heroku app (from the Heroku settings dashboard > add domain and from the CLI) as follows:
my-domain.id
*.my-domain.id
www.my-domain.id
Is there anything I can do to fix this? Any help would be highly appreciated! Thank you!
EDIT:
I have just been informed by my DNS provider admin that the name servers I used, which I got from Heroku ([haiku].herokudns.com) does not have IP address. Is there anything I did wrong on the configuration?
As it turns out I managed to find my own mistake! It turns out that I provided the DNS Target as Name Server to my provider, which is totally not the same thing. What solved my problem was simply asking the provider to register a CNAME with the DNS target from Heroku as the value.
Be sure to provide the correct DNS Target for the domains as the DNS Target produced for registering root domains like your-domain.com will be different from the DNS Target produced for registering subdomains like www.your-domain.com or when using wildcard tag (*.your-domain.com). Also, note that Heroku doesn't recommend the usage of A Record for root domains, so be sure that your DNS Provider supports the record types needed as this Heroku article suggests.
Thank you #Ruurtjan Pul for getting in touch! Hope this helps!
I want to upload my local wordpress to the domain I bought and make it live. But I don't know how to add domain and add dns in oracle cloud.
Unfortunately, there's no simple answer to your question. The general documentation on using Oracle Cloud DNS Service can be found here. Below is a quick summary of tasks that need to be completed:
Note the public IP address assigned to your compute instance that's hosting the web server. Assign one if necessary. The compute instance must be on a public subnet to be assigned one.
In your tenant's root compartment, create a Zone for your domain, e.g. example.com.
Create an "A" zone record, e.g. www.example.com => 123.123.123.123
Publish the record.
On your Registrar's DNS management console, update the name server records to point to Oracle Cloud's name servers assigned to the zone.
I'm trying to do something pretty simple. I have a domain on godaddy. I want to use Azure Dns to host the domain and connect it to an azure website.
I have it working for www.mydomain.com with the CNAME approach. However I cannot get the root domain, i.e. my domain.com to work with this approach. I tried adding an * A record but that didn't work. I also tried to do CNAME with # but that didn't work either.
Does anyone know how to get the root domain to work? This seems pretty basic but there is no documentation and it is not obvious.
Thanks
Thanks for feedback on this one!
If you need to create the isolated deployment with the static IP, take a look at the Service Environment. The reference first and second.
As you mentioned Azure DNS, i assume that you refer to the Azure DNS service. If so, then it is possible if you have the needed access. Reference for the DNS zones.
Regarding your question about www and CNAME, there are some nuances that should be taken into account and set up. Please refer to that post.
You can set up a DNS 'A' record in Azure DNS to point to the IP address listed for the site in the Web Apps portal (as per the screenshot provided by an earlier answer). The Web Apps team provide the IP address for precisely this purpose, and they know that they can't change these IP addresses because DNS entries would break.
Note that there's no need to use a wildcard record (name = '*'). You should instead use an A record at the domain apex (name = '#', or if using the Azure Portal you can also leave the name blank).
If your hosted your WebAPP in free website plan didn't have any option for adding * A record. You have to Change your web App plan to at least Shared Plan instead of free Plan.
I'm using Route53 to address EC2 instances within a VPC, and I set up my subdomain and CNAME records as described in this blog post. (I'm using name.com to manage the main domain, but my setup is otherwise identical.)
At first it was working fine, but then I noticed that the domain name record intermittently becomes invalid (NXDOMAIN), then resolves properly again a while later.
I used a script to monitor this over the course of several hours, and found that the time in between is always a multiple of 300 seconds, which happens to be the TTL of the subdomain in R53.
What might be the cause, or how can I proceed to debug this?
It sounds like you may have misconfigured one of the 4 assigned "ns-xxxx.awsdns.xx" authoritative DNS servers when you pointed your domain to Route 53 with your domain registrar.
Verify those settings.
For people who encounter this in the future: I stopped using the Route53 approach, and am using this one instead: http://alestic.com/2009/06/ec2-elastic-ip-internal
I have a domain registered with Dreamhost
I have an EC2 instance with the site running (that I can access by its IP address)
I'm using Amazon Route 53 for a hosted zone
I have pointed my DreamHost name servers to the ones provided by Amazon (and it has been over 48 hours)
The only thing I don't understand how to enter is the SOA record provided by Route 53. There doesn't seem to be an option in the DreamHost DNS management console to add it.
Going to the website gives the standard "DNS record not found" from my service provider.
What am I missing? I will really appreciate any help :)
In Dreamhost:
Use the values in NS (provided from AWS Route53) with your domain registrar(dreamhost).
In AWS Route53:
Add an 'A Record' with IP of the EC2 instance in value.
To resolve www to the naked domain name you could use, CNAME record, I have attached an image with some values masked.
Hope this helps.