I'm trying to figure out if it's possible to configure DNS server settings for managed DevOps pools so that I can resolve internal hostnames. Has anyone done this or know the steps involved?
3 Answers
Your question isn't 100% clear, but here’s what we do: We have a managed DevOps pool under a management subscription and we also set up a DNS private resolver alongside an Azure Firewall in our connectivity subscription. The Azure Firewall acts as a DNS proxy, allowing us to log all DNS requests and resolve internal hostnames. That said, you can technically use the private resolver on its own without the firewall; VNet peering isn't a requirement for DNS resolution either.
I haven't done it yet, but it looks like you might be able to set DNS resolution as long as you've got everything configured correctly. Check out this guide from Microsoft to delegate the subnet to the managed DevOps infrastructure: https://learn.microsoft.com/en-us/azure/devops/managed-devops-pools/configure-networking?view=azure-devops&tabs=azure-portal#delegate-the-subnet-to-microsoftdevopsinfrastructurepools
You could do this by using a custom image that has pre-configured nameservers in the resolv.conf or hosts file on Windows.
I just want to specify nameservers for the agent when it starts up, and while I believe it should be doable, I haven’t figured out how. Ideally, it should work at the managed DevOps pool agent level, similar to how you can set nameservers at the VM or app service level.