I've migrated one domain to Route 53. The migration was successful, but NS of domain points to NS of previous registrar. I've tried to change the values to new NS generated for HostedZone, but the operation is still stuck. In the dashboard I can see:
domainname.it --- Name server update in progress --- 2016-12-16
18:47:41
After 4 days it's always in "in progress" state.
When I try to change it again, I've got this message:
"You can't edit NS because you have an pending request"
Amazon do not provide any support for this issue. What can I do to resolve this problem?
It takes 6 days to unlock pending request. After that I was able to change NS in 2 minutes.
Related
I have a hosted zone created in Route53 and updated the NS records under the namespaces of the purchased domain.
Unfortunately the DNS check does not return or point to the new NS records instead gets resolved to old/ previously existing records.
I waited more than 72 hours and still i get "This site can’t be reached"failing with error DNS_PROBE_FINISHED_NXDOMAIN in the browser.
Below is a screenshot from the DNS check provided by https://mxtoolbox.com/,
It shows that the old NS records (First 4 rows with TTL to 48 hours) are present in the Parent and not in local whereas the newly updated records (The last 4 records) are present in the parent and not in the local.
Ping to the domain fails with Unknown host.
What are the next steps?
When you update the name servers for a domain, remove the old name server records.
Your TTL is set to 48 hours. That means any recursive resolver such as dns.google will not refresh for 48 hours after last update. For resolvers that have not cached your resource records, they might update immediately but might also get stale data from an upstream resolver. Wait a few hours so that you do not force a new cache load with old data and then check with an Internet tool such as dnschecker.org Change the selection box from A to NS to see the name server changes.
In general I recommend that it takes 48 to 72 hours for authoritative name server changes to propagate around the world.
Google DNS supports "Flush Cache". Wait an hour or two and then request that Google update their DNS cache. Flush Cache
Cloudflare also supports Purge Cache
Google and Cloudflare are very popular DNS resolvers.
Also, do not forget to flush your local computer's DNS cache:
Windows: ipconfig /flushdns
Linux: sudo service network-manager restart (ubuntu) or sudo /etc/init.d/nscd restart
macOS: sudo dscacheutil -flushcache followed by sudo killall -HUP mDNSResponder
I would like to have a custom "under maintenance" page show up if my webservers on EC2 go down.
My current setup 2 A records on Route 53, using DNS Failover with a static page as the secondary and the ELB instance as the primary.
The problem with this is DNS caching - when the server first goes down, the default 502 error appears for a while for clients who were recently on the page. It takes around 5 minutes for our custom maintenance page to show up for them. When the servers come back up, it also takes around 5 minutes for the maintenance page to go away.
The first problem is more pressing for me - I don't want users to see a plain "502 Bad Gateway" message, ever. If they visit our site and things are broken or down, they should always see our custom maintenance HTML page, regardless of whether the ELB targets went down half a second ago or 10 minutes ago.
How can I make it so that if my ELB instance returns a 502, the users will automatically see a custom error page 100% of the time, so that they never see the default "502 Bad Gateway" error page?
We are trying to configure this same thing for our web application. We see the exact same enhancement request pending with AWS since a long time: https://forums.aws.amazon.com/thread.jspa?threadID=72363&start=125&tstart=0
The other option is to use cloudfront for the whole application (not just static content) and configure custom pages for specific error codes: https://docs.aws.amazon.com/AmazonCloudFront/latest/DeveloperGuide/custom-error-pages-procedure.html; we don't like this option for multiple reasons, one of which is the added complexity.
So, at this time, it looks like we will have to live with this default 502 page.
I transferred my domain ( simplifybits.com) using Route 53 and it successfully transferred.
However my domain is not resolving anymore :(
This is what my setup looks looks like
There are two buckets in S3
simplifybits.com
www.simplifybits.com
Route 53 configuration
simplifybits.com - A
s3-website.us-east-2.amazonaws.com.
simplifybits.com - NS
ns-1069.awsdns-05.org.
ns-31.awsdns-03.com.
ns-1556.awsdns-02.co.uk.
ns-535.awsdns-02.net.
simplifybits.com - SOA
ns-1069.awsdns-05.org. awsdns-hostmaster.amazon.com. 1 7200 900 1209600 86400
www.simplifybits.com - A
d3v4utl52t4eyk.cloudfront.net.
I had this same problem. Right now your domains still have Google as the name servers:
Tech Email: tech#simplifybits.com.whoisprivacyservice.org
Name Server: ns-cloud-d1.googledomains.com
Name Server: ns-cloud-d2.googledomains.com
Name Server: ns-cloud-d3.googledomains.com
Name Server: ns-cloud-d4.googledomains.com
It isn't obvious but go to the "Hosted zones" tab and select your domain. Then, copy the "NS" records. Now go to the "Registered domains" and select your domain. If you look you will likely see to the right that the "Name servers" still have Google. Click on "Add or edit name servers" and enter your name servers from above. The popup will keep adding lines for you.
It took me a while to get this right as, like you, I thought I had to only have the NS records correct but that isn't enough.
As #steve-harris points out you will still have to have S3 enabled to serve static content but you'll want to get DNS going first.
I have a site hosted on AWS and recently the site went down with NXDOMAIN error. The site was working before and the issue doesn't appear to be with the site as the Elastic Beanstalk direct link (xxxx-prod.elasticbeanstalk.com) is working fine.
In my Route53 I have a CNAME linking to my (xxxx-prod.elasticbeanstalk.com) and a SOA and 4 NS records supplied by AWS. xxxx is a placeholder for the actual site name. Running dig...
dig xxxx.com any
; <<>> DiG 9.8.3-P1 <<>> xxxx.com any
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 63003
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;xxxx.com. IN ANY
;; AUTHORITY SECTION:
com. 895 IN SOA a.gtld-servers.net. nstld.verisign-grs.com. 1435723016 1800 900 604800 86400
;; Query time: 31 msec
;; SERVER: 64.71.255.204#53(64.71.255.204)
;; WHEN: Tue Jun 30 23:57:22 2015
;; MSG SIZE rcvd: 102
It looks like my NS records might be the issue but I am not sure. Can someone confirm.
TLDR: you need to contact your registar to figure out what's happening with the domains. You've left the domain in the question so I actually tried looking at what DNS was seeing for it.
Do you have an A record for your domain?
host vizibyl.com
Host vizibyl.com not found: 3(NXDOMAIN)
https://www.whois.net ->
Name Server: NS-1519.AWSDNS-61.ORG
Name Server: NS-1828.AWSDNS-36.CO.UK
Name Server: NS-228.AWSDNS-28.COM
Name Server: NS-544.AWSDNS-04.NET
Status: clientHold http://www.icann.org/epp#clientHold
Status: clientTransferProhibited http://www.icann.org/epp#clientTransferProhibited
http://www.icann.org/epp#clientHold
for clientHold:
This status code tells your domain's registry to not activate your domain in the DNS and as a consequence, it will not resolve. It is an uncommon status that is usually enacted during legal disputes, non-payment, or when your domain is subject to deletion.
Often, this status indicates an issue with your domain that needs resolution. If so, you should contact your registrar to resolve the issue. If your domain does not have any issues, but you need it to resolve, you must first contact your registrar and request that they remove this status code.
I wants to use Fast mail service for receiving all mails of my website but stuck in configuring the MX Record from Route 53.
I have added the MX record like this:
Name: mail.locate.ie.
Type: MX
Values:
10 in1-smtp.messagingengine.com
20 in2-smtp.messagingengine.com
When I'm testing for MX record I have found error saying:
The domain you have tested (locate.ie) does not have MX records that point to our servers. The MX records we detected are: (none)
And also no MX record were showing from other online DNS Tools like MXlookup.
Please anybody tell me what I have not done correct to point the MX to FastMail Servers.
It looks like you created the MX record under mail.locate.ie. What this mean is that only mail destined for mail.locate.ie will work. What you will need to do is create an MX record with the name field empty and put the same values in.