[mtlmtlmtlmtl]

This is mostly off-topic I suppose but I recently noticed that Netflix, and Netflix on my TV(WebOS) specifically is absolutely spamming my router with DNS requests sometimes several times a minute, most of them for nrdp-ipv6.prod.ftl.netflix.com. I'm not blocking them btw, so it's not some buggy retry thing going on.

Even if I do a hard reboot of my TV and don't start the app, my TV is still happily resolving away. I'm gonna have to set up a local cache or something just to save on my NextDNS quota.

Edit: I just asked Netflix support about it. Worse than useless, just kept telling me to either try a different internet connection(no idea why), then they told me to take it up with my ISP and immediately closed the chat. I'm gonna wait an hour or so, open another chat, and tell them my ISP said this was purely a Netflix issue, I suppose.

[wesleytodd]

Not my area of work, but pretty sure that is expected behavior to resolve an ever changing set of services being called out to. Better to do dns resolution than for a call to fail and have to re-resolve while you wait on a loading screen right?

[grepfru_it]

It looks like the TTL on that address is 24 hours, so likely a problem of the dns resolver, which would point to webos. Have you tried a factory reset recently? (Or root and diagnose the system internally)

[mtlmtlmtlmtl]

My system is rooted actually, but no idea how to disgnose this. I can SSH in but it's a very limited busybox setup and everything app-related seems to be encrypted.

[NavinF]

> absolutely spamming my router

Ah, how many k/second?

> sometimes several times a minute

WTF?

We're talking 0.00003 thousand requests/second? Most apps do several DNS queries per minute. Otherwise every DNS update would require >1 minute to propagate. Slow DNS updates is a massive pain in the ass.

FWIW, ISP DNS servers and cheap home routers are both capable of caching DNS responses, updating the cache when they get a query for something that's about to expire, and serving thousands of queries per second.

> then they told me to take it up with my ISP and immediately closed the chat

This is the correct response. DNS is usually provided by the ISP via DHCP. If their server can't handle "several times a minute", the ISP would be at fault 100% of the time

[mtlmtlmtlmtl]

My DNS service isn't having any problems, that's your imagination. Everything works. It's just filling up my quota. If "every app" is doing this, why does Netflix account for close to half of all DNS requests on all my devices?

I explained to them that I'm not even using ISP DNS. They still told me to talk to the ISP. Still think it was the correct response? It was obvious they didn't even know what DNS was, they were just slavishly following a script that said DNS resolving issues -> ISP. They didn't even grasp what I was reporting to them.