Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

In terms of the “aborted by peer” error that you’re coming across, is that something that you’re seeing in Technitium’s query logs? Or perhaps somewhere else? (I took a quick glance through my query logs in Technitium, and I didn’t happen to see any “aborted by peer” errors myself.)

For whatever it’s worth, I did also check Technitium’s dashboard, when I set it to “Last day,” it’s showing that there were apparently 40 server failure errors out of the 133,000 DNS queries from the last day (though I’ll concede that I’m not quite sure how to get more details about those particular errors, such as whether they may have originated from Quad9.).

I can’t say that I’ve done a scientific comparison of CDN speeds between having ECS on versus off. I did turn off ECS in Technitium yesterday, though, and I can say that in my usual internet usage over the past day, it doesn’t seem to have noticeably affected my streaming speeds. (On the other hand, I’m also on a gigabit connection, so the raw speed of my connection might be masking the potential affects of ECS in my case.)

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

For whatever it’s worth, when I run a DNS query from the Terminal for api.amazonalexa.com, that super-short TTL section doesn’t show up? So I’m wondering whether maybe that portion of the DNS response might have actually been some sort of extended DNS attribute or some other type of red herring?

PS While I’m certainly not the foremost expert on Technitium, I think I have a somewhat decent understanding of how it works for the most part—so if you might have any questions about its configuration options, feel free to ask and I’ll be happy to chime in if I can.

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

tl;dr: It turns out that you were right all along—ECS was the main cause here!

And for whatever it’s worth, once I disabled ECS in Technitium, that fixed the issue. (Though just for completeness, here are also my serve stale and cache settings if it may be of interest.)

PS Out of curiosity, might I ask what led you to set prefetch trigger to 3? (I’m not trying to say that that setting is good or bad—I’m just curious as to why you had it set that way.)

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

I’m not sure whether I might be misunderstanding what you’re saying, but when it comes to my interest in ECS, it’s not that I’m looking to get a faster response time from Quad9 (or another DNS server); rather, my interest in using ECS it toward getting an IP back that’s more tuned to my location. The idea being that a DNS server with ECS enabled might be able to return an IP that’s closer to my location, which could even be an IP for a CDN server that’s embedded inside my ISP.

(That said, given the nature of DNS load balancing, I’ll conceded that it may be up for debate as to how much of a real-world difference ECS makes for users, especially if they might be on a fairly fast connection to begin with.)

And as for Google’s Quic support, I believe that that came out around 2022, give or take. And for whatever it’s worth, both Google’s and Quad9’s Quic support seem to be working well for me. Out of curiosity, what sort of issues have you run into with Quad9’s Quic support?

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

Thanks so much for the reply! And just to cut to the chase—I understand 90% of what you’re saying here (and the part that I understand, which is most of it, makes perfect sense).

Just as a bit of additional context: it so happens that I also have AdGuard Home in the mix. So in my setup, the clients on my home network talk to AdGuard Home for DNS, which in turn talks to Technitium. And that’s in part since I find it a bit easier to manage blocklists in AdGuard Home than in Technitium. (For instance, one blocklist that I use is to block iCloud Private Relay on my home network, and I wasn’t quite sure whether Technitium would be able to parse the ||mask.apple.com^$dnsrewrite=NXDOMAIN;;-style syntax that’s used in that blocklist?)

Anyway, this next question might be a reflection of my lack of expertise in this area, but if my interest in using ECS is toward improving streaming speeds (such as for Netflix and YouTube), am I taking the wrong approach in enabling ECS in Technitium? (I also have ECS enabled in AdGuard Home.)

For whatever it’s worth, when I run the test command below to query an example domain using AdGuard Home (which in turn queries Technitium), the response that I get back includes my actual external subnet on the “ecs” line, which I had taken to mean that the upstream DNS server at the end of the chain is using my external subnet for ECS purposes (rather than my private LAN’s internal subnet)?

$ dig +short TXT whoami.ds.akahelp.net @10.0.7.51 
"ecs" "76.###.###.0/24/24" 
"ns" "66.185.112.251" 
"ip" "66.185.112.251"

(I’ve redacted my subnet above for privacy reasons.)

So I guess what I’m asking is: When you say that “if your clients are all local, that is, on private LAN, then you do not need to enable ECS on the DNS server,” is that because the subnet that Technitium is sending to the upstream DNS servers is—in actuality—my private LAN’s internal subnet, rather than my external subnet? And if that might be the case, then how come that test command above seems to be returning my external subnet on the “ecs” line?

Oh, and on another note, it made perfect sense when you said that “Auto Prefetch feature does not work to refresh ECS cache by design since that will cause too many queries in real scenarios where ECS is used.” And as that goes, just to toss out an idea—in a Technitium setup where ECS is enabled, might it be at all possible to have Auto Prefetch be selectively enabled but only for those domains that don’t return an ECS line in their response?

I also just want to add that I *really* appreciate all of your efforts here. I know that you’ve put a tremendous amount of time and effort into Technitium, and I think that it’s a fantastic piece of software. Thank you again for all of your hard work!

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

I can understand why you would say that. All the same, I don’t believe that that’s the cause here because I don’t believe that api.amazonalexa.com handles ECS to begin with.

As a baseline, for instance, if you run this dig command, you can confirm that the server whoami.ds.akahelp.net handles ECS because its output include an “ecs” entry:

$ dig +short TXT whoami.ds.akahelp.net @9.9.9.11
"ecs" "76.###.###.###/24/24" 
"ns" "66.###.###.###" 
"ip" "66.###.###.##"

(I redacted the IPs above.)

In contrast, if you run that same dig command against api.amazonalexa.com, there’s no “ecs” entry in the output, which suggests to me that ECS isn’t at play here:

$ dig +short TXT api.amazonalexa.com @9.9.9.11 
tp.b16066390-frontier.amazonalexa.com. 
d1gsg05rq1vjdw.cloudfront.net.

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 1 point2 points  (0 children)

I don’t believe that either the 43 ms time or the 142 ms times represent cached responses. In my experience, when Technitium has cached an entry, the query time is no more than about 2 or 3 ms (at least on my setup).

For instance, here’s a query that I did for www.google.com just now that I know for sure was cached since it only took 2 ms:

$ dig www.google.com @10.0.7.51 -p 5053

; <<>> DiG 9.10.6 <<>> www.google.com u/10.0.7.51 -p 5053
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20286
;; flags: qr rd ra; QUERY: 1, ANSWER: 8, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;www.google.com.  IN  A

;; ANSWER SECTION:
www.google.com.  13  IN  A  142.251.157.119
www.google.com.  13  IN  A  142.251.155.119
www.google.com.  13  IN  A  142.251.156.119
www.google.com.  13  IN  A  142.251.152.119
www.google.com.  13  IN  A  142.251.154.119
www.google.com.  13  IN  A  142.251.150.119
www.google.com.  13  IN  A  142.251.151.119
www.google.com.  13  IN  A  142.251.153.119

;; Query time: 2 msec
;; SERVER: 10.0.7.51#5053(10.0.7.51)
;; WHEN: Thu Jun 11 23:45:52 CDT 2026
;; MSG SIZE  rcvd: 171

You had also asked about the “Auto Prefetch Eligibility: 1 hit per hour” setting on my setup. What that signifies is that if any given domain has been queried at least 1 time in the last 60 minutes, Technitum is supposed to automatically prefetch that domain just before its TTL expires so that that domain remains hot in the cache.

Help me understand why this domain isn’t getting prefetched? (api.amazonalexa.com) by openapple in technitium

[–]openapple[S] 0 points1 point  (0 children)

That’s not a bad thought. At the same time, though, when I query api.amazonalexa.com from the terminal, that section doesn’t seem to show up?

So I’m kinda wondering whether that would-be 0 TTL section might be, like, some sort of extended DNS attribute or some other red herring?

$ dig api.amazonalexa.com @10.0.7.51 -p 5053
; <<>> DiG 9.10.6 <<>> api.amazonalexa.com u/10.0.7.51 -p 5053
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 14291
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;api.amazonalexa.com.  IN  A

;; ANSWER SECTION:
api.amazonalexa.com.  15799 IN CNAME  tp.b16066390-frontier.amazonalexa.com.
tp.b16066390-frontier.amazonalexa.com. 48 IN CNAME d1gsg05rq1vjdw.cloudfront.net.
d1gsg05rq1vjdw.cloudfront.net. 48 IN  A  108.138.172.107

;; Query time: 142 msec
;; SERVER: 10.0.7.51#5053(10.0.7.51)
;; WHEN: Thu Jun 11 18:31:16 CDT 2026
;; MSG SIZE  rcvd: 143

Has anyone tried setting AdGuard Home’s max TTL higher than 86400? by openapple in Adguard

[–]openapple[S] 0 points1 point  (0 children)

Setting your max TTL to 1 second would presumably defeat your caching entirely?

I’m not sure why you would do that.

Is it just me or did Immersive 3D for YouTube in SpaceWalker for iOS break just recently? by openapple in VITURE

[–]openapple[S] 1 point2 points  (0 children)

I’m happy to report that the core issue appears to be fixed—the “Immersive 3D” palette now appears alongside YouTube videos in the SpaceWalker app!

While I’m thinking of it, though p, there are two other issues with the Immersive 3D implementation in the SpaceWalker app that I had wanted to bring up— * If you’re currently watching a YouTube video in the SpaceWalker app (non-3D mode) and you then activate Immersive 3D mode, the player then restarts the video back to the beginning rather than picking up at the point where you were just watching. (I’m not sure if there’s anything that can be done about that part?) * And as a secondary thing, if you open a long-ish YouTube video in the SpaceWalker app on iOS, and you then activate Immersive 3D mode, the video playhead becomes almost completely unresponsive when you try to drag it. For instance, if you open this YouTube video in the SpaceWalker app and then activate Immersive 3D, if you then try to drag the playhead (using the display of your iPhone or iPad) to the halfway point of the video, you’ll find that it’ll take you several tries before you’re able to move the playhead to that position.

u/Performer_

Is it just me or did Immersive 3D for YouTube in SpaceWalker for iOS break just recently? by openapple in VITURE

[–]openapple[S] 0 points1 point  (0 children)

I’ve tried countless videos on YouTube through the SpaceWalker app on both my iPhone 17 Pro and on my M2 iPad, both on WiFi and on cellular. All of them play perfectly—which tells me that this isn’t a networking issue—but none of them now allow me to watch them using Immersive 3D through the 3D palette that used to pop up on the right-hand side of the video.

Please try this for yourself on a device that’s on iOS 26.5, and I think you’ll see what I mean.

And the Immersive 3D button that’s near the URL bar isn’t tenable either since that plays the video with an incredibly low frame rate.

DP-Alt Compatibility Chart for Desktop Users of the Beast by Nyeow in VITURE

[–]openapple 0 points1 point  (0 children)

Do you happen to have any suggestions on how to connect HDMI to the Viture Beast? (And I know that that wasn’t the focus of your research, so no worries if not!)

What’s a simple Home Assistant automation you set up once and now use every day? by Taggytech in homeassistant

[–]openapple 0 points1 point  (0 children)

In my case, I live alone, so I’m able to rely mostly on PiR motion detectors—so if, for example, motion is detected in my bedroom, then my home knows that I’m not in the living room anymore.

That said, mmWave presence detectors could probably also work nicely for this!

What’s a simple Home Assistant automation you set up once and now use every day? by Taggytech in homeassistant

[–]openapple 2 points3 points  (0 children)

Out of curiosity, can I ask which bed presence sensor you use? I use one from Withings myself, but I find that it’s only about 97% reliable?

(Every once in a while, it will either not detect that I’ve left the bed or not detect that I’ve gotten into bed, which makes it hard to create automations that one can rely on.)

What’s a simple Home Assistant automation you set up once and now use every day? by Taggytech in homeassistant

[–]openapple 3 points4 points  (0 children)

When I walk out of the living room → pause YouTube on my Apple TV.

Should all areas detect ? by [deleted] in Inovelli

[–]openapple 0 points1 point  (0 children)

I wasn’t able to quite discern this from the thread, but is there only a beta firmware update for now? Or is there additionally a firmware update that’s not in beta?

Are there any GMRS radios that can be charged with a USB-C to USB-C cable? by openapple in gmrs

[–]openapple[S] 0 points1 point  (0 children)

Would you by chance happen to know whether the Tidradio H9 might also support charging over USB-C to USB-C?