On 3/12/20 11:00 AM, Fred Morris wrote:
The obvious conclusion (until disproved!) is that "DNS lookups to the
rest of the world are slow" but I wouldn't start there.
I feel like running a network sniffer (tcpdump, Wireshark, etc.) on the
recursive resolver will make it quite apparent where the
To confirm, this is a local caching also-known-as recursive resolver. It
is quick (< 100 msec) when answering from cache, but not when it has to do
lookups itself (> 1000 msec).
On Thu, 12 Mar 2020, ShubhamGoyal wrote:
we made a recurive resolver (Cent OS 7, 8GB RAM ,250 GB Hard disk and net
On 12.03.20 11:54, ShubhamGoyal wrote:
we made a recurive resolver (Cent OS 7, 8GB RAM ,250 GB Hard disk and network
speed is also good ) . It reply in 1200 msec and 1800 msec (which is very
slow). if it gave Reply by Cache (80 msec or 76 msec).
so i want to know about,
How can i improve my rec
Thank you very much sir for replying
we made a recurive resolver (Cent OS 7, 8GB RAM ,250 GB Hard disk and network
speed is also good ) . It reply in 1200 msec and 1800 msec (which is very
slow). if it gave Reply by Cache (80 msec or 76 msec).
so i want to know about,
How can i improve my recur
4 matches
Mail list logo
