3 ms·
Header in the article: > DNS is pull, not push Except for when it is.... If you increment the serial number of a zonefile on your authoritative ns1 and reloa
by walrus01 5y ago
Header in the article:
> DNS is pull, not push
Except for when it is.... If you increment the serial number of a zonefile on your authoritative ns1 and reload the zone, it will push it to any slaves that are configured and set as authoritative for the zone. Very standard IXFR config.
If we are referring to third parties' caching recursive resolvers updating a zone, then yes, it absolutely is pull not push.
- kelnos 5y agoArticle specifically addresses this, and "pull, not push" is specifically talking about clients querying resolvers, not zone transfers. No need for the pedantry this time.
- BeefWellington 5y agoThis begs the question though: Did her colleague truly believe that a client keeps a record of all DNS records for the entire internet? This is the unspoken result of a belief that DNS is push vs pull. Otherwise, this is just a simple misunderstanding about which systems are clients in the relationship, which I suppose is less fun to write a blog about.
- bingo-bongo 5y agoTo be fair, your ns secondaries usually does pull the zone (axfr) or zone changes (ixfr) from the primary - the zone reload just sends a notify to trigger it.
- NoWayDude1 5y agoThis is described in section "okay, DNS records actually do “propagate”."
- zimpenfish 5y ago> it will push it to any slaves that are configured But "it" here doesn't include every DNS server, right? Because, e.g., djbdns definitely doesn't do any pushing when you rebuild the database. And PowerDNS has "native replication" mode where there's no pushing done by the server on changes.