<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Detection on imds.foo</title><link>https://imds.foo/tags/detection/</link><description>Recent content in Detection on imds.foo</description><generator>Hugo</generator><language>en-us</language><lastBuildDate>Mon, 05 Oct 2026 19:36:38 +0200</lastBuildDate><atom:link href="https://imds.foo/tags/detection/index.xml" rel="self" type="application/rss+xml"/><item><title>Cross-tenant DNS forwarding in Azure: plumbing that should not work?</title><link>https://imds.foo/posts/cross-tenant-dns-forwarding/</link><pubDate>Wed, 02 Sep 2026 00:00:00 +0000</pubDate><guid>https://imds.foo/posts/cross-tenant-dns-forwarding/</guid><description>&lt;p&gt;My last post on cross-tenant DNS zones naturally leads to the question if other Azure DNS resources have the same visibility issue. One resource of great interest: Private DNS resolvers. DNS resolvers are basically the DNS plumbing Azure provides. You deploy a private one if you have inbound or outbound DNS queries requiring a more complex setup. For example from your on-premise datacenter to an IP in a delegated inbound endpoint subnet, which allows your on-prem infrastructure to resolve names in your Azure private zones. Outbound endpoints in combination with a resource called forwarding ruleset allow you to send Azure DNS queries to on-prem or 3rd party DNS servers. Forwarding rulesets basically define which queries get sent where.&lt;/p&gt;</description></item></channel></rss>