Pods in a Remote deployment intermittently fail to resolve an internal DNS hostname (coinflip behavior — the same repeated request sometimes resolves, sometimes fails), even though the target host and network path are otherwise fine.

All FAQ questions / Developer Studio, deployment, and upgrades

Answer

Check whether the cluster's DNS was configured with the installer's dedicated DNS-setup step during initial middle-tier setup — without it, pods fall back to default public DNS servers (which genuinely can't resolve internal-only hostnames) instead of consistently using your internal DNS server, producing exactly this kind of intermittent, coinflip-style resolution behavior. Running the installer's cluster-DNS-configuration resource step (main.ps1 -resource 'SETK8SDNS') points the cluster's internal DNS correctly and resolves this.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Developer Studio, deployment, and upgrades questions