<!DOCTYPE html>
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
</head>
<body>
<p>Hello,</p>
<p><br>
</p>
<p>I am new to this mailing list but I am a bind user for many years
and have been able to find answers to my problems with internet
search.</p>
<p><br>
</p>
<p>But his time I have a very strange behavior with the
implementation of DoT with BIND 9.20.21.</p>
<p>If I type 'dig +tls @127.0.0.1 google.com A' I get this:</p>
<p>>dig +tls @127.0.0.1 google.com A<br>
<br>
; <<>> DiG 9.20.21-1~deb13u1-Debian <<>>
+tls @127.0.0.1 google.com A<br>
; (1 server found)<br>
;; global options: +cmd<br>
;; Got answer:<br>
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id:
60158<br>
;; flags: qr rd ra; QUERY: 1, ANSWER: 6, AUTHORITY: 0, ADDITIONAL:
1<br>
<br>
;; OPT PSEUDOSECTION:<br>
; EDNS: version: 0, flags:; udp: 1232<br>
; COOKIE: f9d2ab7b838355f70100000069f8ab35798000611d158b1b (good)<br>
;; QUESTION SECTION:<br>
;google.com. IN A<br>
<br>
;; ANSWER SECTION:<br>
google.com. 164 IN A 192.178.204.100<br>
google.com. 164 IN A 192.178.204.113<br>
google.com. 164 IN A 192.178.204.102<br>
google.com. 164 IN A 192.178.204.101<br>
google.com. 164 IN A 192.178.204.138<br>
google.com. 164 IN A 192.178.204.139<br>
<br>
;; Query time: 16 msec<br>
;; SERVER: 127.0.0.1#853(127.0.0.1) (TLS)<br>
;; WHEN: Mon May 04 16:20:37 CEST 2026<br>
;; MSG SIZE rcvd: 163<br>
<br>
But if I type 'dig +tls @192.168.10.205 google.com A' i get:</p>
<p>>dig +tls @192.168.10.205 google.com A<br>
;; communications error to 192.168.10.205#853: end of file<br>
;; communications error to 192.168.10.205#853: end of file<br>
;; communications error to 192.168.10.205#853: end of file<br>
<br>
; <<>> DiG 9.20.21-1~deb13u1-Debian <<>>
+tls @192.168.10.205 google.com A<br>
; (1 server found)<br>
;; global options: +cmd<br>
;; no servers could be reached<br>
</p>
<p><br>
</p>
<p>It's like if the configuration I set for DoT would answer only on
the loopback interface, however, my configuration is:</p>
<p> listen-on-v6 { none; };<br>
listen-on { 127.0.0.1; 192.168.10.205; };<br>
listen-on port 53 { 127.0.0.1; 192.168.10.205; };<br>
listen-on port 853 tls mytls { 127.0.0.1; 192.168.10.205; };<br>
listen-on port 8053 tls mytls http myhttp { 127.0.0.1;
192.168.10.205; };</p>
<p><br>
</p>
<p>If I use the same queries for port 53 I have the same issue, the
local IP address of my server is never available, only the
loopback interface.</p>
<p><br>
</p>
<p><br>
</p>
<p>Does anyone have a clue on this?</p>
<p>Thanks for your answers</p>
</body>
</html>