• Introducing WebPros Cloud - a fully managed infrastructure platform purpose-built to simplify the deployment of WebPros products !  WebPros Cloud enables you to easily deliver WebPros solutions — without the complexity of managing the infrastructure.
    Join the pilot program today!
  • Support for BIND DNS has been removed from Plesk for Windows due to security and maintenance risks.
    If a Plesk for Windows server is still using BIND, the upgrade to Plesk Obsidian 18.0.70 will be unavailable until the administrator switches the DNS server to Microsoft DNS.

Recursive Lookups

B

bjsteiger

Guest
I went to DNSStuff.com and did a DNS Timing of my server. There is only one domain on my server and no traffic because I have yet to launch this publically.

I get the following report:

Looking up at ns1.cafeinsomnia.net.... Reports 1 A record(s). 9ms.
Looking up at ns2.cafeinsomnia.net.... Reports 1 A record(s). 8ms.


Average of all 2 nameservers: 8ms (plus 132ms overhead).

Score: A

Took off 3 points for ".net" TLD (extra lookups may be required to find the parent servers).
Took off 2 points since ns1.cafeinsomnia.net allows recursive lookups (if lots of people are using the server, it can slow down).
Took off 2 points since ns2.cafeinsomnia.net allows recursive lookups (if lots of people are using the server, it can slow down).

Note: The 132ms overhead is the time it takes to get your NS records from the parent servers, and indicates a worst-case scenario (normally, the resolving DNS server would have the common parent server entries cached, and would know the parent server(s) that were responding most quickly).

I am a newbie to all of this, so what does the Recursive Lookup mean and how do I fix this?

Thank you,
bjs
 
Back
Top