zoonderkins / blahdns

A small hobby ads block dns project with doh, dot, dnscrypt support.
https://blahdns.com
GNU Affero General Public License v3.0
428 stars 24 forks source link

🐛 Stange Stubby behaviour #250

Open daemonserj opened 2 years ago

daemonserj commented 2 years ago

Checklist

Describe the issue Strange behaviour using Stubby 0.3 on OpenWRT 19.07 While executing 3 times getdns_query -d @127.0.0.1:5453 www.snbforums.com | grep address_data I've got 3 different results: only ipv4 addresses, only ipv6 addresses and both.

root@OpenWrt:~# getdns_query -d @127.0.0.1:5453 www.snbforums.com | grep address_data
      "address_data": <bindata for 104.26.8.66>,
      "address_data": <bindata for 104.26.9.66>,
      "address_data": <bindata for 172.67.69.81>,
root@OpenWrt:~#
root@OpenWrt:~# getdns_query -d @127.0.0.1:5453 www.snbforums.com | grep address_data
      "address_data": <bindata for 2606:4700:20::681a:842>,
      "address_data": <bindata for 2606:4700:20::681a:942>,
      "address_data": <bindata for 2606:4700:20::ac43:4551>,
root@OpenWrt:~#
root@OpenWrt:~# getdns_query -d @127.0.0.1:5453 www.snbforums.com | grep address_data
      "address_data": <bindata for 2606:4700:20::681a:842>,
      "address_data": <bindata for 2606:4700:20::681a:942>,
      "address_data": <bindata for 2606:4700:20::ac43:4551>,
      "address_data": <bindata for 104.26.8.66>,
      "address_data": <bindata for 104.26.9.66>,
      "address_data": <bindata for 172.67.69.81>,

Replacing Stubby Blahdns config by default Cloudflare config solve the problem and results are the same: both ipv4+ipv6 addresses. I am not sure that it is Blahdns issue but I can't explain why it's happened.

Here is Blahdns config: stubby.zip

To Reproduce Steps to reproduce the behavior:

  1. Configure stubby 0.3
  2. Exec in router's commandline: getdns_query -d @127.0.0.1:5453 www.snbforums.com | grep address_data

Expected behavior Same DNS responce

zoonderkins commented 2 years ago

Okay, let me check it.

zoonderkins commented 2 years ago

Ya, I can reproduce this issue. However, maybe you can add tls_port to resolve this issue or disable edns0 I need some time to figure out what cause this wired issue.

- address_data: 45.91.92.121
  tls_auth_name: "dot-ch.blahdns.com"
  tls_port: 853

Thanks