I'm a network professional, and while I have a solid understanding of DNS, I need some clarity on higher-level concepts. We're currently in the process of merging two companies, each with their own DNS domains – let's say one is company.com and the other is business.com. We've been trying to set up conditional forwarders so each side can resolve the other's domains. However, whenever we configure a conditional forwarder for business.com on company's DNS server, it prevents us from resolving the external domain entries for business.com. Essentially, it reroutes everything to the internal DNS server. Is there a straightforward way to handle this until we consolidate both domains into one?
5 Answers
There are a few options to manage having a single DNS domain while keeping separate internal and external records. You can:
1. Set the internal DNS server to hold both internal and external records, prioritizing internal IPs when conflicts arise.
2. Use a Conditional Forwarder for each external host or subdomain from the internal DNS server.
3. Create Delegated Zones for every external host pointing to outside DNS.
All three methods have their pros and cons; it really comes down to which one fits your situation best without creating extra maintenance work.
For this to work, you must configure the conditional forwarders to point to the internal DNS servers of the other company, not their external ones. Just make sure those internal servers can handle external names; otherwise, you'll create a black hole for requests. But honestly, it might save you a lot of headaches if you consider migrating everyone to one domain straight away.
You definitely need to make sure you have your internal routes set up correctly. Without this, things can get messy really quick!
I wish I were wrong, but I don't think this approach will work as intended. It seems like the only viable solution is to replicate the external zone within Windows DNS, otherwise you might hit a wall.
Yes, it's feasible, but you have to remember that Split Horizon deals with how DNS servers handle authoritativeness, whereas Conditional Forwarders work on the resolver side. They don't communicate directly, and often it's better to keep them on separate servers.
As for your issue with external resolution, that's standard behavior. It might be worth looking into why company.com needs to resolve business.com externally, especially with both networks being interconnected now. Avoid partially connected networks; they tend to complicate things.
If you've got teams still needing access to external resources post-merger, consider setting up conditional forwarding with host file entries for those specific cases to simplify access.
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