Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
docker_notes:docker-dns [2024-08-31 Sat wk35 13:28] – [Testing DNS] baumkpdocker_notes:docker-dns [2024-08-31 Sat wk35 17:03] (current) – [Testing DNS] baumkp
Line 132: Line 132:
 DNS over TLS encrypts the DNS data so others can not see the specific DNS query and response.  DNSSEC does not prevent viewing of the DNS data, but rather ensure prevent man in the middle attacks. DNS over TLS encrypts the DNS data so others can not see the specific DNS query and response.  DNSSEC does not prevent viewing of the DNS data, but rather ensure prevent man in the middle attacks.
  
-It looks like Bind9 is still working on support for DNS over TLS (DoT). It may work on the current developer release 9.19. +It looks like Bind9 is still working on support for DNS over TLS (DoT) for forwarders. It may work on the current developer release 9.19. 
  
   *quad9 TLS config data:   *quad9 TLS config data:
Line 162: Line 162:
     *''host -t A mail.kptree.net 9.9.9.9'' - remote address to local hosted external services via an external name server     *''host -t A mail.kptree.net 9.9.9.9'' - remote address to local hosted external services via an external name server
   *Using ''delv'':   *Using ''delv'':
-    *''delv @ns2.local.kptree.net ns1.local.kptree.net'' +    *''delv @ns2.local.kptree.net ns1.local.kptree.net'' - if both local name servers are running to cross check 
-    *''delv @ns1.local.kptree.net ns2.local.kptree.net'' +    *''delv @ns1.local.kptree.net ns2.local.kptree.net'' - if both local name servers are running to cross check 
-    *+    *''delv @ns2.local.kptree.net google.com''  - an external services via local name server 
 +    *''delv @1.1.1.1 mail.kptree.net'' - remote address to local hosted external services via an external name server 
 +  *Using ''dig'': 
 +    *''dig @ns2.local.kptree.net -p 53 ns1.local.kptree.net any'' 
 +    *''dig @ns2.local.kptree.net -p 53 kptree.net any'' 
 +    *''dig @ns2.local.kptree.net -tAXFR  kptree.net'' gave me the full name list from ns2.local.kptree.net 
 +    *''dig @ns1.local.kptree.net -tAXFR  kptree.net'' gave me the full name list from ns1.local.kptree.net  
 +      *Note that bind9 needs to be setup to allow-transfer from the requesting ip address, I include my LAN address range in the bind9 acl. 
 + 
 +\\ 
 +To find the version of bind9 used, anywhere from the LAN: 
 +  *''nslookup -q=txt -class=CHAOS version.bind ns1.local.kptree.net'' 
 +  *''dig -t txt -c chaos VERSION.BIND @ns1.local.kptree.net''
 =====References===== =====References=====
    *KPTree.net's bare metal implementation of [[linux_router:dns_dhcp|dns - dhcp]], based upon ISC Bind9 and DHCP on Debian 10 <fs xx-small>(was originally Ubuntu)</fs>.    *KPTree.net's bare metal implementation of [[linux_router:dns_dhcp|dns - dhcp]], based upon ISC Bind9 and DHCP on Debian 10 <fs xx-small>(was originally Ubuntu)</fs>.