3 ms·
What problem are you encountering? 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 use
by dsp 5y ago
What problem are you encountering?
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.
- anderspitman 5y agoI'm implementing my own domain seller targeted towards making domain names easy enough for the average person to use. I'd like to move towards a world where you can read the current authoritative TTL and guarantee the user everything will be updated within that time, rather than saying "Up to 48 hours".
- dsp 5y agoThere will never be guarantees. 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.
- anderspitman 5y agoWell yeah nothing is 100% guaranteed. Including the 48 hour rule. Technically ISPs could set every TTL to take weeks. But I maintain we can make a lot of progress reducing the size of the long tail. Sometimes you have to work with broken systems, but why leave things broken that don't need to be? DNS TLL compliance can be improved one organization at a time.
- dsp 5y agoWhy are you so confident there’s a big problem to solve here?
- anderspitman 5y agoBecause every provider I'm aware of still recommends 48 hours?
- deleted 5y ago[deleted]