about:preferences#privacyCertificatesView CertificatesAuthorities TabImport..., import ca.crt file, click on checkboxes to trust and confirm.about:preferences#privacyDNS over HTTPSIncreased Protection radio buttonCustom on Custom Provider Combo Boxhttps://localhost:8443/dns-query on the input which appear belowStatus: Active Provider: localhost must appear below DNS over HTTPS titleWe need to disable RFC-1918 on the browser to make browser able to accept private IPs for hostnames solved on DoH server. The RFC-1918 defines what are private, public IPs, when and where they should be used. For this reason, Browsers won’t accept to resolve private IPs from hostnames solved using DoH because it probably is not a production usecase, the environment which DoH was thought to be used.
about:confignetwork.trr.allow-rfc1918 and change it to trueIn my tests, some real domains like .dev won’t work depending on the combination
of private ip + default port (80, 443), the browser will not accept to solve, so evict them, .com seems to work
normally;
You can track which names are being solved by accessing about:networking#dns