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
I added 201.11.11.11 example.com to /etc/hosts. Pinging example.com shows that I am pinging the IP, so the hosts configuration is correct and working. But when I used dig example.com on my DNS forwarder it returned 93.184.216.34 (the actual IP of example.com from upstream DNS) instead of the IP inside the hosts file.
Describe the bug
I added
201.11.11.11 example.com
to/etc/hosts
. Pingingexample.com
shows that I am pinging the IP, so the hosts configuration is correct and working. But when I useddig example.com
on my DNS forwarder it returned93.184.216.34
(the actual IP ofexample.com
from upstream DNS) instead of the IP inside the hosts file.To Reproduce
Here is a small snippet:
Expected behavior
As expected, the snippet above prints
Some(...)
with the correct RDataSome(A(A(201.11.11.11)))
.But unexpectedly,
dig @127.0.0.1 -p 8000 example.com
still returned93.184.216.34
. It should be201.11.11.11
.System:
Version:
Crate:
hickory-resolver
/hickory-server
Version: 0.24.0
The text was updated successfully, but these errors were encountered: