A
Andre Fortin
Hello,
I have a DC which is also a backup server. In order to back up a
certain server that is not on our domain, I have a second NIC in the DC,
configured on the same subnet as that server (this bypasses going through 2
firewalls to get to that server). I configured the second connection to not
register itself in DNS (in the DNS tab, I've unchecked 'Register this
connection's address in DNS'. The interface facing the real domain is set
to register itself in DNS. However, every time I enable the second
interface, it DOES register in DNS, and therefore, clients are seeing an IP
that is not reachable. Why is this address being registered in DNS despite
being explicitly told not to? Is this a bug? Or am I missing something?
Thanks in advance,
Andre Fortin
I have a DC which is also a backup server. In order to back up a
certain server that is not on our domain, I have a second NIC in the DC,
configured on the same subnet as that server (this bypasses going through 2
firewalls to get to that server). I configured the second connection to not
register itself in DNS (in the DNS tab, I've unchecked 'Register this
connection's address in DNS'. The interface facing the real domain is set
to register itself in DNS. However, every time I enable the second
interface, it DOES register in DNS, and therefore, clients are seeing an IP
that is not reachable. Why is this address being registered in DNS despite
being explicitly told not to? Is this a bug? Or am I missing something?
Thanks in advance,
Andre Fortin