News for hackers. Stuff that matters.
Re:DNS doesn't “propagate” by kelnos on Monday December 06, 2021 @07:02PM (#29467489)
No, it's not. Understanding how DNS changes work is actually necessary when debugging DNS issues or doing work around an infrastructure that uses DNS. Thinking the "propagation model" is correct when working on these systems will make you ineffective at your job, and possibly break things.

For the average non-technical user, it's fine to use the "propagation" explanation. It's easy to understand, and it does describe the result the user sees, even if it gets the mechanism wrong. But the propagation explanation has become so widespread and ingrained that technical people who need to know the correct explanation often don't, and don't even realize that they've had the wrong information for years.

Re:DNS doesn't “propagate” by NoPicklez on Tuesday December 07, 2021 @07:09AM (#29471548)
The author of the article couldn't even come up with a solution or better term to use. The term propagation is used by ICANN in their functional requirements and used by the IETF in their DNS RFC. Even CloudFlare uses the term.

A single word isn't going to tell you exactly how something so technical works, but it is the most correct term to use to describe what is occurring.

It is completely pedantic.

Re:DNS doesn't “propagate” by spurgu on Tuesday December 07, 2021 @10:30AM (#29473457)
If you aren't aware that DNS propagation is actually about waiting for cached DNS records to expire then maybe you shouldn't be the one debugging DNS issues in the first place?

I think propagation it's highly descriptive. You make a change and then you wait for various DNS servers to acknowledge that change (once cached records expire).