DDNS Name Changes to Old Configuration
Posted: Wed Jun 07, 2017 5:01 pm
Hi - I have several servers and bridges I use for development environment and have a strange problem keeping track of them.
I use softether DDNS feature instead of IP address all the time on all machines.
Say I have "vpn123.softerther.net" on machine A
Then I copy configs, make modifications, select a new DDNS name and create machine "B" with DDNS "vpn456.softether.net"
Machines A and B are shut down at some point, and when I reboot "B" the next time it will change the DDNS to "vpn123.softether.net" conflicting with machine "A". Machine "A" then become unreachable by name.
Why is the cloned & modified machine changing DDNS names back to original and how can I make a DDNS name fixed to never change on reboot, restart, etc?
Thanks!
BTW, not sure this is 100% true but seems to happen when the power is cycled (i.e. not graceful shutdown of Machine B)
I use softether DDNS feature instead of IP address all the time on all machines.
Say I have "vpn123.softerther.net" on machine A
Then I copy configs, make modifications, select a new DDNS name and create machine "B" with DDNS "vpn456.softether.net"
Machines A and B are shut down at some point, and when I reboot "B" the next time it will change the DDNS to "vpn123.softether.net" conflicting with machine "A". Machine "A" then become unreachable by name.
Why is the cloned & modified machine changing DDNS names back to original and how can I make a DDNS name fixed to never change on reboot, restart, etc?
Thanks!
BTW, not sure this is 100% true but seems to happen when the power is cycled (i.e. not graceful shutdown of Machine B)