mirror of
https://github.com/hickory-dns/hickory-dns.git
synced 2026-04-24 18:55:55 +03:00
[GH-ISSUE #3401] DNS response from different IP #1179
Labels
No labels
blocked
breaking-change
bug
bug:critical
bug:tests
cleanup
compliance
compliance
compliance
crate:all
crate:client
crate:native-tls
crate:proto
crate:recursor
crate:resolver
crate:resolver
crate:rustls
crate:server
crate:util
dependencies
docs
duplicate
easy
easy
enhance
enhance
enhance
feature:dns-over-https
feature:dns-over-quic
feature:dns-over-tls
feature:dnsssec
feature:global_lb
feature:mdns
feature:tsig
features:edns
has workaround
ops
perf
platform:WASM
platform:android
platform:fuchsia
platform:linux
platform:macos
platform:windows
pull-request
question
test
tools
tools
trust
unclear
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/hickory-dns#1179
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @greenpsi on GitHub (Dec 15, 2025).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/3401
Describe the bug
I ran hickory-dns on a system with multiple interfaces and multiple IPs per interface.
From another system, I ran drill like this:
drill @fde1:ffec:362f:9f31::1 hickory-dns.org AAAA.drilltimes out after about 10s, with the following error message:fde1:ffec:362f:9f31::1is statically assigned toenp1s0. But the same interface also has multiple ULA and GUA IPv6 addresses assigned via SLAAC.In wireshark, I can see a DNS query from my client where I ran
drilltofde1:ffec:362f:9f31::1and right after that a query response from hickory-dns, but from another ULA IPv6 address (fde1:ffec:362f:9f31:fc43:2ba1:c78d:43ce) on the same interface. This is therefore missed bydrill, so it repeats its request. This whole procedure repeats three times beforedrilltimes out.Hickory logs:
To Reproduce
Used config:
Invoked via
sudo ./hickory-dns --config /path/to/config.tomlExpected behavior
hickory-dns should answer from the same IP address the request was sent to.
System:
Version:
built from commit
53dd4a48f9, usingcargo build --release -p hickory-dns --features recursorCan also reproduce with 0.25.2.