3 ms·
When you change zone files (eg. in Bind9) then you need to reload the server in order to have the changes registered. For large amount of zone files reloading g
by andris9 6y ago
When you change zone files (eg. in Bind9) then you need to reload the server in order to have the changes registered. For large amount of zone files reloading gets very expensive, so it is not done after every change but after every, like, 5 or 10 minutes.
On the user side this is super annoying:
1. you create a new A record
2. you try to open the domain name in a browser
3. changes are yet not reloaded, so DNS server responds with NXDOMAIN
4. browser caches the failing result for an hour or so
5. changes get reloaded after 10minutes and the domain gets available...
6. ...except for your computer because every DNS server between the source and your computer has cached the errored response
As PendingDNS reads always records from Redis then there is no reloading step and thus there is nothing to wait for.
- memexy 6y agoGood to know. How is the client side issue addressed? > 4. browser caches the failing result for an hour or so
- andris9 6y agoIf the client manages to get a successful response then it is cached normally - whatever the TTL value attached to the record defines. In case of PendingDNS all TTL values are 5min by default. So the problem is with unsuccessful responses - there is no TTL attached, so the client uses whatever it finds suitable - maybe uses values from SOA records, maybe has its own default, who knows - in any case, it is quite long.
- memexy 6y agoThx.