Wait for Propagation<\/strong><\/p>\n\n\n\nDNS updates will take place, or propagate, within the period established by your zone file\u2019s TTL.<\/p>\n\n\n\n
If you\u2019ve just created a DNS modification and aren\u2019t seeing it reflected yet, the new info may not be available for up to 48 hours.<\/p>\n\n\n\n
Whereas you can\u2019t handle DNS caching throughout every point on the Internet, you do have control over your web browser.<\/p>\n\n\n\n
To bypass your browser’s cache of old DNS data, hold down the Shift or Control keys while refreshing the page.<\/p>\n\n\n\n
You can also preview your website without DNS by opening it in a different browser or editing your hosts file.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Set the TTL (Time To Live)<\/strong><\/p>\n\n\n\nTime to Live (TTL) is a DNS parameter that tells internet servers how long to cache specific DNS entries.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Linode domain zone files have a default TTL of 24 hours.<\/strong><\/p>\n\n\n\nAlthough most people do not update their IP addresses frequently, this is fine in most cases.<\/p>\n\n\n\n
Even so, there will be times when you want the TTL to be as low as possible. For example, when you make a DNS change, you’ll want it to propagate quickly.<\/p>\n\n\n\n
Or else, some people would see the new site straight away, while others will continue to visit the old server’s website.<\/p>\n\n\n\n
When it comes to email, lengthy caching times can be far more troublesome, because certain messages would be sent to the new server while others are sent to the old.<\/p>\n\n\n\n
Lowering your TTL before making a DNS change is the solution. Before making any other DNS modifications, you should lower the TTL.<\/p>\n\n\n\n
Here’s a quick rundown about what should take place during a successful DNS update:<\/p>\n\n\n\n
- First, verify the TTL value for the DNS record you’re updating. This may take 24 to 48 hours.<\/li>
- Update the relevant DNS records 48 to 96 hours ahead of time, taking any intermediate DNS servers into account. Reduce the TTL to 5 minutes\/<\/li>
- Then wait for 48 to 96 hours to pass.<\/li>
- To update your IP address and any other, go back to your domain’s DNS records in the Linode Cloud Manager.<\/li>
- At last, the DNS changes must take 30 minutes to propagate.<\/li><\/ol>\n\n\n\n
<\/p>\n\n\n\n
Find Current DNS Information<\/strong><\/p>\n\n\n\nYou may need to look up a domain’s current DNS information on occasion.<\/p>\n\n\n\n
There are two excellent tools for this:<\/p>\n\n\n\n
- dig<\/strong>: Look up individual DNS records. For instance, you can discover the IP address where your domain fixes.<\/li><\/ul>\n\n\n\n
- \u00a0whois<\/strong>: Find your domain’s registrar and nameserver data.<\/li><\/ul>\n\n\n\n
Use these tools from the command line if you’re using a macOS or Linux computer.<\/p>\n\n\n\n
Run the following command to locate your domain’s IP (the primary A record):<\/p>\n\n\n\n
dig example.com<\/code><\/pre>\n\n\n\nTo find your IP address, look in the answer section of the output.<\/p>\n\n\n\n
Other types of records can also be searched for. For instance, to see a domain’s mail records:<\/p>\n\n\n\n
dig mx example.com<\/code><\/pre>\n\n\n\nThis will return all of the MX records for your domain.<\/p>\n\n\n\n
Run the following command to find your domain’s registrar and nameservers data:<\/p>\n\n\n\n
whois example.com<\/code><\/pre>\n\n\n\nThis generates a significant amount of data about the domain.<\/p>\n\n\n\n
You may have to scroll back to see the essential information you require near the top of the output.<\/p>\n\n\n\n
<\/p>\n\n\n\n
Name Resolution Failures<\/strong><\/p>\n\n\n\nWhen an attempt has been made to access the DNS with DNSSEC enabled at your domain’s registrar, name resolution problems such as NXDOMAIN will occur.<\/p>\n\n\n\n
This is because the Linode DNS Manager does not currently support DNSSEC.<\/p>\n\n\n\n
Are you looking for an answer to another query?\u00a0Contact<\/em><\/a>\u00a0our technical support team.<\/p>\n","protected":false},"excerpt":{"rendered":"Looking for a way to fix Linode DNS slow? We can assist you. How to fix Linode DNS slow? While someone attempts to enter a web page, they generally type the site’s name into the browser, such as example.com. The browser doesn’t know about example.com by default, so it asks the computer to look for […]<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[5,362],"tags":[698],"class_list":["post-9422","post","type-post","status-publish","format-standard","hentry","category-blog","category-linode-cloud-management","tag-linode"],"_links":{"self":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/9422","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/comments?post=9422"}],"version-history":[{"count":0,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/posts\/9422\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/media?parent=9422"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/categories?post=9422"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.skynats.com\/blog\/wp-json\/wp\/v2\/tags?post=9422"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}