3 ms·
Two unrelated questions. Why would I prefer this over NSD? Are ragel parsers really 100x faster than bison parsers? Off hand, that seems atypical and more like
by tedunangst 12y ago
Two unrelated questions. Why would I prefer this over NSD?
Are ragel parsers really 100x faster than bison parsers? Off hand, that seems atypical and more likely the result of other changes.
- scott_karana 12y ago> Why would I prefer this over NSD? That was also my question before I read this. From the article: > only two usable open-source DNS servers > The decision [to make Knot] was based on the idea that DNS protocol is one of the most important protocols of the Internet, and thus it's stability, security, and reliability would benefit from another DNS server implementation that was written from scratch with full standards compliance in mind. Seems laudable to me. Practically speaking, I doubt there's much difference between Knot and NSD. Why not run a few of both? :)
- oerdnj 12y ago> Why would I prefer this over NSD? Don't drop NSD, it's a cool piece of software and folks at NLnetLabs are our friends :). My advice would be to run at least two different pieces of software in any deployment since any software can have bugs. See this very nice presentation by Anand Buddhdev from RIPE NCC about their DNS infrastructure: https://ripe68.ripe.net/presentations/284-AnandBuddhdev_RIPE68_DNS_Update.pdf https://ripe68.ripe.net/presentations/284-AnandBuddhdev_RIPE... > Are ragel parsers really 100x faster than bison parsers? I wouldn't say that generally, but it's true for our zonefile parser. (Or maybe the bison parser we had sucked that hard :)). > Off hand, that seems atypical and more likely the result of other changes. Probably, but those changes came hand in hand with the change of the parser generator.