Hi All,
Hoping someone can advise. I've noticed that when a user connects with Pulse, and they are given an IP address from the MAG DHCP range (issued by MAG device), that an A record is created for them in DNS. This is correct behaviour.
However, when they disconnect and reconnect, and are given a new or same IP, then a new A record is created but the old one remains in DNS.
Is there a way to force a release and renew from MAG side, or a delegate account of some kind that I can setup to do this on the MAG's behalf? I realise I can enable tombstoning in DNS but thought I would check here first.
Thanks
Natasha
Solved! Go to Solution.
This activity of updating the DNS is probably on the client end and not the MAG.
If you are running windows DNS and clients then setup the DNS scavanging options on your windows server to prune the dead records.
This activity of updating the DNS is probably on the client end and not the MAG.
If you are running windows DNS and clients then setup the DNS scavanging options on your windows server to prune the dead records.
Many thanks for confirming Spuluka.