Skip to content
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

vsock_proxy: Use system-configured nameservers for DNS resolution #622

Merged
merged 1 commit into from
Jun 3, 2024

Conversation

meerd
Copy link
Contributor

@meerd meerd commented May 30, 2024

Description of changes:

This commit changes the DNS resolver's initialization to use the system's configured nameservers instead of the default nameserver provided by hickoery-resolver crate.

The Resolver::from_system_conf() method is now used to initialize the DNS resolver. This method attempts to read the system's nameserver configuration, which may come from various sources such as /etc/resolv.conf.

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

This commit changes the DNS resolver's initialization to use the system's
configured nameservers instead of the default nameserver provided by
hickoery-resolver crate.

The `Resolver::from_system_conf()` method is now used to initialize the
DNS resolver. This method attempts to read the system's nameserver
configuration, which may come from various sources such as
`/etc/resolv.conf`.

Signed-off-by: Erdem MEYDANLI <[email protected]>
@meerd meerd marked this pull request as draft May 30, 2024 13:32
@meerd meerd requested a review from eugkoira June 2, 2024 08:16
@meerd meerd marked this pull request as ready for review June 2, 2024 08:16
@meerd meerd merged commit e248e75 into aws:main Jun 3, 2024
9 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants