279 karma · joined September 13, 2009
[ my public key: https://keybase.io/dsporter; my proof: https://keybase.io/dsporter/sigs/pV4cfrY-7Jk69s-cPgasBBqciu-Q6t82ox4CkY02Lws ]
There is the Civil Reserve Air Fleet, of which FedEx is a member.
The "up to 48 hours" is commonly used because that's the ttl of many things that matter. For instance, NS records for names in the .com zone have 48 hour ttls.
You can give better estimates to your users if you know the state you're transitioning from. For instance, a brand new .com domain would be 15 min negative ttl plus the .com zone file update frequency.
I worked on dns gslb for a long stretch at Facebook^WMeta, and didn’t see an excess of bad actors. The vast majority of users follow our dns changes in an orderly fashion. Most delay sources to clients themselves.
How would you propose that work? Hedging currency risk against unsold product isn’t a hedge, it’s a directional bet.
Agreed. I think D-Link devices were some of the most common we saw.
Just as a heads up, zero in the last octet results in general reachability problems. We used x.y.z.0 as a vip at Facebook^WMeta for a while, but learned the hard way that some people can't reach those ips.
Some additional info from RIPE: https://labs.ripe.net/author/stephane_bortzmeyer/all-ip-addr...
https://ir.firstrepublic.com/static-files/1a464a0b-9396-4bd4...
io_uring enables exactly this
The term is ambiguous, and many uses don't include the trailing dot. See IETF RFC 8499 section 2.
> DNS is strictly ASCII-only
DNS is not strictly ascii. At the protocol level labels are octet strings. You may be thinking of the LDH convention.
Some additional info from RIPE: https://labs.ripe.net/Members/stephane_bortzmeyer/all-ip-add...