Re:Microsoft Azure: Cutting prices on compute and storage
by Andys on Tuesday April 01, 2014 @02:11AM
(#7506452)
Some DNS clients ignore the TTL, or have their own minimums.
One of the worst offenders, ironically, is Microsoft's own Windows XP which is notorious for having a minimum TTL of 10 minutes, forcing people away from DNS as a means of failover.
Re:Microsoft Azure: Cutting prices on compute and storage
by CarlHoerberg on Tuesday April 01, 2014 @08:25AM
(#7507510)
Do you have a reference backing that? I've only found information contradicting that, eg: http://support.microsoft.com/kb/318803
I know some places can move IPs around at will, but it seems like the wrong layer in the stack to do it. Aren't IPs something you want to assign based on your network topology? If you need an arbitrary identifier that can move between machines, what's wrong with DNS? (And how are you not re-inventing DNS?) (and the names are more memorable)
If you do have the capability to do this, does it not tie you to that provider? Presumably the IPs would be allocated to the provider, so switching to a new provider would necessitate a new IP, whereas DNS addresses can point anywhere.
Unless I'm completely misunderstanding (I've never tried these shenanigans with IPs), so please correct me if I am.