For Window’s clients, you might want to try out this freeware GRC tool for benchmarking DNS performance: https://www.grc.com/dns/benchmark.htm Cheers -- Yonatan (Yoni) Radzin yradzin@gmail.com
On Sep 26, 2018, at 3:59 AM, Michael Bullut <main@kipsang.com> wrote:
Hi Ross,
How would you gauge good DNS performance?
Warm regards,
Michael.
On Wed, 26 Sep 2018 at 10:50, Ross Tajvar <ross@tajvar.io> wrote: Do note that ping response times are not a good indicator of DNS performance.
On Wed, Sep 26, 2018, 3:48 AM Michael Bullut <main@kipsang.com> wrote: Greetings Team,
Has anyone deployed the aforementioned in your individual networks? A quick test suggests it is quite fast compared with Google's D.N.S. resolvers:
C:\Users\bullutm>ping 1.1.1.1
Pinging 1.1.1.1 with 32 bytes of data: Reply from 1.1.1.1: bytes=32 time=3ms TTL=61 Reply from 1.1.1.1: bytes=32 time=4ms TTL=61 Reply from 1.1.1.1: bytes=32 time=8ms TTL=61 Reply from 1.1.1.1: bytes=32 time=4ms TTL=61
Ping statistics for 1.1.1.1: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 3ms, Maximum = 8ms, Average = 4ms
C:\Users\bullutm>
-------
C:\Users\bullutm>tracert 1.1.1.1
Tracing route to one.one.one.one [1.1.1.1] over a maximum of 30 hops:
1 4 ms 3 ms 4 ms 10.101.129.254 2 6 ms 20 ms 7 ms 10.98.0.165 3 7 ms 13 ms 15 ms 10.98.0.233 4 7 ms 5 ms 4 ms one.one.one.one [1.1.1.1]
Trace complete.
C:\Users\bullutm>
Warm regards,
Michael Bullut.
---
Cell: +254 723 393 114. Skype Name: Michael Bullut. Twitter: @Kipsang Blog: http://www.kipsang.com/ E-mail: main@kipsang.com
---