[email protected] said: >> That won't catch the case where the pool DNS name is used as a server. If we >> put a simple still-there check in the server case, clients would end up >> switching servers every time they checked. I don't see any harm in that.
> I donât think I understood what this meant. I'll try again. There are 2 cases: pool pool.example.com and server pool.example.com If we fix the pool case, we still have to handle the server case. I was thinking that the server case would do a DNS lookup and check all the IP Addresses. If one matched, fine. If not, drop the current IP Address and start using one of the new ones. That would handle the simple case of a server changing IP Addresses. If the name is actually pointing at a large pool that rotates through a lot of IP Addresses, it will probably switch to a new IP Address each time it checks. I was trying to say that was OK. -- These are my opinions. I hate spam.
_______________________________________________ pool mailing list [email protected] http://lists.ntp.org/listinfo/pool
