[GH-ISSUE #455] Different dns lookup result for same host #194

New issue

Closed

opened 2026-03-07 22:43:23 +03:00 by kerem · 6 comments

kerem commented

2026-03-07 22:43:23 +03:00

Owner

Originally created by @sintanial on GitHub (May 11, 2018).
Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/455

Sometimes trust_dns_resolver resolve two different result

For example i try to resolve host www.kinopoisk.ru
first result is only ipv6 LookupIp(Lookup { rdatas: [AAAA(2a02:6b8::2:105)] })
after 1 second, i send another request to lookup, and
second result is only ipv4 LookupIp(Lookup { rdatas: [A(87.250.251.105), A(213.180.193.105)] })

Originally created by @sintanial on GitHub (May 11, 2018). Original GitHub issue: https://github.com/hickory-dns/hickory-dns/issues/455 Sometimes trust_dns_resolver resolve two different result For example i try to resolve host ```www.kinopoisk.ru``` first result is only ipv6 ```LookupIp(Lookup { rdatas: [AAAA(2a02:6b8::2:105)] })``` after 1 second, i send another request to lookup, and second result is only ipv4 ```LookupIp(Lookup { rdatas: [A(87.250.251.105), A(213.180.193.105)] })```

kerem

2026-03-07 22:43:23 +03:00

closed this issue
added the
bug

unclear

crate:resolver
labels

kerem commented

2026-03-07 22:43:39 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 11, 2018):

Hm, I wonder is this is related to the other issue you filed. I have seen this before when the upstream Resolver’s Cache hasn’t been warmed, it will sometimes flip like this until it caches both record types.

Do you see this issue continually? Or is it after any prolonged periods?

@bluejekyll commented on GitHub (May 11, 2018): Hm, I wonder is this is related to the other issue you filed. I have seen this before when the upstream Resolver’s Cache hasn’t been warmed, it will sometimes flip like this until it caches both record types. Do you see this issue continually? Or is it after any prolonged periods?

kerem commented

2026-03-07 22:43:44 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 14, 2018):

I'm hoping this is an artifact of #454

@bluejekyll commented on GitHub (May 14, 2018): I'm hoping this is an artifact of #454

kerem commented

2026-03-07 22:43:49 +03:00

Author

Owner

@bluejekyll commented on GitHub (May 20, 2018):

@sintanial, are you still seeing this issue with the new release and other changes?

@bluejekyll commented on GitHub (May 20, 2018): @sintanial, are you still seeing this issue with the new release and other changes?

kerem commented

2026-03-07 22:43:55 +03:00

Author

Owner

@sintanial commented on GitHub (May 31, 2018):

@bluejekyll hello, i will try to test it today and write result ;)

@sintanial commented on GitHub (May 31, 2018): @bluejekyll hello, i will try to test it today and write result ;)

kerem commented

2026-03-07 22:44:00 +03:00

Author

Owner

@sintanial commented on GitHub (Jun 2, 2018):