came across this. So whatever ip address has the longest colored lines, is the best for your system?
Ever run DNS Benchmark?
- Thread starter daves66nova
- Start date
- Status
What is your question ? Yes, I run DNS benchmarks at my company all the time, but its generally for internal systems. We just use standard Unix / Linux tools, pipe to a log file , then parse out what we are looking for.
I want to change the dns from my computer to a different one, to see if it'll improve my internet speed a bit
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
Originally Posted by javacontour
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
I believe the OP is the latter. We get about a thread a month about some optimization he's tried and/or other similar event from which he needs to recover.
I sure hope he's not in charge of a large corporate IT infrastructure.
Originally Posted by rubberchicken
Originally Posted by javacontour
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
I sure hope he's not in charge of a large corporate IT infrastructure.
Originally Posted by rubberchicken
Originally Posted by javacontour
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
Originally Posted by javacontour
I believe the OP is the latter. We get about a thread a month about some optimization he's tried and/or other similar event from which he needs to recover.
I sure hope he's not in charge of a large corporate IT infrastructure.
Originally Posted by rubberchicken
Originally Posted by javacontour
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
No, not trying to "recover" from anything, just asking to find out if it's worth changing this.
I believe the OP is the latter. We get about a thread a month about some optimization he's tried and/or other similar event from which he needs to recover.
I sure hope he's not in charge of a large corporate IT infrastructure.
Originally Posted by rubberchicken
Originally Posted by javacontour
DNS resolution is such a small part of your network. Your computer should cache any answers it gets for a period of time, so this is a solution looking for a problem to solve for most people.
It's like trying to speed up your phone calls by getting a faster phone book. Looking up the number is a small part of the whole event. Much like a DNS lookup is a very small part of visiting a web page or other internet site.
I think this is one of those "it depends" issues. If your running a large corporate intranet, and many critical applications rely on DNS, then routine benchmarking is desirable. IMO its not so much the speed of one flavor / product over another, as it is the reliability. Failed DNS calls can drive you crazy trying to troubleshoot and resolve. If your just on your home PC then I do not even bother.
No, not trying to "recover" from anything, just asking to find out if it's worth changing this.
Use this:
https://www.filecroco.com/download-dns-jumper/
It made a recognizable positive difference on all our home computers. Everything is a bit faster.
https://www.filecroco.com/download-dns-jumper/
It made a recognizable positive difference on all our home computers. Everything is a bit faster.
javacontour said:
Originally Posted by Lubener
Originally Posted by eljefino
If you find a "good" DNS, will you check again in 3 months to see if there's a better one?
Check it the next day and a faster one is often found.
Exactly, which is why such optimizations are largely fruitless for individual computers.
If you are running corporate IT, why would you be recommending any DNS server but ones you control? Any others and you are at the mercy of the security of others. I do realize DNS is distributed and anyone who is an authority for a domain can be compromised. My point is if you are going to others to do the resolving for your users, when you can be resolving and caching those values, you may be exposing your users to unneeded risk.
But for the home user, your ISP, Google, or whomever you trust is probably good enough. Your device should be caching the values learned for the time the SOA record allows the answer be cached.
Originally Posted by eljefino
If you find a "good" DNS, will you check again in 3 months to see if there's a better one?
Check it the next day and a faster one is often found.
Exactly, which is why such optimizations are largely fruitless for individual computers.
If you are running corporate IT, why would you be recommending any DNS server but ones you control? Any others and you are at the mercy of the security of others. I do realize DNS is distributed and anyone who is an authority for a domain can be compromised. My point is if you are going to others to do the resolving for your users, when you can be resolving and caching those values, you may be exposing your users to unneeded risk.
But for the home user, your ISP, Google, or whomever you trust is probably good enough. Your device should be caching the values learned for the time the SOA record allows the answer be cached.
- Status
