Aug 30 2021 09:21 AM
Setup:
Edge current branch
DNS over HTTPs is set up and working prooved by Edge Logging
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?
Aug 30 2021 01:24 PM
@kwester-ebbinghaus-business Hello! There are a couple of policies for DNS-over-HTTPS. Would these be able to help your scenario?
Thanks!
-Kelly
Sep 01 2021 05:37 AM