-
Notifications
You must be signed in to change notification settings - Fork 1.1k
Document DNS cache bypass limitation for resolution_family #5558
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: v3.0
Are you sure you want to change the base?
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
|
|
@@ -959,6 +959,10 @@ char * MySQL_Connection::connect_start_DNS_lookup() { | |
| host_ip = connected_host_details.ip; | ||
| } | ||
| else { | ||
| // NOTE: DNS cache miss — hostname is passed directly to | ||
| // mysql_real_connect which resolves via the MariaDB client library | ||
| // using AF_UNSPEC. The mysql-resolution_family setting does NOT | ||
| // apply here; it only governs the DNS cache resolver thread. | ||
|
Comment on lines
+962
to
+965
|
||
| host_ip = parent->address; | ||
| } | ||
| return host_ip; | ||
|
|
||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The comment states that
mysql-resolution_familygoverns the DNS cache resolver thread. However, the implementation ofmonitor_dns_resolver_threadinlib/MySQL_Monitor.cppappears to use a hardcodedAF_UNSPECfor the address family:This makes the comment potentially misleading as it suggests
mysql-resolution_familyis being used by the resolver thread when it is not. To avoid confusion, the comment should be updated to accurately reflect the current implementation.