I'm managing a setup where I have primary and fallback databases hosted on-premises, connected via a VPN to Azure. I use several Host Pools that connect to the primary database, and I want them to connect using the HostName instead of the IP address. This way, if the primary database fails, I can easily change the DNS to point to the fallback.
Here's what I've done so far:
1. Set up a Linux VM to run DNS.
2. Updated the Azure Virtual Network to route to the Linux machine for DNS resolution.
3. Conducted tests on the Host Pools and found that they currently require the full domain name *myhostname*.internal.cloudapp.net for resolution instead of just *myhostname*.
My questions are: am I okay relying on this full domain name? Does Azure change these domain names frequently? Also, is there anything significant that I might be overlooking? I understand that if the DNS server goes down, my setup will fail, so I wanted to get some insights before I delve into DNS redundancy. Additionally, is there a way for my Host Pools to resolve just using *hostname*?
2 Answers
Using the full DNS name is actually a safer bet as it reduces the risk of configuration mistakes. However, it seems like there's an issue with your on-premise LAN/VPN setup since your DNS isn't resolving the suffix automatically. You should consider resolving the databases themselves as 'DB.domain.internal' instead of trying to manage host names directly. Double-check your DNS setup to ensure everything's aligned properly.
Have you thought about using hosts file entries for DNS resolution? It's not the most elegant solution, but it can be straightforward to manage, especially if you're dealing with a limited number of entries.
Related Questions
Can't Load PhpMyadmin On After Server Update
Redirect www to non-www in Apache Conf
How To Check If Your SSL Cert Is SHA 1
Windows TrackPad Gestures