# orderedItems[].object.content
I'm experimenting with DNS security this weekend. While plaintext DNS over 53/udp is still ubiquitous, there are two decent options that have been developed to provide security of that data in transit: DNS-over-TLS and DNS-over-HTTPS.

The latter is likely the more widely used; modern browsers have the capability to specify DNS-over-HTTPS and natively circumvent a potentially insecure local resolver. DNS-over-TLS is older (as I understand it) and I've found support more rare. But I have been able to use it on Android with a manual setting.

I've added #DoT and #DoH capabilities to my WIP VPP-native #dnsd caching recursor. I also added the ability for the daemon to seamlessly request and provision TLS certificates from LetsEncrypt using #TLSALPN01. No messing around with DNS records or secondary HTTP servers - just set some configuration options and a public address and it handles the rest.

So far I have the software serving my Firefox browsers using DoH, my Android phone using DoT, and my Windows laptop at a system level using DoH. I thought my Macs would be the easiest because they generally have been about #IPv6 and RAs. But from what I can see, they have some outdated requirements for automatic provisioning (i.e., providing the TLS domain name in the message isn't enough; TLS also needs to include SAN records for the IP addresses) that have proven intractable so far with my tech stack. To be fair, none of the other systems configure this automatically either. But I have come to expect more from my Macs.

Regardless, I added several record types in sfw and dhcpd to facilitate automatic assignment when the systems support it.

> dnsd-query stats

{
  "type": "stats",
  "queries_udp": 644,
  "queries_tcp": 0,
  "queries_dot": 76,
  "queries_doh": 188,
  "cache_hits": 127,
  "cache_misses": 775,
  "forwarder_matched": 0,
  "recursion_walked": 534,
  "rrl_dropped": 0,
  "acl_denied": 0,
  "dns64_synthesised": 100,
  "dnssec_validated": 64,
  "dnssec_failed": 0,
  "udp_inflight_shed": 0
}

# orderedItems[].object.source.content
I'm experimenting with DNS security this weekend. While plaintext DNS over 53/udp is still ubiquitous, there are two decent options that have been developed to provide security of that data in transit: DNS-over-TLS and DNS-over-HTTPS.

The latter is likely the more widely used; modern browsers have the capability to specify DNS-over-HTTPS and natively circumvent a potentially insecure local resolver. DNS-over-TLS is older (as I understand it) and I've found support more rare. But I have been able to use it on Android with a manual setting.

I've added #DoT and #DoH capabilities to my WIP VPP-native #dnsd [caching recursor](https://github.com/justindthomas/dnsd). I also added the ability for the daemon to seamlessly request and provision TLS certificates from LetsEncrypt using #TLSALPN01. No messing around with DNS records or secondary HTTP servers - just set some configuration options and a public address and it handles the rest.

So far I have the software serving my Firefox browsers using DoH, my Android phone using DoT, and my Windows laptop at a system level using DoH. I thought my Macs would be the easiest because they generally have been about #IPv6 and RAs. But from what I can see, they have some outdated requirements for automatic provisioning (i.e., providing the TLS domain name in the message isn't enough; TLS also needs to include SAN records for the IP addresses) that have proven intractable so far with my tech stack. To be fair, none of the other systems configure this automatically either. But I have come to expect more from my Macs.

Regardless, I added several record types in [sfw](https://github.com/justindthomas/sfw) and [dhcpd](https://github.com/justindthomas/dhcpd) to facilitate automatic assignment when the systems support it.

```
> dnsd-query stats

{
  "type": "stats",
  "queries_udp": 644,
  "queries_tcp": 0,
  "queries_dot": 76,
  "queries_doh": 188,
  "cache_hits": 127,
  "cache_misses": 775,
  "forwarder_matched": 0,
  "recursion_walked": 534,
  "rrl_dropped": 0,
  "acl_denied": 0,
  "dns64_synthesised": 100,
  "dnssec_validated": 64,
  "dnssec_failed": 0,
  "udp_inflight_shed": 0
}

```

# orderedItems[].object.content
DNS over TLS with LetsEncrypt

https://blog.hardill.me.uk/2025/12/06/dns-over-tls-with-letsencrypt/

6 months ago LetsEncrypt announced that they would start issuing certificates for IP addresses. Last week I was curious if they had actually enabled it yet for general consumption, it turned out to be not yet available for everybody, but there was a forum thread you could ask to be added to the testing list (I’ve not linked to it as they have said no more testing, it will go live RSN).

When it […]

#certificates #DNS #DoT #letsencrypt

# orderedItems[].object.ephemeral.metadata[].ogDescription
6 months ago LetsEncrypt announced that they would start issuing certificates for IP addresses. Last week I was curious if they had actually enabled it yet for general consumption, it turned out to…

# orderedItems[].object.content
India Enforces Mandatory SIM-Binding for Messaging Apps Under New DoT Rules https://thecyberexpress.com/sim-bindin g-dot-rule/ #TheCyberExpressNews #IndiaCybersecurity #TheCyberExpress #FirewallDaily #Vulnerability #Regulations #Compliance #CyberFraud #SIMbinding #CyberNews #COAI #DoT

# orderedItems[].object.ephemeral.metadata[].twitterTitle
DoT Enforces SIM-Binding To Curb Messaging App Cyber Fraud

# orderedItems[].object.ephemeral.metadata[].description
India mandates SIM-Binding for messaging apps to strengthen cybersecurity compliance, close identity gaps, and reducing cyber fraud nationwide.

# orderedItems[].object.ephemeral.metadata[].ogDescription
India mandates SIM-Binding for messaging apps to strengthen cybersecurity compliance, close identity gaps, and reducing cyber fraud nationwide.

# orderedItems[].object.ephemeral.metadata[].ogTitle
DoT Enforces SIM-Binding To Curb Messaging App Cyber Fraud

# orderedItems[].object.ephemeral.metadata[].twitterDescription
India mandates SIM-Binding for messaging apps to strengthen cybersecurity compliance, close identity gaps, and reducing cyber fraud nationwide.

# orderedItems[].object.content
Using #Unbound over #DoT (DNS over TLS) as a local DNS resolver.

Example setup on #Debian - of course not limited to #Debian - any distro or #BSD will do! 😎

#linux #unbound #foss #ubuntu

https://jhx7.de/blog/using-unbound/

# orderedItems[].object.ephemeral.metadata[].description
We all know that DNS is the lifeblood of the modern Internet. 
But, we also all know that resolving DNS queries can take some time and by default queries are sent unencrypted to a outside DNS server - if one does not selfhost DNS of course.
In this little post I set up Unbound with DoT. Also, Unbound will cache results which makes queries faster in the future (Since these don’t need to be resolved again)

# orderedItems[].object.ephemeral.metadata[].ogDescription
We all know that DNS is the lifeblood of the modern Internet. But, we also all know that resolving DNS queries can take some time and by default queries are sent unencrypted to a outside DNS server - if one does not selfhost DNS of course.
In this little post I set up Unbound with DoT. Also, Unbound will cache results which makes queries faster in the future (Since these don’t need to be resolved again)

# orderedItems[].object.ephemeral.metadata[].twitterDescription
We all know that DNS is the lifeblood of the modern Internet. But, we also all know that resolving DNS queries can take some time and by default queries are sent unencrypted to a outside DNS server - if one does not selfhost DNS of course.
In this little post I set up Unbound with DoT. Also, Unbound will cache results which makes queries faster in the future (Since these don’t need to be resolved again)

# orderedItems[].object.content
Discover dot matrix printers: history, features, pros, cons, and uses. Learn why they still matter in banking, retail, and logistics.

https://printersfy.com/dot-matrix-prin ter/

#dot #matrix #printers #tech

# orderedItems[].object.ephemeral.metadata[].twitterTitle
What Is a Dot Matrix Printer? History, Components, How It Works, Types, Pros and Cons - Printersfy

# orderedItems[].object.ephemeral.metadata[].description
Discover dot matrix printers: history, features, pros, cons, and uses. Learn why they still matter in banking, retail, and logistics.

# orderedItems[].object.ephemeral.metadata[].ogDescription
Discover dot matrix printers: history, features, pros, cons, and uses. Learn why they still matter in banking, retail, and logistics.

# orderedItems[].object.ephemeral.metadata[].ogTitle
What Is a Dot Matrix Printer? History, Components, How It Works, Types, Pros and Cons - Printersfy

# orderedItems[].object.ephemeral.metadata[].twitterDescription
Discover dot matrix printers: history, features, pros, cons, and uses. Learn why they still matter in banking, retail, and logistics.

# orderedItems[].object.content
This cool trick (some would call it "dirty hack" 🙂) by @plantarum can be used for #dot﻿/﻿#graphviz, as well:

(defun my-babel-execute-maybe ()
(interactive)
(org-mode)
(org-babel-execute-maybe)
(org-display-inline-images)
(normal-mode))

E.g. imagine this comment or doc string:

/*
#+BEGIN_SRC dot :file myfunction.svg :cmdline -Kdot -Tsvg
digraph {
a -> b;
}
#+END_SRC
*/

#elisp #Emacs #orgmode

# orderedItems[].object.content
This is fascinating, the Computer Devices' DOT, the a portable that was the first computer to ship with Sony 3.5-inch disk drives and it had a *widescreen* CRT display (which supported 132x25 textmode!).

And the video ... has some surprises...

Well worth a watch.

https://www. youtube.com/watch?v=AR5i9BnJql A

#DOT #vintagecomputing #retrocomputing #retrocomputers #computinghistory #computers #CRT #floppydisk #vintage #vintagetech #tech #video

# orderedItems[].object.ephemeral.metadata[].twitterTitle
Widescreen CRT PC Portable - Computer Devices Dot from 1983

# orderedItems[].object.ephemeral.metadata[].description
The Computer Devices Dot was an extremely forward looking computer. Widescreen display, 3.5in floppy drives, and portable. But the market wasn't ready for it...

# orderedItems[].object.ephemeral.metadata[].ogDescription
The Computer Devices Dot was an extremely forward looking computer. Widescreen display, 3.5in floppy drives, and portable. But the market wasn't ready for it...

# orderedItems[].object.ephemeral.metadata[].ogTitle
Widescreen CRT PC Portable - Computer Devices Dot from 1983

# orderedItems[].object.ephemeral.metadata[].twitterDescription
The Computer Devices Dot was an extremely forward looking computer. Widescreen display, 3.5in floppy drives, and portable. But the market wasn't ready for it...

# orderedItems[].object.content
Zig's dot star syntax (value.*) — https://www. openmymind.net/Zig-Dot-Star-Sy ntax/
#HackerNews #Zig #Dot #Star #Syntax #Zig #Programming #Language #Programming #Syntax #Tech #News

# orderedItems[].object.ephemeral.metadata[].description
Karl Seguin's Blog - A mix of coding and creative writing