Hi everyone,
Our organization uses custom internal DNS servers (added on the VNET level) for DNS resolution. Private DNS zones are avoided in general.
We configured private link for Fabric as per the steps outlined in - https://learn.microsoft.com/en-us/fabric/security/security-private-links-use
We did not integrate the private endpoint with private DNS zones and created Forward Lookup Zone in our internal DNS server as per the FQDNs and IPs in the DNS configuration page of the private endpoint (We have been doing the same for all other Azure services and everything works fine as expected).
For Fabric however, after configuring private endpoints there was disruption for all the Power BI users. Users across the organization were unable to access reports and Power Bi stopped working. Some reports were loading over and over again. For some users we deleted the browser cache, ran dnsflush and what not. But the disruption was major.
We ended up disabling private link and deleting the A record entries from the DNS servers, so that people can resume there work.
We are planning to again attempt to deploy private link for fabric over weekend to minimize the downtime for users.
Our theory was that this disruption was outcome of the replication time in the DNS servers.
Please provide feedback on the scenario, and let me know if there's anything that we are missing and if our theory is correct. Or, if its not possible to use custom DNS server with Fabric private link at all.
Regards,
Rajat