You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Doing multiple DNS queries per request might be pretty expensive, depending where the next caching DNS resolver is that the resolver talks to, which might be 8.8.8.8. Multiple queries, because A and AAAA usually have to be queries for domains.
The text was updated successfully, but these errors were encountered:
clue
changed the title
Connector should use a caching DNS resolver by default
[Client] Connector should use a caching DNS resolver by default
Sep 12, 2017
Thanks for filing this ticket, I think you're raising a very good issue here 👍
It's a very common setup to connect to the same host over and over again, so I agree that it makes perfect sense to keep a small cache of recent DNS records in memory. However, the default cached resolver does currently not limit the number of cache entries, which is why I've just created reactphp/dns#82 which would need to be implemented first.
(Note that this is not really related to IPv6 addresses (AAAA records), I've just created #116 to keep track of this.)
Doing multiple DNS queries per request might be pretty expensive, depending where the next caching DNS resolver is that the resolver talks to, which might be
8.8.8.8
. Multiple queries, becauseA
andAAAA
usually have to be queries for domains.The text was updated successfully, but these errors were encountered: