|
I don't really have to make that clear, because I'm the target market ;-) No, but seriously: it's a tool I wrote for myself (and other people can use it if they like) - I've optimized for the only case I actually know well, which is What I Want. If you want Something Different, man, there's like 430 billion domain search tools out there, most of which are more focused on pleasing other people than mine. That's not to say you should shut up or anything - your feedback is great, and I may even act upon it, but I don't want to give anyone the illusion that this is a product intended for mass consumption. It's like I made some brownies, and other people should feel free to take one if they want, and you're even free to say "You know what? These brownies would be better without the almonds," but I'm not necessarily gonna take the almonds out. I like almonds, and you don't have to eat them, and people make brownies without 'em all the time, and I think that's swell. Or maybe it's just that it would be better if I used "real" chocolate instead of Hershey's - but meh, it was there and cheap, so I used it. (On that subject: it's using NodeJS's built-in `dns.resolveNS`, whatever that means. Didn't see anything referencing SOA, but maybe that's the thing to check? In practice I'm not really bothered with the rate of false +/- at the moment, it seems to work ok for my purposes. If it's a matter of changing one function call, I'd do it, but I'm not going to hack my own DNS wrapper just to get a specialized query. At least, not while I'm in the middle of exams.) |