-
|
I am using the LookupClient with default arguments on Macos Sequoia (15.3.2 (24D81)). It takes about 45 seconds to perform a TXT record lookup for google.com. I am wondering if it might be because there are many interfaces listed on my machine: Do you have any suggestions on how to accelerate the lookup performance for DNS? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
|
Not sure why you have that many interfaces on your machine, but if those are configured with invalid or non-responsive DNS servers, then, yea, it'll take some time to go through all of them and wait for timeouts. That's basically what the client would have to do until it finds a server which returns a response... To fix that, you can define the dns server you want the LookupClient to use, e.g. a public one, 1.1.1.1 |
Beta Was this translation helpful? Give feedback.
Not sure why you have that many interfaces on your machine, but if those are configured with invalid or non-responsive DNS servers, then, yea, it'll take some time to go through all of them and wait for timeouts. That's basically what the client would have to do until it finds a server which returns a response...
To fix that, you can define the dns server you want the LookupClient to use, e.g. a public one, 1.1.1.1
that should give you a reply right away because it doesn't have to go through a long list of DNS servers which probably don't exist.