Hey everyone,
I got a request about adding a DNS record, but the catch is they want it to not replicate across our entire domain. We have domain controllers (DCs) in different data centers and AWS regions, and they want a specific record on only the DCs located in one data center. On top of that, they need a different record on the DCs in another location.
For example, if a server in Data Center 1 accesses url.company.com, it should resolve to a specific IP through a CNAME. Meanwhile, if a server in Data Center 2 accesses uri.company.com, it should resolve to a different IP, hitting a different DC.
Is this kind of setup even feasible? From what I've read, it seems like it might not be possible without changing how DC replication works. Maybe just using a host file entry on the servers in each data center might be a simpler solution?
Thanks for any insights!
3 Answers
You could set up one DNS record for a load balancer, and let the load balancer handle the logic for routing the traffic. This way, you control how requests are distributed without getting into complex replication issues.
Unfortunately, with standard Windows DNS, you can't control AD syncing at the individual record level; it's done per forward lookup zone. If they’re trying to set this up like a CDN, it's not the best approach—they should really handle this at the web application or load balancer level.
Consider using DNS Policies. They can help you manage DNS traffic based on criteria you set, which might be a cleaner solution compared to managing multiple records and their restrictions.
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