Hey everyone, I need some help with an issue I'm facing in my Active Directory setup that involves DNS registration on Domain Controllers with multiple network interfaces. Here's what I've got going on: I've got two Domain Controllers with both being linked to two different networks - one for production and another for point-to-point connections. The problem is, when I run an nslookup on my servers, I see four name servers instead of just the production LAN IPs. I noticed that A records pointing to the point-to-point connections keep reappearing in my DNS records even after I manually delete them. I've checked the settings and disabled registration for the point-to-point NIC, but those entries still come back. Is this a Netlogon quirk or something else? Any advice on how to fix this would be appreciated!
4 Answers
Sounds like a lot of unnecessary complexity. Consider ditching that second NIC entirely and stick to the primary connection for backups and everything else. Just because something was working in the past doesn’t mean it’s the best solution now. Simplification tends to ease a lot of potential issues.
You should know that multi-homed domain controllers aren’t officially supported. That kind of setup can be a recipe for disaster. It's hard to troubleshoot broken configurations when they aren't built according to best practices. You might want to rethink how you've got things set up.
It worked before, so there must be something that changed recently. Have you checked for any internal settings that might have triggered the issue?
The auto-reappearing A records you’re seeing are pretty standard for multi-homed DCs; they generally add all interface IPs to DNS automatically. However, since you’ve got a point-to-point link, which doesn't seem useful if both DCs are on the same network, maybe consider simplifying your connections. DNS can get a bit tricky in these situations, but I wouldn’t dive too deep unless necessary.
Actually, that point-to-point link is there to help me back up to another server without going through the firewall! It's not the usual setup, but it's necessary for my situation.
First off, I'd recommend seriously considering dropping that second NIC. Running Domain Controllers with multiple NICs often leads to headaches down the line. Just keeping it straightforward usually solves a lot of problems. If you absolutely need both, look into NIC teaming, though that's also sometimes frowned upon for DC setups.
I second that. Always heard multi-homed DCs create more issues than they solve.
True. Just keep in mind that unsupported configurations will lead to more hassle in the long run.