Keep the clients in the comparison
Opening a provider's page in Firefox is a useful observation, but it does not establish that another application uses the same name-resolution path. Firefox documents DNS over HTTPS and fallback behaviour. A native player can have its own networking arrangement or use the system path. Record the clients rather than assuming the browser test represents every application on the device.
Also identify the host being tested. A homepage and a media resource can use different names. Even a genuinely identical resolver path for the homepage would not establish that a second media hostname resolves or that later secure access and playback stages succeed. Preserve the exact visible failure category.
A hypothetical page-and-player report
Suppose a viewer can open an official support page in Firefox while a native player reports a name-resolution failure for its documented media host. The useful report includes both hostnames with private paths removed, the browser's relevant DNS-over-HTTPS state and the player version. It does not say that the entire internet works so the account must be wrong.
Use Firefox's current documentation to understand the selected mode. A configured preference is not proof that every lookup used one provider under every condition, because fallback and network checks can matter. Do not disable protections or switch public resolvers repeatedly without preserving the original result.
On a workplace, hotel or other managed network, ask its administrator about the supported setup. The purpose is to explain a comparison, not bypass network policy. On an owned network, any authorised resolver test should change one understood condition and record whether the same player and hostname behave differently.
Return to the actual player task
After a documented correction, test the native player's normal source entry and selected authorised item. A Firefox page continuing to load is insufficient validation of the original application failure. If the error progresses from name resolution to an access or media message, record the new stage separately.
The useful conclusion identifies which client, hostname and condition succeeded. It does not promise that DNS-over-HTTPS improves stream quality or that one browser proves service availability. Keeping the client path visible helps support investigate the real failure without unnecessary credential resets or unsupported hostname substitutions.
Questions answered
Does Firefox loading a page prove the native player uses the same resolver?
No. Preserve each client's networking context and the actual hostname tested.
Does enabling DNS over HTTPS guarantee better video quality?
No. Name resolution and later media delivery are different stages. Test the actual authorised playback task.
Sources & further reading
Official references for the subjects discussed. Service terms and device software can change.