How-to Specify exclusions for DNS-over-HTTPs requests

Question

Setup:

Edge current branch

DNS over HTTPs is set up and working prooved by Edge Logging

Image

Problem:

we have a webpage that is available from Public DNS but when opened from internal network it needs to resolve with internal AD DNS.

Examples / Usecases:

scenario 1:

User opens Edge

opens portal.contoso.com from external network

Portal.contoso.com resolves to the public DNS entry of contoso.com via DNS over HTTPS using Cloudflare or any other provider specified.

expected behaviour: as above (by design)

scenario 2:

User opens Edge

opens portal.contoso.com from internal network

Portal.contoso.com resolves to the public DNS entry of contoso.com via DNS over HTTPS using Cloudflare or any other provider specified.

expected behaviour: as above (by design)

required behaviour:

portal.contoso.com should resolve over local DNS (AD DNS)

Feature Request:

We need a GPO control to specify that portal.contoso.com should first resolve to local DNS (AD DNS).

Means a list object, json or csv in ADMX.

Afaik there is no ability to do so. Other products like Firefox is reportingly able to specify exclusions.

Are there other ideas how to solve this, or is this a FR that is already in milestone or backlog?

Answer 1

Hi @Wester-Ebbinghaus, Karl

The group policies for Edge DNS-over-HTTPs are DnsOverHttpsMode and DnsOverHttpsTemplates. I think they can't achieve what you want and there's no other way to achieve this now in Edge.

If you want to make a feature request about this, you can provide feedback to Edge team by pressing Alt+Shift+I in Edge. The Edge team will check the feedbacks and improve the product continuously. Thanks for your understanding.

---

If the response is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

Regards,
Yu Zhou