DNS is already done by Tor. In fact, if you feed it a raw IP, it will warn in tor's output that it received an IP, which may indicate that the user has accidentally setup browsing via Tor, but DNS resolution via a normal, unsecured way.
YouTube mainly throttles TOR hard and it's a bit of a fight uphill against a never ending avalanche of Captchas or a straight up service refusal. Bridges solve this, by going through exit nodes that are not publicly listed to be TOR exist nodes. Even with bridges it's still a high chance to trip Google's bot detection.
What I mean is, streaming media usually uses UDP (I don't know about YouTube, but I'd guess that's the case) and according to this thread, Tor routes only TCP and not UDP. So is YouTube and other streaming media being routed around Tor?
> (I don't know about YouTube, but I'd guess that's the case)
YouTube delivers video in chunks over the standard HTTPS port 443, as does Twitch. YouTube supports HTTP/3, so it will use UDP via QUIC if your browser and network also support it, but otherwise it will simply go over TCP.
YouTube mainly throttles TOR hard and it's a bit of a fight uphill against a never ending avalanche of Captchas or a straight up service refusal. Bridges solve this, by going through exit nodes that are not publicly listed to be TOR exist nodes. Even with bridges it's still a high chance to trip Google's bot detection.
HTTP/3 is unsupported.