Hi
We have a multihomed server which only has one of its NIC ports plugged into our network.
We did however briefly plug the second port into the network last week, having un-plugged the original connection.
This second port immediately grabbed a DHCP address. Now that we no longer have this port connected, and are back to our original setup of having only NIC1 plugged in with a fixed address, clients are resolving the server name to two addresses - the fixed address on NIC1, and the address grabbed by NIC2 when we temporarily connected it.
No problem I thought, I'll check that the lease for port 2 has expired and deleted the revelant A and PTR records from DNS.
I did so, and flushed DNS cache on all my clients and everything was fine.
However, every morning the problem re-occurs and when I check in DNS, the second A record for my servername has re-appeared - even though I had deleted it the previous morning...am am missing something obvious here?
Cheers
We have a multihomed server which only has one of its NIC ports plugged into our network.
We did however briefly plug the second port into the network last week, having un-plugged the original connection.
This second port immediately grabbed a DHCP address. Now that we no longer have this port connected, and are back to our original setup of having only NIC1 plugged in with a fixed address, clients are resolving the server name to two addresses - the fixed address on NIC1, and the address grabbed by NIC2 when we temporarily connected it.
No problem I thought, I'll check that the lease for port 2 has expired and deleted the revelant A and PTR records from DNS.
I did so, and flushed DNS cache on all my clients and everything was fine.
However, every morning the problem re-occurs and when I check in DNS, the second A record for my servername has re-appeared - even though I had deleted it the previous morning...am am missing something obvious here?
Cheers