I've recently setup a new Tomcat instance on Google Compute Engine and I can access my Tomcat instance via its IP address in the browser.
I've now setup a Cloud DNS entry and had my domain registrar point my domain name to the Cloud DNS servers. However this was 2 days ago and I still can't access my website via the domain name.
The WHOIS record shows the following Name Server entries
Name Server ns-cloud-e1.googledomains.com
Name Server ns-cloud-e2.googledomains.com
Name Server ns-cloud-e3.googledomains.com
Name Server ns-cloud-e4.googledomains.com
I've also setup an A record in the Cloud DNS console based on the feedback of my domain registrar. Is there anything else I need to setup in order for all this to work?
[EDIT 1] Having a look again at the instructions provided by Google it seems the name server names they wanted me to use have changed to
ns-cloud-d1.googledomains.com.
ns-cloud-d2.googledomains.com.
ns-cloud-d3.googledomains.com.
ns-cloud-d4.googledomains.com.
I've asked my registrar to make the change in case this is the problem.
[EDIT 2] My registrar has updated my DNS records and they resolve to Google's servers. However my website still doesn't show when entered into a browser I get an NXDOMAIN error, which implies my domain doesn't exist. Does anyone have a basic example of what the Cloud DNS settings should look like? Do I need to setup A records or CNAME records?
[EDIT3] My setup is shown here (domain name and IP addresses have been faked for screenshot)
Thanks in advance.
Andy.
OK, I finally worked out the problem.
In the screenshot in my question the following changes were required.
1) Replace the A record for *.andtest.com.au with an A record for just andtest.com.au
2) Replace the www.andtest.com.au A record with a CNAME record for www.andtest.com.au which points to andtest.com.au
Now when I enter www.andtest.com.au in a browser, I see my Tomcat web page.
Related
I have a domain registered at Route 53, but I want to have Netlify manage the DNS for this domain (the entire domain, unlike other questions about subdomains). I set the NS record for the domain to point to Netlify's name servers, but Netlify's custom domain configuration tool still claims that DNS is not configured correctly.
Below is a screenshot showing my current Route53 hosted zone configuration, with the NS records clearly pointed at Netlify's DNS servers. I waited for DNS propagation timeouts, flushed Google's DNS cache, and tried other suggestions and nothing worked.
The problem turned out to be that setting the NS records in the hosted zone doesn't actually let Netlify manage the DNS for the domain. Instead, you need to change the nameservers in the Registered Domains section of the Route 53 console. (NOT the Hosted Zones section.)
On that page, remove the AWS nameservers and add Netlify's nameservers. It will look like this when it's done: (Note that your nameserver hostnames may be different; copy them from Netlify's Custom Domain page)
Kudos to Netlify's support team for writing a doc that explains how to do this. It was admittedly hard to find this doc in Google because there are so many different Netlify docs about various DNS intricacies. But eventually Googling helped me find it.
In retrospect, it's now obvious to me that adding DNS records to a zone (even NS records!) can't change the nameservers used by the domain. But it would have been nice if the AWS console included this info when I edited the NS records so I didn't waste a few hours.
Leaving this answer here for the next victim. 😁
For domain registered at Route 53 and Netlify managing the DNS. It worked for me by changing the name servers both from the "Registered Domain" area and "Hosted Zone".
I'm not sure if this question belongs here but because it is a technical question so I'm asking it here. Feel free to move it to any appropriate website of Stack exchange.
My problem is I have created a subdomain successfully on my website through cpanel and also put an index.html file in it to test it. But when I run it in browser it is not showing contents of index.html file. It shows following errors:
DNS address could not be found and ERR_NAME_NOT_RESOLVED errors. Can someone please tell me how to resolve this problem?
You must be missing A record pointing to your sub domain in your domain panel.
Record Point to TTL
A sub 300
Please check the DNS servers for your domain. You might be using external DNS servers. When you create a subdomain on cPanel, a DNS entry is created in the DNS zone for that subdomain pointing to your server ip. If your domain uses external DNS servers then those servers will be queried to find the ip address for that subdomain. In this case you should manually edit your DNS zone and add an A record for that subdomain to point to your server's ip).
Thanks for all the answers. Here is how solved my problem. The problem was that I have purchased a hosting with one domain name. I also have another domain purchase but there is no hostng on it. I had pointed the second domain to first domain which also has hosting support. So what I was doing is I was creating subdomain on second one on the first domain. But it was not recognising it and showing DNS problem. So I made an entry A record entry in the second domain about the subdomain which I wanted to create on it. And then in 5 minutes DNS was updated and issue was resolved.
After adding the subdomain, go to the DNS editor of the domain and add a CNAME record for the subdomain.
For example:
NAME TYPE VALUE
--------------------------------------------------
subdomain.example.com. CNAME example.com.
I have two hosting accounts (Personal one and a work one). I am doing some testing and would like to create a subdomain of a work domain (manage.domain.com) and host it on my personal account. Currently, my personal host is through 1and1 and is dedicated while the work one is shared with GoDaddy.
Work
I have gone into go daddy and created the subdomain. I have also added DNS records such as A, AAAA AND NS (i did not record a CNAME). I have noticed that if is type manage.domain.com it is redirecting to my personal server. However, it is directing to the blank admin page of the root of the server (which is maintained using Plesk).
Personal
Using Plesk I added the website (domain.com) and created the subdomain (manage.domain.com). I have also updated the websites hosting access using Plesk and assigned it the default values of my personal account. Using Plesk I also set the subdomain to the particular location of the files I want to test. However, I cannot get my server to recognize the address and redirect it to the proper location.
Any help is greatly appreciated!
J
You can just create:
in personal account domain(not subdomain) manage.domain.com
on domain.com add DNS record of type A, name "manage" and IP address of personal hosting:
After that "manage.domain.com" will resolving to hosting of your personal account and can be accessed because such domain exists.
I figured it out
What i did above was correct expect do not change the name servers on the work DNS(godaddy).
Add the website to plesk - it will give you an error about not being able to control the DNS settings which you have already adjusted on the original server (godaddy)
Add a subdomain of the website.
*** Ensure the subdomain is pointed to the correct folder within your server
Done
I'm somewhat new to this problem so sorry if this is an obvious question. I am building a website for a client which is hosted on Heroku. The client previously had the old website hosted on HostGator. The Domain name was purchased from GoDaddy. The client has a custom email domain (ex. #client.ca). Today I transferred the new website domain from HostGator to Heroku, and everything seems to be working well except the emails. The "#client.ca" emails no longer work. From what I gather, I have to point Heroku towards the Host Gator IP Address in order for the emails to work. I'm not exactly sure how to do this. Does anyone have a solution for this? Thanks!
You need a DNS service like dnsmadeeasy or others mentioned on heroku. From there you need to distribute the different records, e.g. ANAME and CNAME to heroku, CNAME to external asset hosts like cloudfront, MX (and A) to email host.
Am myself in the process of dealing with the "email problem":
(easier) The registrar (domain name provider) offers email hosting, but does not offer ANAME or ALIAS records (common): You can point the nameservers to the DNS service and then point the email back to your registrar. Found registrars quite helpful in general with helping if you need config details.
(more annoying) The registrar does not offer email hosting in the first place or has an all or nothing policy re nameservers (everything with them, or nothing with them, like e.g. easily). In this case you have to find an independent email host. Any recommendations? The setup is analogue.
(perfect) Your registrar offers ANAME or ALIAS records and email hosting. Lucky you!
I'm new to Amazon.
My client hosted their website www.domain.com at godaddy and
they have created the aws ec2 instance and running their Django apps in this instance.
Now they wants to use this instance for subdomain. say www.subdomain.domain.com
So I have created a record set in aws route 53 by following procedure.
Created Recordset A pointing to elastic IP
Created Nameserver (NS)
Finally added this recordset into godaddy dns files. Still I'm not able to access this subdomain. Please can anyone help here.
Are you managing DNS through AWS?
If so..
You need to create a DNS Zone for that domain.
Add the records or import the ZONE file
Take the Name Server records from AWS
Go to the domain registrar(assuming you manage this also), in this case GoDaddy!
Point the Name Server records from AWS to GoDaddy!