I am not an infrastructure expert. I have the following scenario:
- Primarily a Windows Environment for servers, laptops, desktops, DNS, etc.
- One AIX server (running Symitar/Episys), which we have some issues connecting to at times due to DHCP reservations
- A WAN network (wired) and a wireless network
My understanding of how DHCP and DNS work for our environement is this:
- If I dock my laptop on the WAN network, I get a DHCP reservation, I register it with DNS.
- If I undock my laptop and join the wireless network, I get a new DHCP reservation, it registers with DNS
- If I then attempt to log into the AIX server, the AIX server sees my IP (on wireless) and does a reverse lookup in DNS to find my PC name. This is correct.
- Then the AIX server does a forward lookup of my PC name to confirm the IP for the Symitar/Episys Console. The machine name is to be specified in the Symitar Console record. The first record it finds when searching my PC name in the DNS zone is my first IP, because it has not been cleared. This IP may have been given out to someone else and no longer matches.
- Logins not allowed from host IP XXX.XXX.XX.XXX
My understanding is that if the earlier entry in the DNS zone would automatically clear when my machine reserves a new IP with DHCP, this issue would not happen.
Is that the case? Is that possible, to force a release of all earlier IPs for a machine upon new connection? Is that a bad idea?
