Open 1q23lyc45 opened 2 days ago
Maybe you can't reproduce it there, but this problem does exist. You can rename resolv.conf to resolv.conf.bak and you will find that curl can still resolve domain names, and the resolution is not 8.8.8.8 but the carrier DNS.
Problem description
I changed resolv.conf, but it only works in dig and nslookup, not in curl. Let's look directly at the following:
What steps will reproduce the bug?
Just curl any domain name.
What is the expected behavior?
The DNS modified in resolv.conf must be applied to curl
System information