Unbound+Adguard do not resolve any .sx domain Topic is solved

Having issues with your DietPi installation or found a bug? Post it here.
tr0ner
Posts: 7
Joined: Thu Sep 09, 2021 8:29 am

Re: Unbound+Adguard do not resolve any .sx domain

Post by tr0ner »

@Joulinar someone reacted to the unbound issue...maybe you can take over because my knowledge is somewhat limited =)
He says that sx domains work fine for him - so maybe it is a problem with the dietpi config after all?
User avatar
Joulinar
Posts: 6525
Joined: Sat Nov 16, 2019 12:49 am

Re: Unbound+Adguard do not resolve any .sx domain

Post by Joulinar »

Hi,

I did a test today and for me this is working now ootb without any hack needed

dig test succeed

Code: Select all

root@DietPi4:~# dig registry.sx @127.0.0.1 -p 53

; <<>> DiG 9.16.15-Debian <<>> registry.sx @127.0.0.1 -p 53
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41766
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;registry.sx.                   IN      A

;; ANSWER SECTION:
registry.sx.            300     IN      A       98.129.229.208

;; Query time: 99 msec
;; SERVER: 127.0.0.1#53(127.0.0.1)
;; WHEN: Thu Oct 21 10:44:28 CEST 2021
;; MSG SIZE  rcvd: 56

root@DietPi4:~#
As well tcpdump shows no issues

Code: Select all

root@DietPi4:~# tcpdump -i any -c200 -nn port 53
tcpdump: data link type LINUX_SLL2
tcpdump: verbose output suppressed, use -v[v]... for full protocol decode
listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
10:44:28.574748 lo    In  IP 127.0.0.1.59160 > 127.0.0.1.53: 41766+ [1au] A? registry.sx. (52)
10:44:28.575112 eth0  Out IP 192.168.0.17.20658 > 192.58.128.30.53: 63813% [1au] A? Sx. (31)
10:44:28.593544 eth0  In  IP 192.58.128.30.53 > 192.168.0.17.20658: 63813- 0/4/5 (493)
10:44:28.593796 eth0  Out IP 192.168.0.17.11200 > 185.159.197.10.53: 55525% [1au] A? RegISTrY.sx. (40)
10:44:28.593908 eth0  Out IP 192.168.0.17.50555 > 185.159.198.10.53: 55204% [1au] DNSKEY? sX. (31)
10:44:28.613288 eth0  In  IP 185.159.198.10.53 > 192.168.0.17.50555: 55204*- 3/0/1 DNSKEY, DNSKEY, RRSIG (745)
10:44:28.624255 eth0  In  IP 185.159.197.10.53 > 192.168.0.17.11200: 55525*- 2/0/1 A 98.129.229.208, RRSIG (227)
10:44:28.625029 eth0  Out IP 192.168.0.17.63945 > 185.159.198.10.53: 63614% [1au] DS? REgISTRy.Sx. (40)
10:44:28.642515 eth0  In  IP 185.159.198.10.53 > 192.168.0.17.63945: 63614*- 5/0/1 DS, DS, DS, DS, RRSIG (370)
10:44:28.643059 eth0  Out IP 192.168.0.17.51084 > 185.159.197.10.53: 48383% [1au] DNSKEY? reGIstry.SX. (40)
10:44:28.671504 eth0  In  IP 185.159.197.10.53 > 192.168.0.17.51084: 48383*- 4/0/1 DNSKEY, DNSKEY, RRSIG, RRSIG (934)
10:44:28.672025 lo    In  IP 127.0.0.1.53 > 127.0.0.1.59160: 41766$ 1/0/1 A 98.129.229.208 (56)
^C
12 packets captured
16 packets received by filter
0 packets dropped by kernel
root@DietPi4:~#
Pls let us know if a solution is working. This could help others if they hit by similar situation. Your DietPi Team
tr0ner
Posts: 7
Joined: Thu Sep 09, 2021 8:29 am

Re: Unbound+Adguard do not resolve any .sx domain

Post by tr0ner »

You are right - now it works for me too! Maybe it was a cache thing yesterday.
Thank you very much
Post Reply