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.
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
Does dns cache clears after the max-cache-ttl seconds even if receives negative response from the parent name server which defined in resolv-file=/etc/resolv.dnsmasq..?
# Server Configuration
listen-address=127.0.0.1
port=53
bind-interfaces
user=dnsmasq
group=dnsmasq
pid-file=/var/run/dnsmasq/dnsmasq.pid
# Name resolution options
resolv-file=/etc/resolv.dnsmasq
cache-size=1000
neg-ttl=2
max-cache-ttl=5
domain-needed
bogus-priv
cat /etc/hosts
127.0.0.1 localhost
cat /etc/resolv.conf
nameserver 127.0.0.1
search eu-west-1.compute.internal
My domain resolves fine with #127.0.0.1 and not resolves with the parent name server in resolv.dnsmasq. So is it resolving from cache..? In that case I have max-cache-ttl as 5 seconds so does it maintain the cache if the parent name server provides negative response..?
The domain I am trying to dig ends with rds.amazonaws.com
Thanks in advance.
I am using the following API's for making a HTTP request.
QNetworkRequest Request (QUrl (QString (HTTP_PRF PING_URL)));
m_pNetworkReply = m_pNetAccesMgr->get (Request);
My resolv.conf has the following entries.
nameserver 8.8.8.8
nameserver 10.10.182.225
It seems that the QNetworkAccessManager's get API uses the nameservers sequentially to resolve the given domain name, i.e it tries 8.8.8.8 first, and if it fails it tries 10.10.182.255. Is there some way to make Qt to do this name resolution parallely.
I am no network expert, but it looks like a problem that would better be solved system wise than just by tweaking a single program.
According to Adjusting how long Linux takes to fail over to backup DNS server listed in resolv.conf, you can add this line to resolv.conf:
options timeout:1 attempts:1
This will set the timeout to 1s, switch dns server after first failed attempt.
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.
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.