I have a Route53 public hosted zone containing the normal CNAME/A/etc records for using an S3 bucket to host a static website, yet "nslookup" on these records fails, and I don't know why.
The domain remains unavailable on the internet, presumably because these DNS records fail lookup.
One of the AWS troubleshooting guides recommends using "nslookup" to check the hosted zone records, but it doesn't say what to do if it does fail.
My question specifically is : since "nslookup -type=A my_domain" fails for one particular hosted zone, what can I try to resolve it?
I can see the records there in the hosted zone.
(I have another hosted zone which works fine - it uses a S3 bucket to host a static website. The website is publicly available and "nslookup" on the hosted zone records succeeds. I've tried to make the troublesome hosted zone equivalent to the working one, but to no avail.)
I already:
confirmed the hosted zone is public.
confirmed the NS records of the hosted zone match those of the registered domain
tried ipconfig /flushdns
The NS and SOA records do exist, they were auto-created by AWS (are clipped from the screenshot).
Edit:
The response from nslookup is:
Server: cache1.service.virginmedia.net Address: 194.XXX.X.100
*** cache1.service.virginmedia.net can't find bXXXXXXXXXXe.com: Server failed
Credit to kdgregory who got to the bottom of it, "nslookup" was not working because of some config with my ISP/router, the relevant comments are repeated here:
"This appears to be a problem with cache1.service.virginmedia.net. I tried looking up my personal website using it, waited for what seemed like 30 seconds or more, and got the message "connection timed out; no servers could be reached". My next guess is that Virgin Media is your ISP, and your router is configured to use their nameserver by default"
"You can try another nameserver, such as Google or CloudFlare, to verify that your hosted zone is set up correctly. Run nslookup without any command-line arguments, enter server 8.8.8.8 as the first interactive command (this is Google's service), then enter your hostname as the second command. Ctrl-D or Ctrl-C to exit"
Related
I have followed the instructions at https://docs.openshift.com/container-platform/4.11/installing/installing_gcp/installing-gcp-account.html#installation-gcp-dns_installing-gcp-account for setting up an openshift trial.
All steps I managed to get working excpet for DNS steps mentioned.
I created a zone my-new-zone for my subdomain in GCP clusters.mysite.com and pointed DNS NS's to google (ns-cloud-d[1-4].googledomains.com) and I am able to interact with my openshift just fine.
However, in so doing, all of my other DNS entries for mysite.com no longer function.
I tried creating a second zone my-zone in GCP for mysite.com and added those preexisting entries there, but they came up with different GCP DNS NS servers (ns-cloud-a[1-4].googledomains.com).
How can I fix this so that I can access the openshift and also access my original sites?
Note: I can destroy and recreate the openshift cluster as needed at this point, but I need to know the correct steps for getting the DNS right.
Additional clarifications:
Note 1. I thought I had included above but apparently left out this detail: [mysite].com DNS entries were maintained at Dotster.com. When I got to step 6 in the linked instructions, I had to call Dotster.com because I could not understand how to proceed. I was told I could not use separate NS servers for the subdomain and they asked if I wanted to point the NS servers for my domain to the GCP servers indicated. I agreed and they repointed the NS servers. At that point I tried to add my DNS entries to GCP to restore access to my primary sites, and am not understanding how to do so. GCP will not allow me to change the zone name from clusters.[mysite].com to [mysite].com. It looked like all I needed to do was add another zone for [mysite].com, so I did so, not expecting the second zone would use totally different nameservers.
PROBLEM: DNS does not work for primary domain after setting up OpenShift on GCP. My website is down, my email is down, all of my sites are down.
Objective/Goal: Restore DNS service for primary domain entries AND have OpenShift working correctly.
Errors:
$ nslookup www.[mysite].com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53
** server can't find www.[mysite].com: SERVFAIL
As for why I created a subdomain, I already had my domain set up at dotster.com. I was following step 2 which says "2. Create a public hosted zone for your domain or subdomain in your GCP project. See Creating public zones in the GCP documentation. Use an appropriate root domain, such as openshiftcorp.com, or subdomain, such as clusters.openshiftcorp.com." And then I called dotster.com when I got to step 6 as I did not know how to proceed at that point. Please see note 1 above.
I suggest to create zone in your root domain, once created, add "A record" using your root domain then add "cname record" for subdomain. Once done, get the nameserver and place it in your domain registrar. Make sure to add other necessary record to the zone that you created in order for other service to work like email. Propagation will take at least 24 to 48 hours depends on DNS server.
I registered domain with AWS and set Hosted Zone.
inside the hostedzone i have NS with 4 records and SOA as a record type
I added A record type and point it to EC2 public IP.
in browser i can not get response when type domain name.i got "This site can’t be reached"
search here and some people advice to check NS with dig command.
dig command answered when i run in on Ec2 Ubuntu command but didn't get response when run it on my laptop.
I have other sites on roure53 but new one doesn't work.
any thought?
How did you registered the domain? Did you purchase it from a website and paid for it?
From what you said, it seems the FIRST thing you did was creating a Hosted Zone in Route53. Let me explain.
Usually when we purchase a domain from another website, after paying for it and everything we will need to tell the Domain Registrar to use the Name Servers and input a value like ns1.abcdomain.com and ns2.abcdomain.com . The purchase of a domain name usually comes with a free DNS service, so it will already have a valid name servers defined.
If my guess is correct, you created a hosted zone in AWS Route 53 without actually paying and registering a domain with a registrar (AWS is also a registrar). Therefore the domain only exist in AWS world because you created a Hosted Zone.
This explains why running dig on your EC2 provided the expected IP, because somewhere along the line the EC2 reaches AWS internal Route53 DNS service before reaching the public internet for DNS result.
If you indeed paid AWS something like $12 to purchase a domain, you might have misunderstood their interface (which can be confusing sometimes) and missed appointing Route 53 to be the domain's Name Servers.
I'm starting out on AWS and try to host a website on the platform. The S3 bucket and its content is set up and i'm able to access the website via the url s3 is providing.
Permissions and properties are set to accept public traffic and that the bucket is used to host a website. The index document is correct.
Now i want traffic to be redirected to my domain visionranger.com, but it shows the error "IP address could not be found"
I tested this issue on 4 different devices across multiple browsers (including Chrome, Safari and Firefox).
Bucket, domain and hosted zone do have the same name and as AWS recommends, I asked my previous provider if they transferred the dns services to the new provides (in this case route 53) and they did.
I waited longer than 48 hours after settings everything up before writing this so all services should be working by now - but they don't.
The image shows the dns records of route 53.
I am grateful for any help.
By running a DIG command to get the NS value of your domain it returns a SERVFAIL indicating that the configured nameservers for your domain do not contain the record for you domain.
The next step is to run a whois which indicates your configured nameservers are below:
NS1.BDM.MICROSOFTONLINE.COM
NS2.BDM.MICROSOFTONLINE.COM
NS3.BDM.MICROSOFTONLINE.COM
NS4.BDM.MICROSOFTONLINE.COM
As you're trying to use a Route 53 public hosted zone you will need to update your domain registrar to use the nameservers found under the NS record of the public hosted zone.
Follow the instructions here for your specific domain.
I have registered a domain name with Amazon Route53 and I'm trying to link it to an EC2 instance. I'm unable to do this successfully. I have read documentation many times over, I have looked at many tutorials online, I have read many stack overflow answers. I still haven't been able t figure it out. Help will be greatly appreciated.
What I have done so far:
Launched EC2 instance and installed LAMP stack. I'm running a web app on the instance.
Associated an Elastic IP to the instance and I'm able to reach my web app using this IP address.
Registered domain name with Route53
Created a Hosted Zone with the same name of registered domain
Created a Record Set with the following info:
Name: example.com (of course not literally, I have my domain name here)
Type: A - IPv4 address
Alias: No
TTL(Seconds): 300
Value: Elastic IP of EC2 instance
Routing Policy: Simple
This is the point at which I am stuck. When I run nslookup example.com DNS server name in terminal I get the desired response. Running dig domain name, as expected returns no answers. How do I finally connect the Hosted Zone to my domain name to get the latter pointing to my EC2 instance?
Documenting the solution as an answer. It sounds like you got everything correct except hooking up the hosted zone Name Servers to the domain name. This is done via NS Records. When you create a new hosted zone, it automatically assigns you Name Servers. To link the two together, you need to enter the NS records under the "Registered Domains" area.
1. First get the NS records from your hosted zone
2. Copy those records to the appropriate domain under "Registered Domains".
Note: NS Record TTL (time to live) can be as high as 72 hours (rarely), so it could take a significant amount of time for the change to be reflected in a lookup tool like dig (or browser).
It's been couple of days that I transferred my domain name from one AWS to another--dev environment to production. The problem is, the domain name isn't showing up in any DNS (Amazon or Google). I'm pretty sure I've configured the hosted zone correctly.
I'm also trying to verify SES which is failing and I also set MX records (Gmail) which don't work. The MX records and SES were set couple of days ago. Additionally, I created an A record to point to a elastic load balancer DNS name.
Any suggestions on what might be the problem? It's been couple of days and from past StackOverflow posts as well as past experience, DNS propagation on Amazon's server doesn't take more than 15 minutes.
EDIT:
Here is a timeline of events which can provide more information:
I had a domain abc.com on AWS account user1
The domain was transfered to AWS account user2
As of right now, the following hosted zone is created on user2's account:
The one thing this record set is missing is a CNAME to the load balancer which I had setup when the domain belonged to user1. However my understanding is that an A record should be good enough and it was a mistake on my part.
I'm using Windows and so I've flushed my DNS. I've tried looking up using AWS's DNS servers and Google's DNS server and nothing.
C:\>nslookup abc.com 8.8.8.8
Server: google-public-dns-a.google.com
Address: 8.8.8.8
*** google-public-dns-a.google.com can't find abc.com: Server failed
It's been a couple of days since the domain was transferred. MX records were something I setup immediately and so I haven't gotten an email. If the DNS doesn't have any clue about the domain name, something must be wrong.
NOTE: The domain name is obfuscated to abc.com.
As suggested by #michael-sqlbot, the name servers were different in the console and hosted zone. I updated the name servers to the NS of the hosted zone. I see DNS propagation.