How to Reduce DNS Lookups

What is DNS recognition?

reduce DNS stands for Domain Name System, which keeps records relating to domain name maps at any IP address. Where often compared to a phone book in which the names of people match a particular phone number. Specifically, a DNS look is a process of determining which IP a domain name belongs to. This application allows us to use easy-to-use domains such as https://hacksrelease.com while still communicating with the requested data server.

The process for creating DNS views falls into the browser function. When we log in to a web page, the browser finds all the resources that require DNS recognition and we have to wait until the completion of the process is complete before downloading anything. According to YSlow, average DNS uploads take between 20-120 milliseconds to complete.

This article will learn how to reduce DNS delivery to help improve page load times.

Example of looking at DNS

To show an example of how DNS lookup can affect the speed of a web page we will test https://www.keycdn.com via WebPageTest.

In total, 32 applications were made, and of these seven applications required DNS recognition. In total, the DNS check time for these resources took 1.23 seconds. As we can see, the time necessary to complete DNS views can add up quickly, which is why it is essential to know how to reduce DNS delivery to help improve page speed.

How to reduce DNS lookups

Processing to reduce DNS lookups is actually straightforward. Where things get more granular in using the remaining DNS uploads that you can’t do without (we’ll cover that in the next section). However, reducing the number of DNS visits followed the suggestions below:

  1. Reduce the number of catchwords

    Simply reducing the number of keywords used to generate your web page is the most straightforward way. Browse your site and explore the hostname and assets of new application forms.

    For example, when you make external requests to generate social icon buttons, fonts, libraries, etc. All of this requires a DNS view. Determine whether all of these external resources are needed and assess the cost/benefit ratio between external storage resources and overtime loading resulting from this.
  1. Hold third-party services in your area.

    External hosting services allow you to reduce DNS uploads while gaining better control of how the service is delivered more widely. Using this method, you can specify how long an asset should be stored, whether it is provided by CDN, and much more.

    Download files displayed on an external device and host them on your root server or CDN. In this way, resources will be available without additional DNS recognition. Storing them on a CDN will help improve upload times as users will be sent content from the closest edge server. Besides, hosting files on a CDN will help remove the load from the root server.

    This method, however, should not be used in all cases. For example, third-party scripts are often updated, so if you are hosting property in your area or on your CDN, you may not be using high-quality scripts. However, in some cases, there are ways to capture third-party documents and check periodically for updates. Learn more about how to do this in Gravatars, Google Analytics, and font libraries.

Improve the speed of the remaining DNS

Reducing DNS breakage by following the suggestions above is a good step to increase the number of lookups required. However, what about enabling DNS configuration required to host a site. There are many ways to improve these things, including:

  1. Use DNS cache for your benefit

    Thankfully, due to DNS cache DNS storage is not always required when the browser requests an asset. As long as the cache is not expired, the DNS server cache can assign the host’s name to the browser without looking at it. Defining the DNS cache length is what is called TTL or lifetime.

Not all DNS records should be stored equally. It is based on the type of record you are using which should define what its TTL should be. There are no “set” values ​​however the following provide a good basis:

~ CNAME records – 24 hours
~ A and AAAA Records – Anytime between 5 minutes to 1 hour
~ TXT records – 12 hours
~ MX records – 12 hours
Note that in most cases (as in the screen above), TTL values ​​are displayed in seconds instead of minutes or hours, so be sure to make a change before defining the value.

  1. DNS starts selecting

    Use DNS selector to allow the browser to perform DNS uploads in the background while the user is browsing the current page. Therefore, when a user clicks on a particular link for the services used, they will not have to wait for DNS recognition to occur. The image below shows how the first choice works.

DNS pre-configuration is very easy to set up and can be added to your link attributes as follows:

<link rel="dns-prefetch" href="https://www.yourlink.com">
  1. Reduce the number of CNAME Records

    CNAME records generate additional views that create a minimum amount of extra waiting time. Having a few CNAME records is normal and you won’t get much change. However, if your setup has too many CNAME records it may be time to consider deleting a few of your DNS settings. That being said, you can use ANAME records instead of providing the same functionality as the CNAME record, but at the root level. Therefore, instead of the following CNAME record checking process:
www.yourwebsite.com. 43200 IN CNAMEyourwebsite.com.
yourwebsite.com. 43200 IN A 192.1.1.1

The ANAME record will return the following:

www.yourwebsite.com. 43200 IN A 192.1.1.1

In addition, Cloudflare also provides a solution to what they call CNAME Flattening.

  1. See JavaScript filtering

    Specifying the JavaScript split will not speed up your DNS upload; however, it will increase your high content. Visitors will, therefore, begin to see your website uploaded soon, which helps improve visual performance. In addition, JavaScript abuse allows for critical content to be first uploaded and then uploaded to sensitive JS
  1. Use a fast DNS provider.

    Lastly, use a quick DNS provider when looking to add your DNS uploads. Although many DNS providers exist, all created are equal. Check out a complete guide to the top 10 best DNS providers to learn more about what’s available and how they compare. Do your research before making a final decision and do some job tests to compare yourself with your current DNS provider.

Summary

Keeping an eye on and minimizing DNS configuration is essential if you want to increase the performance of your site. With so many third-party services available now, it is easy to install a slifry of external applications that significantly increases the latency of your website visitors. If you receive a recommendation from Google PageSpeed ​​or GTmetrix to reduce DNS downtime, use the suggestions above to help resolve this recommendation and improve your site’s performance.

Leave a Comment