Slashdot Mirror


BIND Is Most Popular DNS Server

bleachboy writes "Last week I completed a new DNS server survey, since D. J. Bernstein's hasn't been updated for years. Not surprisingly, BIND wins. Why is it so hard for alternate DNS servers to gain favor, especially when BIND can be so frustrating sometimes? And yes, I'm shilling."

452 comments

  1. probably by greechneb · · Score: 5, Insightful

    probably since most distros (BSD & Linux) include BIND as their default DNS server. People are lazy.

    1. Re:probably by kinema · · Score: 4, Insightful
      People are lazy.
      If laziness dictated what DNS server people ran I find it hard to believe that they would choose BIND. BIND is hardly the simplest DNS server out their to learn, setup and maintain.
    2. Re:probably by huge · · Score: 4, Interesting

      No matter which DNS server is the default in any distro. All of the DNS admins I know will compile or reinstall the server anyway.

      It maybe true that some of the home users running a "server" in the closet may be using the default server of distro, but I think there aren't that many to make a difference.

      --
      -- Reality checks don't bounce.
    3. Re:probably by bryanp · · Score: 2

      probably since most distros (BSD & Linux) include BIND as their default DNS server. People are lazy.

      Probably since most retail desktop OS's (Mac & Windows) include IE as their default browser. People are lazy.

      (sorry, I couldn't resist)

      --
      "An unarmed man can only flee from evil, and evil is not overcome by fleeing from it." Col. Jeff Cooper
    4. Re:probably by kfg · · Score: 1, Funny

      ARRRGHHHH!! MY EYES!!

      Fooled you. I'm not wearing any underwear.

      KFG

    5. Re:probably by Dr+Bile · · Score: 0

      Indeed, people generally use what is provided for them. And BIND generally does the job, which is enough for most folks. Most people, myself included, couldn't care less for any more functionality than responding reliably to a request for an A record, MX record, whatever. I use TinyDNS for an authoritative nameserver. It is lightweight, reliable, and apparently secure. Yeah, it hasn't been updated in a while, but I have no need for it to be. I'm pretty sure BIND has had more releases for security updates and bugfixes than for new features. When folks look up my hostname, they get an IP address (well, assuming my 2yo hasn't found the power button).

    6. Re:probably by missing000 · · Score: 4, Insightful

      It may not be "simple", but it is /powerful/.

      Do you live in a DOS shell? It's "simple" - so is driving a golf cart or programming in BASIC.

      Simple is not equal to good. Very few people would actually chose simple over capable any day.

    7. Re:probably by kfg · · Score: 5, Insightful

      It depends on what you mean by lazy.

      Ever see someone toss a coat on the floor rather than hang it up, and then go back later to hang it up anyway?

      Most lazy people create an extraordinary amount of needless labor for themselves and then berate people who have a lot of free time because of their efficiency "lazy."

      It's very peculiar.

      KFG

    8. Re:probably by Morth · · Score: 1

      But it's not really that hard to get a basic setup either. The default configuration file is typically setup for caching, so all you have to do is add your own zones. Isn't exactly super hard to copy the zone file and edit the A entries (plus a few more).

    9. Re:probably by Anonymous Coward · · Score: 1, Funny

      pfft, why should you ever go back to hang up you're coat when you've thrown it in a perfectly good spot.

      The normal course of action is to pick up the coat on the way out, if it's a stairway you don't have to even bend, just kick it to the stairs take a few steps down, reach out with you're arm and voila, all with the least lost of bodily fluids.

    10. Re:probably by kfg · · Score: 2, Insightful

      pfft, why should you ever go back to hang up you're coat when you've thrown it in a perfectly good spot.

      I haven't a clue, but people do.

      KFG

    11. Re:probably by Anonymous Coward · · Score: 5, Informative

      Exactly. What is so difficult about setting up BIND for an average site? I was able to set up BIND on Woody by installing the package, reading documentation for 15 minutes and then editing a few example zone files. And I have never ever set up a DNS server before (though I know quite a bit about how DNS protocol works).

      Now, I clicked on one of the links in this story and found that to configure tinydns (as an example) you have to learn some strange sendmail-like syntax:
      =www.panic.mil:1.8.7.99
      @panic.mil:1.8.7 .88:mail.panic.mil.:0
      Zpanic.mil:dns1.panic.mil:h ostmaster.panic.mil::72 00:3600:604800:3600

      Heh, WTF? I would have to learn this syntax and how it relates to common DNS terminology (A, CN, MX, ...) AND learn what the common DNS terminology means. In the BIND case, I only need the common terminology.

      All for all, I'd say BIND is used not only because it's default. It's default and sufficiently easy to use so most people do not feel the need to replace it. As a bonus, if there is a security problem, it is likely to be fixed REALLY fast upon discovery, which is a bit less probable for the other servers (because they are not used as frequently).

    12. Re:probably by gclef · · Score: 2, Interesting

      No. I'm running BIND because I want "delegate only" zones. When the other DNS servers can handle Verisign's obnoxiousness gracefully like that, then I'll look at moving. Until then, BIND stays on my DNS server.

      (ps: If there are any Gentoo folks reading, please get Bind 9.2.3 into portage properly. I got it installed on my machine by hand just fine, but emerge keeps trying to downgrade it to 9.2.2. That makes me unhappy.)

    13. Re:probably by petard · · Score: 1

      Yes, but then you've created a security hole on your network because you've configured the same DNS server for both recursive and authoritative lookups. Don't do that.

      --
      .sig: file not found
    14. Re:probably by Anonymous Coward · · Score: 0

      The inertia effect of being installed by default is significant, no doubt about it.

      The only reason I've looked into other DNS servers is that I had niche situations I was looking into, like virtual hosting (MyDNS), or firewall dns proxys (pdnsd, dnsmasq, and dproxy)

    15. Re:probably by Anonymous Coward · · Score: 0

      How is that a security hole? You mean it's not MORE secure, neither EQUALLY secure, so it has to be LESS secure? I can probably live with that cca 0.000001% of lower security... otherwise I would have to have a separate computer for every deamon I run. Running more daemons on a single computer creates similar "security holes".

    16. Re:probably by StupidGoose · · Score: 1

      Mac OS X includes Safari as it's default browser.

    17. Re:probably by dsojourner · · Score: 3, Interesting

      As I recall, djbdns has a licence that makes it hard to distribute: everything goes in weird places, and if you distribute the code you can't distribute changes (only patches). ... which might affect whether the major distributions would be interested.

    18. Re:probably by swb · · Score: 3, Interesting

      An interesting observation. On a related note, I've noticed that a lot of "messy" people seem to know where everything is. I call it the chaos theory of organization; it can often be easier to remember where things are than to spend the effort to put them someplace. So you just put them where there's space, and remember where they went.

      My wife has what I call the pro-aesthetic theory of organization; if a room or place appears to be neat, it's organized -- even if the stuff is put away without any regard to an organizational structure (eg, related items aren't in the same cabinet or closet). It's important for the room to look clean, even if in reality its a highly user unfriendly mode of organization.

      When you contrast the former and the latter, it's an interesting mix -- on one hand, you have a visual mess but things are relatively easy to find. On the other hand, you have visual neatness, but things are hard to find since there's no scheme (other than size and volume) as to where things went.

      As far as laziness goes, I've known neat freaks that never get anything done because the overhead cost of neatness eliminates their time.

    19. Re:probably by Anopheles · · Score: 1

      Laziness, by the way, is one of the 3 great virtues of programmers, according to Larry Wall.

      Don't knock laziness. It gets things done.

    20. Re:probably by olderchurch · · Score: 3, Interesting
      So I have to learn a more complex syntax. It took me half an hour (not taking the strange M$ lookup into account). The fact that you need to update your BIND software because of security related problems _at all_ is something I do not like. Take for example securtiyfocus' Vulnerabilities archive:
      BIND: 24 vulnerabilities (since 1999)
      TinyDNS: 0 vulnerabilities

      That's what I call a secure DNS server!

      --
      Disclaimer: This opinion was created without the use of any facts
    21. Re:probably by kfg · · Score: 1

      While you certainly raise some side issues that I have made some personal observations on (and which you might find addressed in Zen and the Art of Motorcycle Maintenance) if you go back and read my post again you might note that I very carefully crafted a specific example germane to the question I was addressing that has absolutely nothing to do with the issue of neat vs. messy.

      KFG

    22. Re:probably by Octorian · · Score: 1

      And the biggest problem with an artificially neat room is that you make a much bigger mess when you actually need to find something there. Then, if lazy, you take forever to clean this mess up. Thus, the room is perpetually messy and only clean for brief periods of time where demanded.

    23. Re:probably by bryanp · · Score: 1

      Yes, I know. It was mostly a joke. I find it amusing that it was modded as "underrated" instead of "funny."

      --
      "An unarmed man can only flee from evil, and evil is not overcome by fleeing from it." Col. Jeff Cooper
    24. Re:probably by petard · · Score: 2, Informative

      Not a separate computer, just a separate service. If you're running a public DNS service, you really should allow only recursive or authoritative queries. If you must service both, have the authoritative service listen on a 127.0.0.x IP and have the recursive one query that for the domain in question. But unless you're an ISP, there's really not a good reason to have your public nameserver handle recursive queries.

      Here's a bit more discussion of why it's a good idea to split your DNS. But like I said, it doesn't have to be a separate computer, just a different interface :-)

      --
      .sig: file not found
    25. Re:probably by walt-sjc · · Score: 3, Informative

      While bind may not be "super simple moron proof", It's also not that frigging hard either. Add on top all the various GUI management tools for it that make it not hard at all. Looking at some of the zones managed by clueless Windows (and linux) administrators using Active Directory or other tools, it's clear that some people need to read the O'Reilly DNS and BIND book. There is more to DNS than the server software - you need to understand WHAT the records do, and HOW to use them correctly. You also need to know how to use tools like dig and nslookup. Bind is only one part of the equation, and it's just not that hard to learn. While there are a lot of options, most people won't need but a few. There are MANY MANY good examples and tutorials.

      Bind is also rock solid. It doesn't die. I have servers that run bind that have been running for YEARS without a reboot, and bind has never needed to be restarted. The answer is quite simple. It's not THAT hard, and it works. Why change? Occasionally someone will find a security hole, so you patch and move on, just like everything else.

    26. Re:probably by Anonymous Coward · · Score: 0

      Impossible, Linux users are immune to that kind of thinking. Only Windows lemmings fall for those kinds of tricks. I am not a troll.

    27. Re:probably by walt-sjc · · Score: 0

      Software that so few use or look at is MUCH more likely not to have reported vulnerabilities. Doesn't mean that there aren't any. Since bind is standard on 99.9%+ unix like OS's and is supported by several large unix houses (IBM, HP, SUN, etc.) it's going to have LOTS of eyeballs looking at it.

    28. Re:probably by twoflower · · Score: 1
      My wife has what I call the pro-aesthetic theory of organization; if a room or place appears to be neat, it's organized -- even if the stuff is put away without any regard to an organizational structure (eg, related items aren't in the same cabinet or closet). It's important for the room to look clean, even if in reality its a highly user unfriendly mode of organization.

      Oh. My. $DEITY.

      Thank you for so concisely expressing exactly what my wife does as well. I've tried to come up with a good way of describing it in the past and failed -- but I'll never lack for this again.

      It drives me nuts, sometimes -- I go to look for something, and it isn't where I remember it being. Then I think hmmm, it was visible -- maybe she put it somewhere to get it out of sight and I have to start rooting through drawers, cupboards, etc. In most cases, it hasn't gone far, because it goes in the first hidey-hole that comes to hand instead of the most sensible place it might go, which might be in another room or even on another floor.

      Again, thanks.

      --


      --
      Twoflower
    29. Re:probably by fyonn · · Score: 1

      BIND: 24 vulnerabilities (since 1999)
      TinyDNS: 0 vulnerabilities

      That's what I call a secure DNS server!


      that is not a given. how many people actually use tinydns vs how many use bind? not to say that tinydns is not excellently programmed, but if no-one is really looking for flaws then they are unlikely to show up

      dave

    30. Re:probably by dinog · · Score: 1
      Perhaps it is because of the prophecy :

      One DNS to rule them all,
      One DNS to find them,
      One DNS to bring them all,
      And in the darkness bind them,
      In the Land of Internet, where shadows lie.

      Dean

      Those who say "Never say never" are clearly hipocrites.

    31. Re:probably by painandgreed · · Score: 2, Informative

      It depends on what you mean by lazy.

      Ever see someone toss a coat on the floor rather than hang it up, and then go back later to hang it up anyway?

      That's not laziness. That's called "time management".

    32. Re:probably by mellon · · Score: 1

      Right, 'cuz knowing this is _really_ going to help you to get along better with your wife. TBF, I think your best bet is to just proactively organize things in a way that's neat, but that may well be too much trouble.

      Anyway, what does this have to do with the DNS?

      BTW, Nominum's CNS product is a caching name server, so of course it's going to hose the averages - it's always going to be authoritative for zero zones. And I think it mostly lives behind firewalls, so you wouldn't be able to get a good count on the installed base, unfortunately. And one of ANS' real strengths is its ability to serve _really_ large domains efficiently. So once again, not going to look good when you're judging the product based on the deployed number of domains for which it's authoritative.

    33. Re:probably by Anonymous Coward · · Score: 0
      On a related note, I've noticed that a lot of "messy" people seem to know where everything is. I call it the chaos theory of organization; it can often be easier to remember where things are than to spend the effort to put them someplace. So you just put them where there's space, and remember where they went.


      The problem with a system of organisation is that you to remember the system in addition to how things fit into the system. In other words, if you forget the system, you're screwed.

      Mnemonics are similar. How do they make remembering things easier? Not only do you have to remember the mnemonic but you have to remember how to apply the mnemonic to get the information you want.
    34. Re:probably by Anonymous Coward · · Score: 0

      You missed the point of the parent post. The post isn't saying simple == good. He/She is saying that most people choose simple OVER good, because good (usually) is complex. He's agreeing with you, and you are misreading his post.

    35. Re:probably by Anonymous Coward · · Score: 0

      mkdir /etc/portage
      echo "net-dns/bind" >> /etc/portage/package.mask

      there have been some compile problems with 9.2.3, which is why its marked -x86 (unusable) instead of ~x86 (unstable). we're working on it.

    36. Re:probably by rthille · · Score: 2, Interesting

      Well, to be fair, you don't have to learn the syntax to get started, DJB created command line programs to do the 'normal' things like 'add-host' 'add-ns', etc.

      I had trouble figuring out BIND's zone-file format when I first installed it. But the main thing I had trouble with was trying to figure out which packets I wanted my DNS server to be sending out.

      DJB talks about not using CNAME, but it took me a long time to understand why.

      --
      Awesome furniture, accessories and cabinetry in Santa Rosa, CA: http://humanity-home.com/
    37. Re:probably by Anonymous Coward · · Score: 0

      you're == you are
      I think you meant "your", as in "belongs to you"

      Jesus. This one isn't that hard.

    38. Re:probably by dasmegabyte · · Score: 2, Interesting

      So why not use tinyDNS...which is both simple AND powerful, AND fast, AND secure.

      A good answer is "because the syntax is occasionally inscruitable." another would be "because DJB expects you by default to conform to HIS way of doing things, which is quite different from the bind way."

      But if you don't already know the BIND syntax...and you want a DNS server you will NEVER have to think about...tinyDNS is goddamn fabulous. So is qmail. The combination of the two means the only things *I* think about on my webservers are Apache, Tomcat and Courier-IMAP (which loves to crap out unprovoked, once every three months or so).

      --
      Hey freaks: now you're ju
    39. Re:probably by MesiahTaz · · Score: 1

      Not exactly. It's because djb actually knows how to write good, secure code. Look at qmail: lots of people use it, no vulnerabilities.

      --
      Are you an open source warrior?
    40. Re:probably by swb · · Score: 1

      It drives me nuts, sometimes

      Drives me nuts sometimes is an understatement. How about, "Drives me into fits of frothing homocidal rage"? I've generally tricked myself into appreciating her willingness to keep the house decluttered, but there are times when I desperately need $thing and find that she's arbitrarily "put it away", usually someplace totally illogical and the last place I look, and I tear the house apart, growing more and more pissed each time I demolish a "storage location" looking for something.

      I'll even admit to hiding something of hers on occasion, simply to make a point about her "organization." Which is totally juvenile, but it really represents how batty her lack of logic makes me.

      Thank you for so concisely expressing exactly what my wife does as well.

      I wish I had a *why* for it, though. There's clearly something going on about how the genders define cleanliness and the logic applied to organization. I sometimes suspect my wife doesn't even *care* about logical organization, or at least it doesn't enter her mind. I'm more concerned with logical organization than overall cleanliness, and I often find myself settling for "chaos" organization if the resources (containers, cabinets, etc) don't exist to logically organize.

    41. Re:probably by justMichael · · Score: 1
      On a related note, I've noticed that a lot of "messy" people seem to know where everything is. I call it the chaos theory of organization; it can often be easier to remember where things are than to spend the effort to put them someplace. So you just put them where there's space, and remember where they went.
      I got a chuckle out of that...

      But seriously, my wife always thought I had some magical powers. I never lose my keys/wallet/phone... I don't have some steel trap for a memory, maybe at one point, not anymore. I don't lose stuff because things are always in the same place. I get home, unload all my stuff into it's place and I'm done. There is no extra effort as the sideboard is right as you come in the door and that's where my junk lives.

      One of the biggest beneifts I find in this method is that I don't even have to think in the morning on the way out. The down side is if my phone starts bitching in the middle of the night and my wife puts it in the charger, I WILL leave without it ;)

      My wife is the other side of the fence, I can't tell you how often she loses her keys or has to chase the ringtone to find her phone.
    42. Re:probably by linzeal · · Score: 2, Insightful
      If you want logical organization you are going to have to label where everything goes, that has been my exp with past live in gf. Get a label maker and put labels on the bottom of drawers and on the inside of cabinet doors for each shelf and section of drawer. For large bulky items like christmas decorations put them on storage containers on at least 2 sides so that when you store them you can see what is in there.

      This is a fun weekend project as you get to walk around your place with your SO and figure out 'exactly' where things should go.

    43. Re:probably by Anonymous Coward · · Score: 0

      "Very few people would actually chose simple over capable any day."

      *chuckle* This said without regard to Windoze.

    44. Re:probably by perlchild · · Score: 1

      "People are lazy", and yes, that's why they use BIND, but not the kind of laziness you think.

      You're thinking of "ease of use" not "least amount of perceived work". Looking for a software that does a particular task is considered "work"!!!! by many people(I'm shocked myself) which is why laziness is why more people use IE (not necessarily because it's easier to use or makes your tasks easier) but because there's little work "up front" in installing/integrating. And yes, the fact that many distros include graphical admin tools that depend on bind, and only really work on bind does not help. I'm a powerdns addict myself.

    45. Re:probably by ncc74656 · · Score: 1
      If there are any Gentoo folks reading, please get Bind 9.2.3 into portage properly. I got it installed on my machine by hand just fine, but emerge keeps trying to downgrade it to 9.2.2. That makes me unhappy.

      You could write an ebuild and submit it to Bugzilla. You probably don't even have to write it from scratch...take the 9.2.2 ebuild, tweak it a bit if necessary, file it under /usr/local/portage, and try it out.

      (I would do this, but I don't use BIND...I use djbdns. I put in ebuilds for MythTV 0.15 and a couple of smaller packages using the aforementioned method, though. A fair bit of the time, you can get by with just copying the ebuild without any changes (the program version frequently isn't hardcoded anywhere in the ebuild).)

      --
      20 January 2017: the End of an Error.
    46. Re:probably by bugnuts · · Score: 2, Interesting

      It may come standard on 99.9%, but it's only used by 70%, vs 15% tinydns. Plus, the source is not available on 99.9% of the distributions -- it's almost always a binary. E.g, I have NEVER seen sun distribute the source to it in their distributions.

      Lots of people would've eyeballed tinydns for bugs, which IIRC (and I might not), is not available in binaries. Plus, the security is guaranteed!

      The djbdns security guarantee
      I offer $500 to the first person to publicly report a verifiable security hole in the latest version of djbdns.

    47. Re:probably by gclef · · Score: 1

      I've already done the modify-9.2.2-ebuild-to install-9.2.3 bit. That's how portage knows that Bind is there at all on my machine.

      The problem is, 9.2.2 is the most recent version by portage's knowledge, and it keeps trying to downgrade it (which means I can't just blindly "emerge world", or portage will downgrade bind).

      An AC responded earlier stating that apparently there's some compile problem with 9.2.3 (can't say I've ever heard anyone complain about it, and I know lots of folks using 9.2.3), which has the gentoo folks marking 9.2.3 as unusable. Since it's not clear to me what the compile problems are (I've not seen any), I can't help solve them.

    48. Re:probably by Oopsz · · Score: 1
    49. Re:probably by Onan · · Score: 1

      Actually, tinydns's syntax is immensely easier than bind's.

      In either case, someone could easily take a look at an existing zone and add a few A records. But creating a new bind zonefile from scratch is filled with intricacies, subtleties, and just plain weirdnesses that no sane person should have to know. Yes, you have to put the domain contact's email address at the top, and yes, that looks like another record, because we decided to substitute another . for the @, for some random-ass reason. Yes, you have to manually create your own forward and reverse records, even though there is only one valid combination that could exist. Yes, reverse entries (usually) need to use the fqdn and end in a trailing dot, even though the forward entries don't. Yes, you have to get the every syntax detail correct in every file, or the nameserver will refuse to serve any queries at all.

      The problem with tinydns is djb's suckass documentation. And the first problem with djb's suckass documentation is that it makes the syntax look immensely harder than it is. The only examples he gives are of crazy edge cases, obscure and complex things that most people would never want to do. Presumably he's more interested in showing off the flexibility of his software, and all the unusual things it can handle, than just clearly showing people how to specify a goddamn A record.

    50. Re:probably by strobert · · Score: 1

      hmm.. lesse I run (on the work servers) bind, postfix, and courier-imap (imap on different servers since we don't run IMAP for public use -- not sure why you are running any DNS or IMAP on your "web servers", but that is another matter). Never have to think about them. bind's syntax ain't bad. I recall way back when people telling me BIND was too obtuse. I actualyl picked up its syntax far quicker than qmail. yeah it is not very englishy, but maybe that is why it is easier for me (I program in C, C++, perl).

      As for fast, powerfull and secure. never noticed speed issues. it lets us easily manage hundreds of domain names. we havea distributed name servign environment with a mix of internal/external nameservers, resolvers, etc. We set it up, and it just works.

      And as for security I have had FAR more many security updates in openss[lh] in the past 2 years than I have had with bind. In fact I don't recall the last security updated for bind9.

      One thing people don't recall is BIND's history. Bind4 was more of initial prrof of concept, written back when people assumed they could trust their neighbors on the Internet (because pretty much back then you basically could). Bind8 was a evolution of Bind4 to have the newer better features from the RFCs. But it still had Bind4's legacy issues. Bind9 is a complete rewrite. so it is like the new alternative guys out there in terms of being written with security in mind.

      oh, and for us courier-IMAP stays up fine, on the office servers we run it on (aka the user servers).

      we had qmail running originally handling a fraction of e-mail the postfix servers now handle (used to have most inbound e-mail handled directly by an Exchange server) and I spent many a holiday babying the server back to health. Now this was a server I inherited, so it may have been setup wrong.

      so this comes down to your mileage may very. For us having system tools that don't try to fight unix, and work with the other parts of the system (init scripts, directory layout, log rotation, etc.) makes it far more easier to maintain and put on auto-pilot.

    51. Re:probably by Onan · · Score: 1
      I have servers that run bind that have been running for YEARS without a reboot, and bind has never needed to be restarted.
      And congratulations on those nice, juicy, rootable systems. I wonder what else they're running?
    52. Re:probably by akac · · Score: 1

      He said NEEDED to be rebooted. He probably has rebooted them for kernel updates and such, but that wasn't a requirement.

    53. Re:probably by walt-sjc · · Score: 1

      And you know they were "rootable" exactly how? You DO realize that Unix is Not Windows and you can patch most of the OS without rebooting, right???

      Of course it's obvious that you completely missed the point of my post, instead choosing to troll. Nice.

    54. Re:probably by Anonymous Coward · · Score: 0
      Software that so few use or look at is MUCH more likely not to have reported vulnerabilities.
      Big talk. Find a vulnerability in djbdns to back up your point. Until then, I don't believe you. How many people have done full audits of the Bind source code? How many people have done a full audit of djbdns source code? Those are numbers that I would think would be relevant, in addition to the authority of the auditors. I could give you lower bounds in both cases, but I don't know what the totals would be. Also, how easy is it to audit both source bases? djbdns-1.05 contains 10,210 SLOC, and bind-9.2.3 contains 221,268 SLOC(this data was generated using David A. Wheeler's 'SLOCCount'). This indicates that any bugs in djbdns would probably be easier to find.
    55. Re:probably by dasmegabyte · · Score: 1

      YMMV? Boy I'll say. I have never seen a server that ran better with postfix than qmail. What I have seen is one underpowered qmail server do the work of three Exchange boxes. Getting it to work with active directory was hella tricky, but that's a samba thing, not qmail's fault.

      qmail lends itself handsomely to domain management because it groups standard functions together. You can create all of the information in a standard BIND record -- A records, MX records, PTR records, SOA data, etc -- with only two short lines in a qmail config file. Once you figure out what the hell you're doing (not easy...took me three days to figure how to get it working the way *I* wanted it), doing it again is simple.

      And as for why my "webserver" is running DNS and IMAP -- we handle virtual hosting for many low traffic domains. The easiest way for us to control them is to manage all of the services and all of the data for a domain on a single server. One server can comfortably handle a hundred or so such domains without feeling the load in the least. And if that domain gets too big for its britches, it can be moved to a new server very quickly...in fact, we assemble the data in a sort of a "packet," so you can copy the directory foo.domain.com from one server to the next and (after a rebuild of dynamicly generated config files and a graceful reload) have the new server take over all the functionality of serving the domain.

      So really, each server is a webserver/email server/dns server/database/ftp server. It's not the most efficient way to handle any of these functions, and I suppose if I were a CCNA or some gibberish like that I'd be appalled...but this is just a part time thing and it seems to work very well.

      --
      Hey freaks: now you're ju
    56. Re:probably by sudog · · Score: 1

      Until one day you suddenly realise that you've traded a pile of required functionality for some extra security and the onerous distribution clauses that guy attaches to his software.

      There have already been four or five distinct situation in which, had I been running qmail, large volumes of customer data would have to have been destroyed.

      No, thanks.

    57. Re:probably by GoneGaryT · · Score: 1
      Right on, bro'.

      Good firewall rules and BIND config acl keep the shit at bay. We ran 8.1.2 as a primary for long past its sell-by date, but good acl and f/w kept it safe. It all depends on who you trust and who you don't.

      Links recht 2 3 4

    58. Re:probably by rainer_d · · Score: 1

      can you elaborate ?

      --
      Windows 2000 - from the guys who brought us edlin
    59. Re:probably by EsbenMoseHansen · · Score: 1
      The problem is, 9.2.2 is the most recent version by portage's knowledge, and it keeps trying to downgrade it (which means I can't just blindly "emerge world", or portage will downgrade bind).
      If you don't mind going for the ~x86 packages for bind, you could use
      echo net-dns/bind ~x86 >> /etc/portage/package.keywords
      This link is your friend
      --
      Religion is regarded by the common people as true, by the wise as false, and by rulers as useful.
    60. Re:probably by Onan · · Score: 1

      If you know of a way to upgrade kernels without rebooting, or bind without restarting the daemon, I'd love to hear about that.

      If you don't have such fu, then either your systems and services have needed to be rebooted and restarted, or you're using years-exploitable versions.

    61. Re:probably by Anonymous Coward · · Score: 0

      And the masses choose Microsoft windows why?!

    62. Re:probably by mysticalreaper · · Score: 2, Informative

      I know the problem, and i have a solution

      A) the maintainer is a dink, and won't upgrade, plus the interested parties seem to like to whine and complain about weird craziness and misnamind of files (both problems non-existent IMHO) instead of upgrading. There's a bug about the compile problem, solaris only, as i remember. Why is it out of x86 then? Exactly. Gentoo was once great for being more current than anyone, but has been slipping, sometimes severely, as in this cae.

      B) use the -U flag. like so "emerge -Upv world"

      That -U is upgrade-only. I use it all the time, that way portage doesn't downgrade. Also, yes, 9.2.3 has been out for something like 8 months now, using 9.2.2 is starting to look downright silly.

    63. Re:probably by Anonymous Coward · · Score: 0

      The point of BIND being powerful is only relevant in this discussion if it were relatively powerful.

      And so your point must also be that BIND is relatively more powerful than the other simple solutions. Which it is not.

      And now we throw in the issue of vulnerabilities. Ha. Powerful also does not equal good, especially when it is power you are giving to remote attackers.

      And people do in fact choose simple over /powerful/ every day.

    64. Re:probably by CmdrTHAC0 · · Score: 1

      On a related note, I've noticed that a lot of "messy" people seem to know where everything is.

      For me, my memory works best in the time domain. If I have several piles of stuff, all the items in the pile have temporal locality. So when I need something, I can quickly find the right pile because I remember when I last needed it, and the piles provide that information.

      Once I figured this out, I developed an excellent algorithm for those concentration/memory games (e.g. on cell phones.) I spiral around the outside ring, and when I see a symbol the second time, I can generally get back to the original in one attempt.

      --
      __CmdrTHAC0__
      In Soviet Russia, Spanish Inquisition doesn't expect YOU!!
    65. Re:probably by Anonymous Coward · · Score: 0

      The problem is, 9.2.2 is the most recent version by portage's knowledge....


      That's one example of what a portage overlay is for. From thy shell prompt, assuming no changes needed made to the ebuild:

      mkdir -p /usr/local/portage/net-dns/bind
      cp /usr/portage/net-dns/bind/bind-9.2.2.ebuild !$/bind-9.2.3.ebuild
      ebuild !$ digest

      Don't forget to set PORTDIR_OVERLAY=/usr/local/portage in /etc/make.conf.

    66. Re:probably by Anonymous Coward · · Score: 0
      While the "parsing friendy" (as opposed to "user friendly") syntax of the the tinydns data file may be hard to understand at first, once you learn it it's quite easy to work with. Easier than BIND IMO.

      However, there are several web-based data file editors listed on www.tinydns.org that make dealing with the data file MUCH easier for newbies.

      Also, some of them, including VegaDNS, allow for a multi-user admin environment for tinydns by storing the data in a MySQL database, and dumping that database to the data file regulary via cron. VegaDNS even allows for importing domains via AXFR.

      So to me, such tools make it easy for newbies to take advantage of the speed and security of djbdns without the necessary learning curve.

    67. Re:probably by tigga · · Score: 2, Informative
      So why not use tinyDNS...which is both simple AND powerful, AND fast, AND secure.


      You may use it at home.. That's it. I would not call powerful DNS server which does not have idea about zone-transfer requests, inverse queries, non-Internet-class queries (queries list from DJB's page).


      As for qmail - it's pretty inconvenient to patch it every time I need any new functionality. Qmail is pretty simple and doing complex things is quite frustrating with it.

    68. Re:probably by tigga · · Score: 1
      In either case, someone could easily take a look at an existing zone and add a few A records. But creating a new bind zonefile from scratch is filled with intricacies, subtleties, and just plain weirdnesses that no sane person should have to know.

      So why don't you copy new zone from another and replace appropriate names?

    69. Re:probably by Anonymous Coward · · Score: 0


      but if no-one is really looking for flaws then they are unlikely to show up


      The most striking and important thing about the djb code is how little there is of it. I am a tinydns/dnscache user and I have grokked the entire codebase for this product, and I'm not bragging, it was a cinch. (One thing to notice, is while DNS is actually conceptually simple and grokking a well written DNS service is easy, you realize that writing a network application CORRECTLY is very difficult). BIND, on the otherhand (even 9), is a piece of garbage. BIND8 was a POS because it screamed of being written by inexperienced programmers with a patchwork of kludges over time. BIND9 has a different problem of both second system effect and the effects of being written by an overly large committee like team.

    70. Re:probably by huskymo · · Score: 1

      It's not "BIND's zone-file format"--it's master file format, as described in the RFCs. Anything that calls itself a DNS server ought to read master file format (and optionally other formats).

    71. Re:probably by huskymo · · Score: 1

      Don't blame BIND for DNS's master file format. BIND reads the format described in the RFCs, not a format coined specifically for it.

      I won't deny that master file format is subtle and fraught with occasion for error, but it's also the lingua franca of zone data. Anyone working with DNS should understand it. It's the format query tools like dig produce, for one. How can you expect to understand dig's output if you can't read master file format?

    72. Re:probably by brakk · · Score: 1

      That sounds very familiar, although I think I actually use a combination of space/time to find things.

      When I was living in a dorm and there wasn't enough room to spread out, the only place to go was up. When I was looking for something, I would remember how long ago I last saw it and then know which layer to look for it in.

    73. Re:probably by Solandri · · Score: 1
      The problem with a system of organisation is that you to remember the system in addition to how things fit into the system. In other words, if you forget the system, you're screwed.

      My "messy system" just involves putting stuff near where I need it, temporally stacked. Photo scanning stuff (compressed air, brush, pending slides, etc) goes next to the scanner. Computer stuff goes next to the computer. Stuff I need while reading books goes next to the books. etc. I imagine most "messy" people are like that too - favoring efficiency over cleanliness (less time spent getting and returning stuff from/to its storage location since it's already right where you need it). It's pretty hard to "forget" this "system" unless you forget what you want to do.

    74. Re:probably by macdaddy · · Score: 1
      The fact that you need to update *insert-software-package-name-here* because of security related problems _at all_ is something I do not like.

      I would describe a person such as yourself as a lazy, inefficient and piss-poor systems administrator that give us good administrators a bad name and make our jobs much more difficult. You're as bad as the Windows cronies that can't find the time in their oh so busy daily schedule to apply software patches and updates.

    75. Re:probably by Anonymous Coward · · Score: 0

      Gee fella, don't loose your cool...

    76. Re:probably by sudog · · Score: 1

      Sure-last I looked, qmail mail queues are tied to the inode of the disk they're on. Try moving them around to a new location or a new machine. At the time I had to do it with sendmail, I learned very graphically that one of the sister machines (running qmail) required very careful handling. Obviously it's not impossible, nothing's impossible, but with sendmail it was *easy* and *painless.*

      Also, without extensive patching the base qmail doesn't do virtual mail hosting so well. There are no support utilities and the delivery mechanism leaves.. a little to be desired.

      I mean, sure, you can talk about the base qmail being ultra-secure: but then what can the *base* qmail actually accomplish? Very little for an enterprise. That's why nobody big uses the base qmail at all--it's all qmail+patch, or postfix or exim or sendmail.

    77. Re:probably by rainer_d · · Score: 1
      [snip]

      What does that have to do with having to destroy customer data ? If I may ask ?
      And yes, queues are "fixed" you can't backup them, you can't move them.
      Also, qmail without patches is pretty useless other than a single mailhost.

      I think that postfix is very nice - but when it comes to virtual hosting, there are just not so many ready-to-go tools for user-management etc. out there. It's all for qmail (+patches, admittedly). But as with most other open source products, there are people dealing with this specific problem.

      Rainer

      --
      Windows 2000 - from the guys who brought us edlin
    78. Re:probably by sudog · · Score: 1

      In the world I live in, email is customer data (in the sense that the customer owns the data or expects to have access to the information contained therein and even pays for the privilege) and if the main mail server dies or must be moved to a new system, a qmail installation would prevent this from happening, and thus the mail queues would be lost.

      This is not a good thing.

  2. arrr! by Baka_kun · · Score: 0, Insightful

    the old mighty conservative geeks wins again!

    1. Re:arrr! by WesG · · Score: 1

      And lets not forget those silly sendmail geeks :P

  3. De Facto by the_mad_poster · · Score: 5, Insightful

    Becuase no matter what ridiculous flaws it has in it, it's the de facto standard by which all other (frequently superior) systems are measured. People figure "gee.... I wanna learn DNS servers", they think BIND. They think "gee.... I wanna learn SMTP servers". They think sendmail.

    It's the same flawed system that supports Windows, but executed to a much greater extent. People are familiar with it, so despite the fact that BIND and sendmail are absolute abominations, they get used.

    The geeks bitch about people using Windows even though "such far superior" systems exist as alternatives, but we keep using the horrendous abortion that is BIND even though there are superior alternatives that are free. I guess we can't stand the taste of our own medicine, hm?

    --
    Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    1. Re:De Facto by Tet · · Score: 5, Interesting
      People are familiar with it, so despite the fact that BIND and sendmail are absolute abominations, they get used.

      Sigh. Y'know, I really should get used to sendmail FUD on Slashdot, but here I am feeding the trolls anyway. I use sendmail because it's better than the alternatives, and it's far from an abomination. I'm not going to claim the syntax looks good at first glance, but then most perl programs look like line noise too, yet the Slashdot crowd doesn't seem to have a problem with that. When other MTAs can match Sendmail's flexibility, then maybe I'll consider switching. But not before.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    2. Re:De Facto by robslimo · · Score: 2, Interesting

      ...no matter what ridiculous flaws it has...

      Did you see the version results for BIND? There are some really ancient ones out there. 1.971% are version 4.9.3 to 4.9.11

      I haven't checked any vulnerability databases on it, but that seems pretty old... too old to have patches available?

    3. Re:De Facto by MrMickS · · Score: 1
      The basic statement that BIND is used because it is a defacto standard is a good one. The rant that follows doesn't help the argument.

      Could you please define what you mean by superior?

      --
      You may think me a tired, old, cynic. I'd have to disagree about the tired bit.
    4. Re:De Facto by winchester · · Score: 2, Insightful
      False arguments. At least the possibility for people to run other software in full compliance with the published standards (RFC's), thus providing full interoperability exists.

      With windows, you do not get that choice... either you use what Microsoft provides you or you don't use it at all. There is no choice. On Unix, there is.

    5. Re:De Facto by Psiren · · Score: 3, Insightful

      When other MTAs can match Sendmail's flexibility, then maybe I'll consider switching. But not before.

      I haven't used sendmail in years, having switched over to exim a long while ago. Out of interest, what does sendmail offer you that exim doesn't?

    6. Re:De Facto by stephenbooth · · Score: 4, Insightful

      There's also the fact that, due to it's current dominance, if I buy a book about DNS it probably assumes BIND. Therefore in a lot of people's heads BIND = DNS. Heck, for that very reason if I had to set up a DNS server (I'm not a networking expert) I'd select BIND as then I know that there's going to be examples in a book I can adapt to suit what I want to do. If it's not my core area then I don't want to have to spend hours learning how to configure a system, I just want to copy something out of a book and for it to work. Looking at the MyDNS site that has a second strike against it, it requires MySQL. Not only do I have to learn to setup and configure the product I actually want but I also have to learn another unrelated product! At least BIND uses text files, I know how to edit those.

      Stephen

      --
      "Don't write down to your readers, the only people less intelligent than you can't read" - Sign on Newspaper Office Wall
    7. Re:De Facto by Total_Wimp · · Score: 5, Informative

      When other MTAs can match Sendmail's flexibility, then maybe I'll consider switching.

      I think you hit the nail on the head. These big, some would say bloated, systems end up getting used because they're flexible. Others are constantly writing 3rd party stuff that specifically use these systems.

      Case in point: Microsoft ADS is very DNS dependant and the only DNS they support besides Microsoft DNS is BIND. BIND may, or may not be the best DNS out there, but because it's the standard people are building their systems to, it is almost certainly the most compatible and, by extension, the most flexible.

      TW

    8. Re:De Facto by SWroclawski · · Score: 5, Interesting

      Please tell me something Sendmail does that Postfix doesn't.

      I'd argue Postfix is more modular, more simple to configure, more respectful of system resources, more secure and more flexible than Sendmail.

    9. Re:De Facto by Apreche · · Score: 5, Insightful

      True that. But in addition, because it is the de facto standard, its what they teach college students in IT classes. I'm a CS major, and I know quite a few IT majors around here. If you asked most of them to set up a DNS server they could. If you asked how they would say "the bind command". Because they are all windowsy, they don't realize bind is a piece of software that is replaceable. They were taught how to do things a certain way, and they don't know to do it differently.

      Not all IT majors are that dumb, some of them deserve some credit.

      The other problem is that old pain in the butt standard programs like bind and sendmail are feature complete. Because they are old and used by tons of people they have all the features in them, workin properly. It may be a horrid pain in the ass to make them work, but it can be done. And while there are many nice new alternative programs that serve the same functionality in an easy clean fast way. You'll be hard pressed to find one that can do everything. I can't tell you how often Who will use a piece of software that they know is terrible, will admit to it being terrible, even complain about it being terrible, because it is the only one with a single feature that is necessary. Made up Example: One website someone visits often only works in IE. They love Firefox, but its too much of a pain to visit that one site.

      There's some guy out there using bind who wants to use something else, but can't because he needs one tiny feature that nothing else has. This is a major weakness of Open Source because since software is under constant development and bug fixing and security hole patching is priority, few programs ever become feature complete.

      --
      The GeekNights podcast is going strong. Listen!
    10. Re:De Facto by AKnightCowboy · · Score: 1
      People figure "gee.... I wanna learn DNS servers", they think BIND. They think "gee.... I wanna learn SMTP servers". They think sendmail.

      Naw, Bind 9.x is quite good and I love it. It probably helps that EVERYONE uses it so it's easy to standardize on it's zone file format. As for Sendmail, that's the biggest pile of shit mail system I've ever used and I have never looked back since switching my systems to Postfix. Bind on the other hand is acceptable.

    11. Re:De Facto by compass46 · · Score: 1

      OpenBSD up until 3.5 has used BIND4 by default. It was their own self maintained fork of the program.

    12. Re:De Facto by Zapman · · Score: 1

      I certainly haven't looked at all the contenders in the DNS space... However, most of them are missing some requirements of the RFC.

      The most glaring example is djbdns not implementing zone transfers. I am well aware of his answer of 'use rsync over ssh', but that's not acceptable. The RFC dictates that zone transfers be possible, so they should be possible. If there's a problem with the RFC, then it should be updated... They're called 'REQUEST FOR COMMENTS' for a reason.

      That said, it's perfectly possible to set up a secure DNS environment with BIND. It's part of my job.

      If you like, there's a good template for a named.conf file at:

      http://cyberbuzz.gatech.edu/jprice/named/named.c on f

      --
      Zapman
    13. Re:De Facto by CrankyFool · · Score: 4, Insightful

      After about ten years of using Sendmail (I was using Sendmail back when you had to understand rulesets and how to hack LHS/RHS of rules), I switched to Postfix. I am happier than a pig in mud for a whole bunch of reasons and consider Postfix a superior MTA.

      I have at least one acquaintance who, on his very large enterprise, runs Sendmail at the edge (and Exchange internally, but that's not his choice). Why? Because that way, he doesn't need to worry about separate patch management for his MTA -- Sun makes sure his MTA is up to date, and he doesn't have to document "this is how to install the MTA" separately.

      Is he using an inferior MTA? I believe so. So does he. But the ways in which Sendmail is less good don't affect him nearly as much as the way in which it is better -- by lowering maintenance costs (or, really, just rolling them into the ridiculous amount he pays Sun -- though he could get the patches for free, of course).

      With respects to my fellow sysadmins here -- obviously, some of you are vastly superior to me in all matters technical -- we really should know by now that sometimes, we make technical decisions for reasons that are not purely technical. The reasons people choose Sendmail over Postfix are usually in that sort of category, as well as the reason people choose BIND over other DNS servers (BTW, BIND is also the default DNS server on Solaris).

      I don't see this as a huge problem, except for (I guess) people who take it personally that not 'enough' people use the software they developed with great effort (though I don't see Wietse complaining "more people should be using Postfix!"). Unlike the Windows situation, it's not like the fact that, likely, most people I communicate with use Sendmail means I'm forced into using Sendmail. UNIX-based MTAs (Sendmail, Postfix, qmail, exim, other custom MTAs) mostly seem to be fairly standards-compliant, much like DNS servers (go ahead. Point out some obscure thing that 99% of people don't use where BIND doesn't follow the spec, just so I can laugh at you). So BIND and Sendmail dominate? Fine. I'll still run Postfix and ... well, BIND. Who cares?

    14. Re:De Facto by jonadab · · Score: 1, Insightful

      > I'm not going to claim the syntax looks good at first glance

      The major objection to sendmail isn't syntax; it's security. sendmail is on
      the very short list of programs I disallow on my network for security reasons.
      Its security track record is every bit as bad as IIS, and the problem is a
      core problem with the philosophy of the developers: they patch specific
      vulnerabilities, but they don't have any interest in fixing the core design
      that _leads_ to all those vulnerabilities.

      Fundamentally, sendmail runs as root while processing untrusted data arriving
      from the internet. That's a major fundamental security no-no. You just don't
      *do* that. Apache doesn't do that. proftpd doesn't do that. There's no
      *need* to do that, but sendmail does it anyway for arcane historical reasons.

      > but then most perl programs look like line noise too

      Now *you're* trolling. The only Perl programs that look like line noise
      are the ones that are deliberately obfuscated, like my signature.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    15. Re:De Facto by ChristTrekker · · Score: 1
      Therefore in a lot of people's heads BIND = DNS. Heck, for that very reason if I had to set up a DNS server (I'm not a networking expert) I'd select BIND

      With BIND's reputation in the (in)security department, I'm looking for a non-BIND DNS. Right now I only want DNS for my LAN where it would be perfectly safe to run BIND, but why should I learn something I wouldn't want to deploy later when it matters?

    16. Re:De Facto by jonadab · · Score: 1

      > Perl programs ... are deliberately obfuscated, like my signature.

      Uh, like my *former* signature, which I replaced with something else now.

      --
      Cut that out, or I will ship you to Norilsk in a box.
    17. Re:De Facto by lewp · · Score: 1

      OpenBSD included BIND 4 up until relatively recently (they went straight from BIND 4.x -> BIND 9.x in the base system IIRC).

      Version numbers and release dates escape me, but I don't think it was too terribly long ago.

      Not that these machines are necessarily OpenBSD boxes, but you find it popping up a lot in roles like this. Things that are critical but not very visible.

      Likely even if this is the case these systems are out of date. That said, they're not necessarily ancient.

      --
      Game... blouses.
    18. Re:De Facto by lewp · · Score: 1

      My OpenBSD 3.3 box has BIND 9.2.2 as part of the base system. I can't remember if I previously upgraded from 3.0, 3.1, or 3.2; but whichever one it was I believe that version included BIND 4.

      Of course my 3.5 CDs just showed up in the mail a few days ago. About time to do another upgrade :).

      --
      Game... blouses.
    19. Re:De Facto by Tet · · Score: 1
      Please tell me something Sendmail does that Postfix doesn't.

      Selectively route some mail by sender rather than recipient. This is possible in Postfix, using sender_based_routing=yes, but only as an all or nothing affair. I need to be able to send mail from certain senders via one route, but all other mail using a different route, based on recipient as normal. This isn't a contrived example, either. We have a legitimate business need to do that, and sendmail lets us do it.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    20. Re:De Facto by daviddennis · · Score: 3, Insightful

      As others have said, I think the main reason people use BIND is that it's in all the examples in the standard books (mainly O'Reilly) we use to learn.

      I was unaware DNS servers really needed much in the way of features for most people. In fact, I thought it was about the simplest thing in the world - get a request, look it up in a table and return the results. Not exactly rocket science, and the BIND configuration file's pretty ugly looking if my memory serves.

      I think overcomplexity is one of the biggest problem with the software world as it is today. It's worst on Windows, of course, but Sendmail and BIND are proof that Unix has similar problems too.

      D

    21. Re:De Facto by Alioth · · Score: 1

      I wouldn't say BIND is a pain in the butt; actually, I find it rather easy to administer. Sendmail on the other hand...switched to Exim about 3 years ago and haven't looked back.

      I'd also argue that the feature-complete weakness is true with proprietary software; they are just better at papering over the feature incomplete bits so people don't see them.

    22. Re:De Facto by Anonymous Coward · · Score: 2, Interesting

      Out of interest, what does sendmail offer you that exim doesn't?

      For me, operational changes that would require programming in exim, but require only tweaking sendmail.cf.

      Example: I recently added some anti-spam rules to restrict the HELO of connecting mailservers. If it's malformed, or matches against a blacklist of 'known bad' signatures, I reject the mail. In sendmail, this was trivial (err, well - as trivial as hacking your sendmail.cf can be :o)

      I'm not saying it's for everybody - it requires a very high level of knowledge - but it's safer (no worries about buffer overflows in code I add myself, etc.) and simpler than modifying the program itself.

    23. Re:De Facto by Tet · · Score: 1
      Now *you're* trolling. The only Perl programs that look like line noise are the ones that are deliberately obfuscated

      Nice try, but my real world experience proves you to be wrong. Sure, it's perfectly possible to write clean perl programs -- I've done so myself. But I ban its use on our production systems simply because it's just too easy to write line noise, and I don't have the time to verify all the code that my team write to ensure it's readable.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    24. Re:De Facto by the_mad_poster · · Score: 3, Interesting

      Yea, ok Tet. I'm a troll and that's FUD. It's not like sendmail really is a total piece of shit.

      Don't give me shit about Perl either. I can write totally unreadable code in C, Perl, Python, PHP, VBScript, Vb6, C++, Java, shell scripting, and QBASIC. I can also write clean code, readable code in all of them.

      It's not FUD, most Slashdotters just have their heads so far up their own asses that it just looks like they sit on top of their necks. Morons around here bemoan Microsoft for its shitty security, then they run out every other day to patch BIND or sendmail. Even assuming you're the 1 in 20 person who actually has a need that only sendmail can meet (which I doubt you are given the odds), the fact that you would suggest that saying sendmail has shit poor security is just "FUD" just serves to prove the point that you're just another one of the idealogical nutjobs that frequent this place.

      Give it a rest. It's not FUD because it's true. Sendmail blows a left donkey's swollen nut when it comes to security, usability, and reliability. Just deal with it. While you're at it, ask yourself if you even really need sendmail, or if you're just too lazy to make the switch to something that actually works.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    25. Re:De Facto by the_mad_poster · · Score: 3

      Nice try, but my real world experience proves you to be wrong.

      Holy shit... you're a real gem...

      MY experience is that people who use sendmail might as well just generate their configuration files using /dev/urandom. I guess MY real world experience proves YOU to be wrong, so now you're going to stop using sendmail, right?

      I also like how the guy that you responded to got pinned as a troll. See, on Slashdot, the fact that sendmail is a total piece of security shit doesn't matter. All that matters is that MICROSOFT programs have lousy security.

      I suspect this is because 95% of the people on Slashdot that actually talk don't know shit about computing, but they spit the same old idealogical mind dumps that appear in every Microsoft/Linux/SCO article and get excellent karma and mod points. Then, they run around and mod down anyone who doesn't say exactly what they were saying before. I mean, god forbid an intelligent post appear that doesn't exhort the many virtues of OSS! After all, with a license like GPL/BSD, it HAS to be good..... right?

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    26. Re:De Facto by the_mad_poster · · Score: 1
      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    27. Re:De Facto by the_mad_poster · · Score: 1

      The Windows statement references the mentality of choosing a tool that's familiar over the tool that's actually best for the job. It does not compare technologies used in Windows to those used in BSD, Unix, and Linux systems.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    28. Re:De Facto by walt-sjc · · Score: 3, Informative

      what does sendmail offer you that exim doesn't

      As someone who used to run sendmail (from the late 80's to 2002 before switching to exim) it gives you native support for UUCP!! It also gives you good brain excercises so you can do things like complex regular expressions, the US tax code, etc. :-)

      Seriously, if you really need to customize sendmail, you need to understand the rewrite rules in depth which are quite bizzare to someone not familiar. Adding additional functionality like sql DB lookups for virtual users with SMTP Auth, etc. can be a challenge for even the more seasoned sendmail admin. Once you get beyond the simple soho stuff, sendmail becomes quite awkward to work with. Sendmail Milter's is a horrible interface. Add on message archiving, spam / virus filters, special handling for certain addresses / domains, etc. and exim really starts to look good. Unless you are a full time mail administrator, you probably have better things to learn than sendmail syntax, and that's the bottom line.

      Bind is no sendmail. Bind's syntax is actually quite clean - more like apache or exim than sendmail. There are no bizzare ruleset's to learn - it's more like defining a structure in C.

    29. Re:De Facto by Anonymous Coward · · Score: 0

      Bind 4 is a separately maintained branch from the main tree which is currently 9.3.0beta4. 4.9.11 is the current version still available at isc.org. People still run bind 4 because its stable and secure, they don't need new features and they don't want to rewrite their config files.

    30. Re:De Facto by Smallpond · · Score: 1

      get a request, look it up in a table

      You can do that with a host table, you don't need DNS.

      Oh. Its too big? Maybe you want a server somewhere.
      Oh. It needs to be reliable? Maybe you need master and slave servers.
      Oh. Now you want to distribute it across lots of servers? Now you want DHCP and dynamic updates? Now you want authentication and remote management?

      Maybe its just more complex than you think.

    31. Re:De Facto by Oopsz · · Score: 1

      I don't know about other MTAs, but postfix has out of box support for UUCP :)

    32. Re:De Facto by Oopsz · · Score: 1

      DNS servers standards compliant? Only Bind. djbdns doesn't even support zone transfers..

    33. Re:De Facto by walt-sjc · · Score: 1

      Exim does that. Exim seemed to be just a wee bit more flexable than postfix which is why I went with it to replace sendmail. I have a Very complicated setup as far as routing, filters, AUTH, SSL/TLS, spam / av, etc. goes. The difficulty of doing all that in sendmail is the whole reason I dumped it after using it for almost 15 years. It just wasn't maintainable anymore. That, and I couldn't find anyone else that could work with the sendmail cf files - how the hell do you take a vacation???

      Again I have to reitterate, bind is not like sendmail. Comparing bind configuration file to sendmail is just wrong. Compare it to apache or exim, but it's even easier than both of those. It's just not that hard. Along that line, there is no way in HELL I would use a GUI to maintain more than a very simple zone file. When I want to make changes in bulk, there is no better way than scripts / vi / emacs / awk / whatever over a plain text file.

    34. Re:De Facto by Oopsz · · Score: 1

      Aw, he cares enough to write his own server, but not to implement the entire DNS spec. Maybe that's why no one uses it! Some of us need zone transfers! BIND9 was a complete rewrite of the server, which has proved stable and efficient. It's easy to use, has straightforward syntax (cf. sendmail, which is arcane and annoying), and is in such widespread use that bugs and holes are found quickly.

    35. Re:De Facto by Oopsz · · Score: 2

      Think about using Bind. Bind9 was a rewrite of the server from the ground up, and has proved secure. If you wanted to use sendmail, I'd tell you to go look up postfix or exim, but Bind isn't evil. It's remarkably straightforward to set up and admin, the configuration syntax is simple, and the server is stable as hell.

    36. Re:De Facto by megarich · · Score: 1

      I'm not to familiar with MTA programs so can anybody tell me which is the advantages/disadvantages of sendmail over postfix and vice versa? Here we use sendmail I guess because they guy who sets that part up is used to it and know that is proven to work. Like the old saying goes, if it ain't broke why fix it but I would like to know the differences between sendmail and postfix...

    37. Re:De Facto by Tet · · Score: 1
      MY experience is that people who use sendmail might as well just generate their configuration files using /dev/urandom. I guess MY real world experience proves YOU to be wrong, so now you're going to stop using sendmail, right?

      Not at all. You didn't read what I wrote. I even agreed that sendmail.cf leaves a lot to be desired. You said that the only way to get perl to look like line noise is to deliberately obfuscate it. My real world experience proves that to not be true, because I have seen line noise perl that was intended to be used rather than entered into an obfuscated coding contest. I didn't say all perl was like that, though, and I didn't say it was a reason for you to stop using perl, though, just as the cf syntax isn't going to stop me using sendmail.

      --
      "The invisible and the non-existent look very much alike." -- Delos B. McKown
    38. Re:De Facto by ahodgson · · Score: 1

      djbdns does support zone transfers. It's not the recommended way of running a secondary (rsync over ssh is), but you can do it if you really want to.

    39. Re:De Facto by ahodgson · · Score: 2

      djbdns supports zone transfers. The tcp server accepts AXFR commands, and axfr-get implements a client-side transfer into a djbdns-format zone file.

    40. Re:De Facto by daviddennis · · Score: 2, Insightful

      Well, I meant that was what a DNS server does. It gets a request, and looks it up in a lookup table. That's all most people running DNS servers really need.

      You're over-complicating things for simple applications if you use the software meant to distribute DNS over an entire network of servers for your single web site which just needs to receive a request for www.amazing.com and return an addresss.

      D

    41. Re:De Facto by the_mad_poster · · Score: 1

      I have to admit that I don't have much against BIND9, and I only have a vague preference for djbdns since I've never need ZTs. Plus, I don't use either in any particular capacity. The point about BIND still stands, however. It's not so much that it's chosen on merit (if that was the case it never would've made it to BIND9), just that it's chosen because it's the default.

      sendmail's the package I really hate...

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    42. Re:De Facto by the_mad_poster · · Score: 1

      I think you're confusing me with another poster. The most I ever said was, basically, that any syntax can be obfuscated by lazy or stupid people. However, that was said in response to your complaint that Perl lends itself to ugliness. Well, guess what? So does sendmail configuration. Now I'm calling bullshit on throwing Perl off the server becuase it's "too easy to write line noise" when you use a package that is notorious for having some of the most fucked up cf syntax in the history of SysV/BSD systems.

      Why do you think the prevailing wisdom is to treat the configuration like a delicate deck of cards that should only be touched if it means staving off the cataclysmic end of the world? Hmmm.... because it's shit poor line noise? Just like the security is shit poor lip service?

      Give it a rest. There's no "sendmail FUD". You should Fear sendmail and treat it with Uncertainty because there is no Doubt that it will totally screw you the second you turn your back.

      It's just a lousy package, plain and simple. If you're one of the very, very, very, very, very few people who need some arcane feature that only sendmail includes, congratulations on being unlucky. Otherwise, I'd say it's not too much of a guess to say the only reason you don't pick a better package is because you're too lazy to jump on that learning curve.

      --
      Alito: A vote for Alito is a punch in the eye to put that bitch back in her place!
    43. Re:De Facto by thomasa · · Score: 1

      Active Directory certainly CAN work with BIND.
      There are changes you have to make to your options
      section and zone files you have to manually add
      to BIND but it works fine.

    44. Re:De Facto by ChristTrekker · · Score: 1

      I'd be interested in hearing more about Bind9 then. Off to Google...

    45. Re:De Facto by pHDNgell · · Score: 1

      As someone who used to run sendmail (from the late 80's to 2002 before switching to exim) it gives you native support for UUCP

      I can't speak for EXIM, but I use postfix' native UUCP support out of the box. Works great and is very easy to set up.

      --
      -- The world is watching America, and America is watching TV.
    46. Re:De Facto by Anonymous Coward · · Score: 0

      You must be using an ancient version of exim.

      Recent 4.x versions allow an ACL to be applied at every stage of an SMTP transaction, including HELO/EHLO. You can check it for anything you want. regex, dns lookup, whatever. Of course the HELO string given in an SMTP transaction is of fairly little value, compared to, say, the remote IP address. There are more nonspammer mailservers out there with invalid/bogon HELO strings than there are spammer senders that arent smart enough to send a valid helo.

    47. Re:De Facto by mikemcc · · Score: 1

      I switched to postfix from sendmail for my company's MX servers, and have been extremely happy.

      A couple of severe Sendmail message-born vulnerabilities came out in rapid succession, around the time that I was trying to make sendmail more efficient at stopping spam.

      Postfix's UCE rules are straightforward, logical, and easy to configure. I don't see postfix vulnerability alerts with the same frequency that I do for sendmail. The first time one of my coworkers looked at my postfix main.cf file, he understood immediately what I was trying to do.

      I don't have any mail-related needs that sendmail does but postfix doesn't, and I find postfix to be MUCH more maintainable. For me, postfix does the same amount of work while demanding less of my time.

    48. Re:De Facto by CmdrTHAC0 · · Score: 1

      You might find dnsmasq useful, depending on the size of that network. Local DNS, recursive lookups, and DHCP rolled into one convenient package.

      --
      __CmdrTHAC0__
      In Soviet Russia, Spanish Inquisition doesn't expect YOU!!
    49. Re:De Facto by Jonathan+the+Nerd · · Score: 1
      That's a somewhat common thing with DJB's software. He generally doesn't support features that he thinks are inferior, broken, or useless. Zone transfers are supported, but their use is discouraged, for various reasons.

      If you go to the tinydns site, you can read quite a lot of ranting about the brokenness of BIND and how it doesn't conform to various RFC's. DJB hates BIND with a fiery passion, and his rants make for interesting reading if you have nothing better to do.

      --
      Disclaimer: The opinions expressed are not necessarily my own, as I've not yet had my medication today.
    50. Re:De Facto by Inuchance · · Score: 1

      Heh, real subtle. :P

    51. Re:De Facto by huskymo · · Score: 1

      Active Directory should work with any name server that supports SRV records and dynamic update (IXFR would be handy, too). I imagine there are name servers besides BIND that fall into that category.

    52. Re:De Facto by Jonathan+the+Nerd · · Score: 1
      Some of us need zone transfers!

      Why not use djbdns then?

      --
      Disclaimer: The opinions expressed are not necessarily my own, as I've not yet had my medication today.
    53. Re:De Facto by ChristTrekker · · Score: 1

      Great, thanks! (Nice nick, too, BTW.)

    54. Re:De Facto by Anonymous Coward · · Score: 0

      Sendmail is the MTA I use on most servers, but it's been about 10 years since I manually hacked sendmail rules. I know people who still hack sendmail.cf directly, but I thought most sendmail admins today use m4 to generate sendmail.cf from mc files. Adding a feature or modifying behavior is usually a one line change in the mc file. New hacks that have not yet been promoted to features can be downloaded from sendmail.org. Unless you are doing something unique to your site, there is no need to directly edit sendmail.cf.

  4. MyDNS by Havokmon · · Score: 5, Informative
    I've played with it.. it's defintely a nice DNS server.

    But what I really want is something like EasyDNS provides: Aliases. I want to be able to 'clone' whole domains, because they're all going to the same place anyways based on the hostname.

    Maybe EasyDNS just wipes out all the duplicate hostnames, and writes new records for them between the web interface and the backend when a host is changed or added..

    --
    "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    1. Re:MyDNS by boaworm · · Score: 4, Informative

      You should try PowerDNS. It's entire records are located in MySQL database tables, enables very easy update/modify/add/delete scripts. Performance is great :-)

      --
      Probable impossibilities are to be preferred to improbable possibilities.
      Aristotele
    2. Re:MyDNS by Anonymous Coward · · Score: 1, Informative

      Do you mean to automatically have a.domain2.com, b.domain2.com, ... once you have a.domain1.com, b.domain1.com?
      If yes, you can definitely do this with bind: simply use an abbreviation-only file (no reference to the domain) and use this file for both domains.

    3. Re:MyDNS by Havokmon · · Score: 1
      You should try PowerDNS. It's entire records are located in MySQL database tables, enables very easy update/modify/add/delete scripts. Performance is great :-)

      Yep played with that too.. but I'm kinda scripted out - I was hoping someone else already did all the work for once :P

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    4. Re:MyDNS by Anonymous Coward · · Score: 1, Informative

      try PowerAdmin, its a php frontend to pdns.

    5. Re:MyDNS by Havokmon · · Score: 1
      Do you mean to automatically have a.domain2.com, b.domain2.com, ... once you have a.domain1.com, b.domain1.com?

      Yes, exactly

      If yes, you can definitely do this with bind: simply use an abbreviation-only file (no reference to the domain) and use this file for both domains

      Hmm.. I kind of wanted to avoid BIND ;) In fact, I actually like the MySQL based DNS servers because they also provide easy replication of the data.

      Or can maybe BIND store it's data in MySQL now too? I didn't think so..

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    6. Re:MyDNS by Simon+Lyngshede · · Score: 1

      Bind provides easy data replication, that's how you make secondary dns servers :-)

      I can understand why some people would what to have dns information in a SQL database, but personally I feel that it's just adding a not piece of software that could potentially fail. Trust me, you don't what your dns to fail.

      I run tinydns, small, secure and easy to use. I not fan of the license and I really should switch to something with a clearly defined license, but I haven't found anything better.

    7. Re:MyDNS by Havokmon · · Score: 2, Interesting
      Bind provides easy data replication, that's how you make secondary dns servers :-)

      Yeah, but I'm already replicating MySQL - so what's another table? :P

      I can understand why some people would what to have dns information in a SQL database, but personally I feel that it's just adding a not piece of software that could potentially fail. Trust me, you don't what your dns to fail.

      Ahhh. Actually, I run an email service. So I already have MySQL servers that need to be up 100% of the time. In fact, I'd wager that most websites would also run some type of SQL, and need to be up 100% of the time. So it's a natual fit.

      Plus, DNS is cached. So depending on your traffic, odds are pretty good that you'll have your server up before your hostname's cache expires - and if necessary you can concentrate on what's probably a bigger problem than DNS ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    8. Re:MyDNS by muckdog · · Score: 1

      a front end to dns???? since when have text files sorted into neatly sorted columns become so difficult?

    9. Re:MyDNS by Electrum · · Score: 1

      But what I really want is something like EasyDNS provides: Aliases. I want to be able to 'clone' whole domains, because they're all going to the same place anyways based on the hostname.

      MyDNS supports server side aliases. The web interface lets you specify default records (such as NS and MX records) to add automatically whenever you add a domain. This makes it very easy to setup many domains with the same records. Of course, since the data is in MySQL, it's easy to write a script to do the same thing.

      As a side note, I've been using MyDNS for almost two years (when it was first released) on many servers and have been very happy with it. It is perfect for situations where MySQL is more convenient than a simple text file (tinydns).

    10. Re:MyDNS by Anonymous Coward · · Score: 0

      The records are stored in a database. You gonna fire up emacs and edit the hashed db tables into nice little columns? That should be verrrry interesting.

  5. bind difficult to use? by Anonymous Coward · · Score: 0

    Well, I don't find BIND difficult to use or set up. Sure, it's better to understand the DNS protocol, but I find the configuration files & syntax to be very clear (at least in my configs ;)

  6. That's like... by Simon+Carr · · Score: 3, Informative

    "air is most popular substance to breathe". :)

    That being said, PowerDNS is pretty awesome as a master, very nice for front end interface building.

    --
    -- The unsig...
    1. Re:That's like... by Ctrl-Z · · Score: 1

      "air is most popular substance to breathe".

      You think that's air you're breathing now?

      --
      www.timcoleman.com is a total waste of your time. Never go there.
    2. Re:That's like... by Anonymous Coward · · Score: 0

      I breath from an oxigen tank you INSENSITIVE CLOD!!!

  7. Not necessarily the best for all... by Piranhaa · · Score: 4, Informative

    Personally, I use one called djbdns. It's extremely small and basically bug free! The author actually will pay $50,000 to whoever finds the first exploit in it or something. If you don't need all the extra power that bind offers, this is a much better way to go. Less memory and space required, meaning cheaper systems may run it better. Even the config file can't be simpler!! cat /etc/tinydns/root/data .pnet:10.0.3.33:a:259200 .10.in-addr.arpa::ns.pnet: #Define hosts & aliases =pollux.pnet:10.0.3.1 =altair.pnet:10.0.3.2

    1. Re:Not necessarily the best for all... by Anonymous Coward · · Score: 1, Informative

      Yeah, that is Tinydns mentioned in the survey.

    2. Re:Not necessarily the best for all... by Anonymous Coward · · Score: 2, Informative

      You mean, $500.

    3. Re:Not necessarily the best for all... by Russ+Nelson · · Score: 2, Interesting

      Uhhhhhhh, sorry, Anonymous Coward, but you don't get away with that accusation without more details than that. There have been no security lapses in tinydns or dnscache. Weasles is actually spelled Weasels. Googling for djbdns fraud gets me nothing. Honest up, dude!
      -russ

      --
      Don't piss off The Angry Economist
    4. Re:Not necessarily the best for all... by Russ+Nelson · · Score: 2, Informative
      Actually, your zone file looks like this:
      .pnet:10.0.3.33:a:259200
      .10.in-addr.arpa::a.ns.p net:
      #Define hosts & aliases
      =pollux.pnet:10.0.3.1
      =altair.pnet:10.0. 3.2
      --
      Don't piss off The Angry Economist
    5. Re:Not necessarily the best for all... by Piranhaa · · Score: 1

      Thank you :) I don't remember what I was on when I pasted that hehe

    6. Re:Not necessarily the best for all... by Christianfreak · · Score: 2, Informative

      I use djbdns as well. Very simple, very easy to use. I actually run about 100 domains off of it.

      I can't say that I really like the separate cache/dns server but I've gotten used to it. I just wish my cache would immediatly pick up changes in my DNS. And I wish it was better documented.

    7. Re:Not necessarily the best for all... by Anonymous Coward · · Score: 0
      just add
      svc -t /service/dnscache
      to your make file for your tinydns data file, then it will restart dnscache whenever your change your data file.
    8. Re:Not necessarily the best for all... by diablobsb · · Score: 1

      man.... you couldn't be more wrong ..
      it's not $50,000
      it's $500
      as per :
      http://cr.yp.to/djbdns/guarantee.html

      --
      I for one, welcome our new hot grits... PROFIT!
    9. Re:Not necessarily the best for all... by geniusj · · Score: 4, Interesting

      As another testimonial, I use djbdns for over 900 domains and over 100,000 RRs. We receive about 300 queries/sec with tinydns using about 2% CPU and about 800K of memory. I love the rsync method of syncing dns data, it works especially well for Dynamic DNS (which is something I provide).

      As an aside, long ago, ODS (the service I run) ran BIND. At the time BIND used 90+% CPU consistently. Mainly because of the constant dynamic updates being sent to BIND via the update daemon. It also used about 50MB of memory or so (back in 1999 or therabouts). The switch to djbdns came shortly thereafter and I haven't looked back. Granted, djbdns cannot provide immediate dynamic updates because of its use of CDB. However, I find that every 30 seconds proves to be sufficient, especially when the 'secondaries' get updated immediately as well (thanks to rsync). Building the cdb is also remarkably fast, with it taking 0.55 seconds to hash the cdb with over 100k records.

      Overall, I'm quite happy.

    10. Re:Not necessarily the best for all... by Anonymous Coward · · Score: 0

      I run two domain registrars and we use tinydns. We have exactly 29226 domains currently hosted which all use tinydns. The tinydns data file lends itself well to programs that need to create the data file out of a DB or some other source. The syntax is clean and easy.

      Our current data file is 5.9MB in size. We have 4 DNS servers which average ~50 queries / second each. Load average is usually at 0.00 on single proc 1.4Ghz, 2GB/mem boxes.

      There are also bigger registrars than the ones I run that use tinydns that host many more domain names and they would use nothing other than tinydns. Tinydns is one of those things that once you start using, you probably will never go back to Bind.

    11. Re:Not necessarily the best for all... by TheMysteriousFuture · · Score: 1
      --
      .sig
  8. For the same reason most people use windows by kickus_assus · · Score: 1

    They don't know any better and are afraid to change!

  9. It is the default, and not hard to understand by hattig · · Score: 2, Informative

    Unlike sendmail which can scare people away just with the configuration file, the BIND zone file layout and other stuff isn't hard to learn.

    So people use what came with the box, what their book on "DNS & BIND" uses, and so on.

    Also, everybody else uses it!

    1. Re:It is the default, and not hard to understand by Russ+Nelson · · Score: 1, Insightful

      Actually, the BIND zone file layout is error prone. How many times have you forgotten to update a serial number? How many times have you forgotten to put a dot at the end of a name?

      Also, BIND allows you to mix caching and authoritative services. Not only is this insecure in nature, it's insecure in BIND's implementation. Much safer to have them on different IP addresses.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:It is the default, and not hard to understand by Nohea · · Score: 3, Interesting

      I really like BIND 9 - easy to use, the most features, plus a full rewrite since BIND 8.

      DNS servers are low on resource usage anyway, so switching to a leaner daemon would always be a niche product (like Apache alternatives).

      The only motivation for switching is the exploit issue. With the rewrite, its less of a case, and everyone should be keeping up to date w/security patches anyway.

    3. Re:It is the default, and not hard to understand by Grayputer · · Score: 1

      I've never forgotten to update serials or had a dot problem. There is a tool called h2n that takes a standard host file and generates all zones needed for bind. I think the discussion misses the point, BIND is the standard, tools exist to generate the zones, it works, it is reasonably bug free given today's definition (low to moderate instances, quick fixes), it is the default install on most *nix, and help/doco is everywhere. Why would the AVERAGE guy change? (Yes, security geeks might, windows guys hate unix tools, newer toys to play with exist, and some people just have to be different, but why would Joe Average?).

  10. crypto ... by straybullets · · Score: 1

    http://cr.yp.to/djbdns/run-server-bind.html i dont know ...
    maybe i'm just too old for this now ...
    :)

    --
    With that aggravating beauty, Lulu Walls.
  11. Dynamic DNS by ldspartan · · Score: 1

    Let's not forget Dynamic DNS, i.e., DNS updates from DHCP. I 3 DJB's software, tinydns included, but you can't (readily) attach it to ISC DHCPD and have your DNS records change with your DHCP leases. This isn't a limitation of Dan's software, but rather vendor lock-in on the part of the ISC (and MS, who provides the other major DDNS implementation).

    For some people, in some situations, this is a necessity. I just can't wait for someone to write a DJB-inspired DHCP server.

    1. Re:Dynamic DNS by Russ+Nelson · · Score: 2, Informative

      Why not?? He's replaced the other major ISC-associated software. Plus you know there must be security holes in dhcpd.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:Dynamic DNS by s3ti · · Score: 0

      You should take a look at this.

    3. Re:Dynamic DNS by ldspartan · · Score: 1

      Heh, _my_ C skills certainly aren't up to DJB quality codig, but I bet yours are. You should go for it once that domainkeys implementation is done. :)

      --
      Phil

    4. Re:Dynamic DNS by ldspartan · · Score: 0

      'codig' ... nor are my typing skills, apparently.

    5. Re:Dynamic DNS by BK425 · · Score: 2, Interesting

      You've got to be talking about some other ISC. The ISC I know is a non profit, they make the open source BIND product by paying some of the guys who wote (pretty much with volunteered time to) the open standard for DNS. It needs help IMHO but vendor lock in it isn't.
      It's really cool to see someone remaking it with a real database behind it, anyone who's made/makes major system changes has had LDAP problems and at the very best it is a marvle of 1960 db design. But... the "can even do AXFR to other servers" thing in the frill portion of his web site description is worrisome. AXFR is part of the DNS game, if you'r not going to play with other servers... well the whole point of the way DNS works is a -distributed- name system. How would you distribute load without standard zone transfer protocol? Far from a frill IMHO.

    6. Re:Dynamic DNS by Anonymous Coward · · Score: 0

      Actually, it is indeed a limitation of Dan's software. ISC DHCPD supports DDNS through a mechanism very close to the yet-unfinalized IETF spec for it; djbdns doesn't. Once the spec is finalized, ISC will support it; djbdns still won't. It's no secret that DJB doesn't give two shits about specs.

    7. Re:Dynamic DNS by ldspartan · · Score: 1

      Vendor lockin is probably too strong a phrase. What I mean is that, without writing your own solution, ISC DHCP only plays nicely with ISC BIND, and MS AD only plays nicely with MS DNS server and ISC BIND. Personally, I don't really care about ISC's motivation or employees or whatever else, just that their software is easy to use and secure. DJBDNS fits the bill for me better than BIND does.

      As for AXFR and so forth... I don't know where you're getting all this, but one of the selling points of DJB's design philosophy is modularity. tinydns does exactly one thing: serves authoratative DNS over UDP. It doesn't do TCP (and therefore AXFR), nor is it a caching resolver. Both of those functions are done by other parts of the DJBDNS package (axfrdns for TCP queries and AXFR, dnscache for a caching resolver). If you want to do incoming AXFR, its easily implemented with a short perl script that generates a tinydns data file (autoaxfr) - this is from a third party, and is widely used.

      Heck, say you want to (for some ungodly reason) create DNS entries based on incoming email statistics. Its easy, hack up some perl and you're all set, no need to restart tinydns (it reloads its data file automatically) or even touch anything DJB-related.

    8. Re:Dynamic DNS by Simon+Lyngshede · · Score: 1

      I once used dhcp_dns http://www.thismetalsky.org/magic/projects/dhcp_dn s.html

      Im not quite sure if this was what you where looking for. If you just need to update tinydns with information from dhcp it works okay.

    9. Re:Dynamic DNS by Anonymous Coward · · Score: 0
      The ISC I know is a non profit

      That is because either you are astroturfing or you have bought into Paul Vixie's marketing myth that ISC is a poor non-profit.
      He is shinning you on, the guy is making money by the truckload:
      • ISC has rich corporate sponsors
      • Expensive support contracts http://www.isc.org/index.pl?/sw/bind/
      • a private bind "club" with expensive dues
        http://www.isc.org/index.pl?/sw/guild/membership.p hp
        the cost is apparently a secret
      • he controls the f root server and the RFCs say that access by ISPs to the root servers can be charged for.
        Do they charge?
      • he controls the volunteer-built RBL lists that he closed, took private and now charges big $$ for access
        http://www.mail-abuse.com/services/purchase.php the prices are now secret because I think he realizes that it is bad PR to show the phenomenal gouging that is going on from a community built resource.
      • he has a private "club" for root/tld domain operators that charges $1500 - $50,000 to join (why is this _under_ ISC, why not a separate true peer stand alone entity? why because he wants to control it, that is the only reason why)
      • he got huge government and corporate grants to upgrade bind, turned around and had Nominum, his for-profit company do the programming and then after they wrote bind 9 they took what they learned and they did a better job programming the commercial, closed source DNS server software.
      • The biggest joke is that to sell their commercial software they level the same criticisms at bind that djb has been for year. To add insult to injury, they also use the architecture that djb has used (that they publicly lambasted in the past) - separate auth (ANS) and caching (CNS) servers.
      • Does he own part of MFNX/AboveNet?
      • This is a guy who has/controls alot of privately held businesses and associations

      This is a person who has avoided scrutiny and he, his business practices, his cronies and business relationships need to be much more closely examined before people go off cheering for "ISC".

      Then there is all the just weird, creepy stuff:
      The Hitler reference Vixie uses third person reference to Hitler and himself
      The collateral damage is really necessary quote: http://www.cctec.com/maillists/nanog/historical/97 09/msg00108.html :
      The spammers are going to make it as hard as possible to block them. For a while they used to abuse "popular" relays and shell machines and so on, in the mistaken belief that nobody would block a popular and necessary host resource just to get stop spam. I think I've told the story of the firebombing of Dresden to at least a half dozen popular host resource owners in the last two years.

      And all the rest of the stuff that would never fly around here...

      The fiasco when bind security patches were not available to those who hadn't paid to join the club:
      http://news.com.com/2100-1001_3-966666.html :
      "They basically responded that they wouldn't make it available until the weekend, and then they said they had an early warning service and you have to pay money for that," Maiffret said.

      http://www.centr.org/meetings/ga-9/tech-report.htm l :
      The development of BIND 9 was largely funded by donations procured in 1998 from US government agencies, IT vendors and ISPs. However, it became clear this method of funding was unreliable and did not provide sufficient revenue to develop BIND on an ongoing basis. In addition, it was unclear whether ISC would be accepted as a non-profit organization by the US Internal Revenue Service (IRS), which potentially meant corporate tax would have to be paid on the donations.

      http://lists.freebsd.org/pipermail/freebsd-current /2003-June/004481.html :
      Indeed, even

    10. Re:Dynamic DNS by Anonymous Coward · · Score: 0

      How would you distribute load without standard zone transfer protocol?

      How would you distribute http server load without a standard webpage transfer protocol?
      Since the idea of a single zone file format is outdated, presumably we can use waste (which would be much more secure than any existing crap), bittorrent, rsync, scp, etc, etc. No need for vendor lock-in on the damn file format, esp. since it doesn't translate well into various database format.

    11. Re:Dynamic DNS by Anonymous Coward · · Score: 0

      Dan? Is that you?

    12. Re:Dynamic DNS by Anonymous Coward · · Score: 0

      Actually, no Dan has trouble mostly with their DNS shell game. I in some feel that there are shifty things going on with all his businesses - like what happened with the RBL stuff and OARC - it's all about being in control.

  12. Far from accurate by FistFuck · · Score: 0, Troll

    Please explain how you managed to fingerprint DNS servers. I don't think many DNS servers have version identification fetures. BIND does but it's not exactly a standard. ...or maybe even a good idea.

    This surey ranks up there with "Most dentists recommend brand X" marketing for me. The accuracy of the sample set is extremely questionable.

    1. Re:Far from accurate by crimoid · · Score: 2, Informative

      He used fpdns which is a well-known and accurate tool. http://www.rfc.se/fpdns/

    2. Re:Far from accurate by FistFuck · · Score: 1

      No. fpdns is guessing.

      Determining what product is used when the product does not identify iteslf does not lead to accuracy.

      "That pile of rocks must be coal because they look black."

      Far from definitive.

    3. Re:Far from accurate by Iamnoone · · Score: 3, Informative

      Please explain how you managed to fingerprint DNS servers.
      The same way you fingerprint OS's via there ip stack. Unusual queries and how the server reacts to them.
      http://cr.yp.to/surveys/dns1.html is one among several fingerprinting methodologies.

      The accuracy of the sample set is extremely questionable.
      If you RTFS, he didn't take a sample, he used all the name servers. There aren't that many (which in itself is a interesting commentary on the true size of the internet) - for the .com, .net, .org, .info, and .biz TLDs 37 million domains -> 1 million name server names -> 646,524 unique name server IPs.

      The interesting part is is the 27 percent that can't be fingerprinted. My guess is that they would follow a similar pattern to the fingerprintable ones but their firewalls block some of the unusual queries.

    4. Re:Far from accurate by Sique · · Score: 2, Informative

      Yes and now. Every chemical analysis is basicly guessing, because no substance presents itself: Hey, I am Carbonbihydroxide! There are several tests which can give you a quite conclusive set of clues, what substance you are looking at. "Quite conclusive" in this case means: Better than 0.999999... probability.

      That's the same way server fingerprinting works. Run several tests, and each of them increases the probability for one and lowers the probability for others. It gets quite hard to modify a server in a way that it responds exactly like another one (error messages, timing, matchting between OS type and DNS server: You won't find WINS running on OpenVMS that easily.)

      Of course it's not definitive. But it gets very close to several nines in probability.

      --
      .sig: Sique *sigh*
    5. Re:Far from accurate by Anonymous Coward · · Score: 0

      via there ip stack.

      Oh god, a there/their/they're error, time to flog myself...

  13. You really see which DNS does heavy lifting. by Inoshiro · · Score: 5, Interesting

    Ratio of BIND domains serviced to installs: 24,335,752 / 340,345 = 71.5 domains/server.

    Ration of MS DNS domains to installs: 2,165,143 / 101,781 = 21.27 domains/server.

    Ratio of TinyDNS domains to installs: 5,405,266 / 12,130 = 445.6 domains/server!

    Despite only having 2% of the installs, TinyDNS serves 15% of all domains on the internet. Obviousy it is very capable, and has few to no exploits available for it. Why don't more people use TinyDNS if it's so capable?

    Because they haven't read how easy it is to setup!

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:You really see which DNS does heavy lifting. by James+Youngman · · Score: 4, Insightful
      Despite only having 2% of the installs, TinyDNS serves 15% of all domains on the internet.
      Maybe that just means that TinyDNS is popular with domain squatters.

      I think that the best definition of "heavy lifting" is not the size of the installed base or the average number of domains per server, but instead the total number of queries served. Those numbers of course are hard to estimate.

    2. Re:You really see which DNS does heavy lifting. by Florian+Weimer · · Score: 5, Informative

      Despite only having 2% of the installs, TinyDNS serves 15% of all domains on the internet. Obviousy it is very capable, and has few to no exploits available for it. Why don't more people use TinyDNS if it's so capable?

      tinydns is unmaintained software. It does not compile out of the boxon modern systems. You don't have a license, so you can only do with it what your local copyright law permits (which may or may not be enough). The zone file format of tinydns is non-standard. The answers it generates are often excessively verbose (e.g. redundant NS records). Third-party documentation suggests a configuration that violates recommendations of TLD operators and most ISPs, which means that you have to redo parts of it once you receive your first delegation.

      And so on. Go ahead and use BIND alternatives for authoritative name servers, but try to avoid tinydns.

    3. Re:You really see which DNS does heavy lifting. by AKnightCowboy · · Score: 1
      Despite only having 2% of the installs, TinyDNS serves 15% of all domains on the internet. Obviousy it is very capable, and has few to no exploits available for it. Why don't more people use TinyDNS if it's so capable?

      Because it sucks. I tried to get it working a Linux box, followed the directions exactly step by step and all I ended up with was a DNS server that worked for about 2 minutes then stopped accepting queries and hung. Whether that's the crappy inetd replacement DJB wrote or the DNS server itself I have no idea. I happily went back to BIND and have NO problems. Not to mention DJB's whole arrogant attitude about zone transfers and using scp to copy zones around. WTF?

    4. Re:You really see which DNS does heavy lifting. by Tmack · · Score: 1
      If you are talking about the local check that the docs tell you to use (tinydns-get or something like that), yes, it stops working after the server has been running for a few mins. However, remote queries should still be working. I experienced the same problem setting it up, but noticed that even though that local app could no longer get a response from tinydns, my windoze machine could.

      tm

      --
      Support TBI Research: http://www.raisinhope.org
    5. Re:You really see which DNS does heavy lifting. by photon317 · · Score: 1


      It does compile out of the box on modern systems. I use it for 5 different domains that I administer. The latest time I set it up, it was on a Gentoo Linux box, I just had to emerge the package and was good to go. It is maintained, but the author doesn't see a pressing need for any changes to its functionality. It's simple, secure, and does everything an authoritative dns server should do correctly.

      I don't know what third-party documentation you're referring to, but most people just read how to configure it from the djbdns official site at http://cr.yp.to, which suggests no bad configurations. If you'd like I could write a third party document for how to fuck up BINDs configuration too :)

      Perhaps one of the most important aspects of djbdns is that it avoids lots of complexity and security problems by fulling seperate authoritative nameserving of data from caching resolver servers for clients - they're actually two seperate unrelated programs.

      --
      11*43+456^2
    6. Re:You really see which DNS does heavy lifting. by PlusFiveTroll · · Score: 2

      TinyDNS is popular with admins that have lots of domains because there is one configuration file for the domains, the default bind way sucks if you have any number of them, and I have domain entry scripted so it takes seconds to add a new domain. Not having to restart TinyDNS when your domain file is changes is a big plus too. I manage around 150 domains with the average of 3 per customer, hardly squatting.

    7. Re:You really see which DNS does heavy lifting. by PlusFiveTroll · · Score: 1

      The zone file format of tinydns is non-standard.

      Which standard would that be?

      Damn Trolls... :)

    8. Re:You really see which DNS does heavy lifting. by Florian+Weimer · · Score: 4, Informative

      RFC 1035 (STD 13) describes the format of zone files (which are called "master files" in this document).

    9. Re:You really see which DNS does heavy lifting. by drew · · Score: 1

      actually the one that surprised me was Net::DNS::Nameserver.

      36,195 domains on 6 installations: 36,195 / 6 = 6032 domains/server!!!

      Also amusing was Nominum ANS/CNS:

      12 domains on 14 installations: 12 / 14 = 0.86 domains/server

      --
      If I don't put anything here, will anyone recognize me anymore?
    10. Re:You really see which DNS does heavy lifting. by Just+Some+Guy · · Score: 1
      Ratio of BIND domains serviced to installs: 24,335,752 / 340,345 = 71.5 domains/server.

      I serve DNS for about 65 domains on my BIND server. Even though it's also a fairly busy webserver and a mailserver with lots of spam filtering, my long-term load average is currently sitting at 0.02.

      I am not limited to the number of served domains because BIND isn't capable of any "heavy lifting" - I just don't have any more that I need to serve. TinyDNS may or may not be more capable of serving thousands of domains on the same machine, but the tiny numbers you're trying to draw conclusions from wouldn't put a dent in any sane server.

      --
      Dewey, what part of this looks like authorities should be involved?
    11. Re:You really see which DNS does heavy lifting. by Florian+Weimer · · Score: 2, Informative

      It does compile out of the box on modern systems. I use it for 5 different domains that I administer. The latest time I set it up, it was on a Gentoo Linux box, I just had to emerge the package and was good to go.

      In this case, you don't use the official version of tinydns, but a modified one which contains random patches. Others have patched GNU libc to increase interoperability with broken applications such as tinydns, too.

      It is maintained, but the author doesn't see a pressing need for any changes to its functionality. It's simple, secure, and does everything an authoritative dns server should do correctly.

      The official version does not support IPv6, for example.

      I don't know what third-party documentation you're referring to, but most people just read how to configure it from the djbdns official site at http://cr.yp.to, which suggests no bad configurations.

      The way serial numbers for zones are automatically generated by tinydns is not universially accepted.

    12. Re:You really see which DNS does heavy lifting. by JianTian13 · · Score: 2, Informative

      Umm, Florian, couple of questions here:

      1) Unmaintained? Well, if it's feature complete (does what the author and its users need), and hasn't been shown to have any serious bugs or exploits, what's to maintain?

      2) Doesn't compile out of the box on "modern" systems? Excuse me, but doesn't OpenBSD 3.4 count as modern? I sure didn't have to do anything special to get it working there. Got an example?

      3) Non standard zone file format? Well, for me the tinydns format is a helluva lot more readable, and less error prone. No serial number incremeting, no missing closing braces, etc.

      4) Can't really say anything about the length of the answers returned, so I have to defer to you on that. But can you show me which 3rd-party docs tell you to do something "that violates recommendations of TLD operators and most ISPs"? Are we talking about this site? Or someone else?

      I'm not one of DJB acolytes here; I just was able to understand DJB's docs and examples a lot faster than any of the BIND howtos I saw, and it looked like there would be fewer pitfalls. And yes, on the license thing, I'd like to see him release it under something more permissive, but for now:

      A) It does what I want, and
      B) I can satisfy myself that the software's reasonably secure.

      That's enough for me. I was just hoping you could clarify some of what you'd said... Thanks!

    13. Re:You really see which DNS does heavy lifting. by Just+Some+Guy · · Score: 1

      TinyDNS is popular with admins that have lots of domains because there is one configuration file for the domains, the default bind way sucks if you have any number of them

      In BIND, you add a record with the domain name and the file storing its contents to named.conf. I have a hard time imagining a much simpler way to configure that information. You can also point multiple domains to the same zone file if you have a default you'd like to use.

      I have domain entry scripted so it takes seconds to add a new domain.

      This is also trivially possible with BIND.

      Not having to restart TinyDNS when your domain file is changes is a big plus too.

      rndc reload not good enough for you?

      Use whatever you want - it makes no difference to me. But every reason you gave for using DJB's tools apply equally to BIND, so I'm not sure what point you're trying to make.

      --
      Dewey, what part of this looks like authorities should be involved?
    14. Re:You really see which DNS does heavy lifting. by geniusj · · Score: 1

      This is pet peeve of mine.. Who gives a shit what your serial number is as long as it incrememts. tinydns's method is perfectly fine as far as I'm concerned. Saves me a lot of time. In case you haven't read my post above, I currently run tinydns with over 100,000 RRs and 1000 domains. I have had no problems except for with one registrar who complained that our serial numbers weren't in the 'yearmonthdatenum' format. They got over it though and just delegated the domain. Why people care about such trivial crap is beyond me..

    15. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0

      [quote]3) Non standard zone file format? Well, for me the tinydns format is a helluva lot more readable, and less error prone. No serial number incremeting, no missing closing braces, etc[/quote]

      Funny thing is, that it can be easily read and used by programs, making it extremely easy to use.

    16. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0

      tinydns is unmaintained software.

      I suppose if your idea is "unmaintained" is "there aren't security patches coming out every other month that swear its the last one" then yes, tinydns is unmaintained.

    17. Re:You really see which DNS does heavy lifting. by Electrum · · Score: 1

      The answers it generates are often excessively verbose (e.g. redundant NS records).

      This only occurs if you specify redundant name servers in the database. tinydns serves exactly what you tell it to serve.

      Third-party documentation suggests a configuration that violates recommendations of TLD operators and most ISPs, which means that you have to redo parts of it once you receive your first delegation.

      That is because you should avoid RFC 2317 style delegation. RFC 2317 was written by the authors of BIND:

      "If you were running BIND, you'd find it only a little bit painful to receive a classless reverse delegation (setting up one zone file), while you'd find it much more painful to receive separate reverse delegations (setting up many zone files)." (source)

    18. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0

      And so on. Go ahead and use BIND alternatives for authoritative name servers, but try to avoid tinydns.

      But what are those alternatives besides bind and djbdns? Are there any other good ones? Do you have any experience? Because speaking from my experience there's either bind or djbdns. Thanks.

    19. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0

      Pretty much all djb software is abandonware. He doesn't maintain it. There are security exploits, major design flaws, etc in software like qmail, but he never releases updated versions. Don't mistake it as simply "the software is done, there's no need to update it." There are definitely needs, he just doesn't update it. Even simple updates.

      In fact, pretty much no djb software will compile on modern system without patches. You say it compiles on OpenBSD -- did you use a port? If so, I bet you it patched it.

      Try downloading the source by hand and building it. It won't build.

      Using abandonware with a license that redistributing modified versions illegal isn't a good foundation for my own purposes. For some it's acceptable.

      As for the zone file.. I think it's very hard to read for humans. For machine parsing, it's excellent, but I'm not a machine, and I personally don't want to have to find/use/write frontends to make it usable when there are human readable formats available.

      I use both tinydns and BIND.. I use tinydns because that's what was in use at a place I came to, it does the job, and I'm not the kind of guy who comes in and remakes everything in his image just because he can. Some day if our DNS structure/system needs redesigning, I may switch to something else. But in the meantime I'm very aware of the downfalls of djb software.

      If you want a good taste of djb software, I strongly suggest an exercise. Try making binary packages of daemontools, uspci-tcp server, qmail, and tinydns. You may not use binary packages normally, but this is just an exercise to get more familiar with his software.

      Examine the install instructions, the build structure, the build scripts. You may be astounded at how assasinine it is. Don't forget to include all the patches need to 1) make it compile 2) make it secure 3) make it perform well (see qmail silly queue thread..). It's a nightmare.

      FWIW, OpenBSD has dropped the qmail port. It's just ridiculous.

    20. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0
      [ http://cr.yp.to/djbdns/other.html ]

      Other DNS software

      Management tools

      twa lets authorized browsers edit the tinydns data file.

      ldap2dns converts an LDAP DNS database to a tinydns data file. tinyadmin is a graphical interface to the LDAP DNS database used by ldap2dns.

      mkdns converts a MySQL DNS database to a tinydns data file. It lets authorized browsers edit the MySQL DNS database.

      sql2tinydns is similar to mkdns.

      dhcp_dns watches dhcpd for new DHCP address assignments, and publishes those addresses through tinydns.

      tinydyndns publishes dynamic IP addresses authenticated through POP connections.

      Servers

      ldapdns publishes DNS information from an LDAP database.

      MyDNS publishes DNS information from a MySQL database.

      Posadis publishes DNS information from BIND-style zone files. Security history: Buffer overflow, allowing attackers around the Internet to take control of the server; fixed in m5pre2 (2002.03.30). Someone announced an exploitable buffer overflow in m5pre2 a few weeks later; the history here isn't clear from the Posadis web pages.

      NSD publishes DNS information from BIND-style zone files. Security history: Unclear. The NSD documentation includes bugs like ``Very strange coredump in hash_destroy() that happens sometimes'' without any analysis of their security impact. Is that an exploitable buffer overflow?

      PowerDNS publishes DNS information from MySQL databases, PostgreSQL databases, Oracle databases, IBM databases, LDAP databases, or BIND-style zone files. Security history: Unclear, like the NSD security history.

      MaraDNS is a general-purpose DNS server.

      lbnamed is a load-balancing DNS server.

      lbdns is another load-balancing DNS server.

      Oak DNS Server is a good example of why novices shouldn't try to write DNS software. The digitallumber.net domain, served by Oak DNS Server 1.0, is inaccessible to a huge number of clients that try AAAA lookups before A lookups: the server incorrectly returns NXDOMAIN for AAAA, effectively wiping out its own A record.

      Caches

      pdnsd is a DNS cache. Security history: Remotely exploitable buffer overflow; fixed in 1.1.7a (2002.01.18).

      MaraDNS can act as a cache.

      I don't know why anyone would want to use these caches in place of dnscache .

      DNS clients

      adns is a DNS client library.

      ares is a DNS client library.

      perldns is a DNS client library for Perl.

      The Buggy Internet Name Daemon [how very professional... *sigh*]

      BIND is a monolithic server/cache; it also includes a client library, libresolv. Security history: IQUERY buffer overflow in BIND before 8.1.2-T3B (1998); NXT buffer overflow in BIND before 8.2.2-P4 (1999); nslookupcompla

    21. Re:You really see which DNS does heavy lifting. by Anonymous Coward · · Score: 0
      [ http://www.maradns.org/dns_software.html ]

      Other DNS software

      This is a list of some other DNS software out there:

      Freely downloadable DNS servers

      Caching DNS servers

      • BIND 9 is a complete rewrite of BIND, and, as such, probably does not have the security issues that previous versions of BIND has. In fact, one of the BIND developers found a security problem in earlier versions of MaraDNS. Very full-featured, and is the reference standard for the newer DNS RFCs.
      • Oak DNS is a DNS server written completely in python. It is compatible (I think) with both BIND zone files and cache files.
      • pdnsd is a recursive caching DNS server. Paul Rombouts is the current maintainer of this program.
      • Posadis is another DNS server project, similiar to MaraDNS. This server is now both a resolving and an suthoritative DNS server.

      Non-recursive DNS servers

      • PowerDNS is an authoritative-only DNS server with support for, among other things, SQL. I would like to applaud the PowerDNS developers for making a libre release of this software. Note: Recursive code is in the works; PowerDNS will soon enough be a fully functioning recursive DNS server.
      • DnsJAVA is an authoritative-only DNS server written in Java.
      • NSD is an authoritative-only DNS server which is compatible with BIND zone files.
      • MyDNS is an authoritative-only DNS server which uses MySQL as a database back end.
      • The Pliant language/package comes with a DNS server. This DNS server can not recursively process DNS queries given a list of root servers.
      • Twisted includes a non-recursive DNS server.
      • The Eddit project includes a DNS server
      • SheerDNS is a simple non-caching DNS server that stores all records as their own files.

      Abandoned DNS server projects

      These are DNS server projects which have not released any files for six months or longer, and which never became functioning recursive (caching) DNS servers.

      • MooDNS is another DNS server project. A CVS checkout on January 21, 2003 shows that no files have been updated since July 20, 2002, except for a single readme file updated on August 1, 2002. This project is abadoned.

        I have made a tarball available for people who do not want to bother with a CVS checkout.

      • Dents is a DNS server that showed a lot of promise. Unfortunatly, no files have been released since 1999.
      • Yaku-NS is a DNS server geared towards embedded systems. According to the changelog, no one has made any changes to this software since Feburary, 2001.
      • CustomDNS has not released any files since the summer of 2000.

      Other

      • LdapDNS is a small DNS server which converts DNS requests in to LDAP requests, without caching.
      • DnsPython is a DNS toolkit for Python.
  14. thanks! by SQLz · · Score: 0

    Thank you captain obvious.

  15. Reasons why DJBDNS is not more common by James+Youngman · · Score: 5, Informative
    1. Its config file syntax is even more human-unfriendly than BIND's
    2. It doesn't allow free reign to set the records up exactly how you want (trivially for example, it forces you to adopt a mandatory naming convention for MX records - though the convention is pretty sensible)
    3. It doesn't support caching, so you need a separate server for that (this is actually good, but it does add to the overall amount of work required to set up a set of DNS servers)
    4. Some people find DJB difficult to get on with and/or were turned off by the whole problem around (non) distribution of modified versions of qmail, and so avoid DJB's other offerings
    1. Re:Reasons why DJBDNS is not more common by embo · · Score: 4, Funny
      Its config file syntax is even more human-unfriendly than BIND's

      I've got to disagree with you when I can parse a zone file like this:

      while (<STDIN>) {
      $line = split(':', $_);
      for $line[0] {
      if (/Z/) { # Zone file }
      elsif (/+/) { # A Record }
      elsif (/\@/) { # MX Record }
      etc. etc. etc.
      }
      }
      All you need is this page to understand the entire format of any zone file: http://cr.yp.to/djbdns/tinydns-data.html For BIND, I need the entire manual. Maybe it's just me.
    2. Re:Reasons why DJBDNS is not more common by Sevn · · Score: 1

      it forces you to adopt a mandatory naming convention for MX records

      I call shenanigans.

      It doesn't *force* you do use anything specific for MX records. I think you are confusing MX with NS. And even there, it doesn't *force* you to use a certain naming convention there either. You can choose what you like if you pop the entire FQDN in the record and throw a dot on the end.

      --
      For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
    3. Re:Reasons why DJBDNS is not more common by Sevn · · Score: 1

      Its config file syntax is even more human-unfriendly than BIND's

      I'd say this is a matter of opinion. The important thing is that the config file system is more script friendly, smaller, easier to distribute, etc. One record per line.

      It doesn't allow free reign to set the records up exactly how you want

      I set my records up exactly how I want. You'd have to explain that one. There isn't anything I haven't been able to do.

      It doesn't support caching

      DnsCache is for caching.
      TinyDNS is for authoritative DNS.
      They are both part of DjbDNS.

      Some people find DJB difficult to get on with and/or were turned off by the whole problem around (non) distribution of modified versions of qmail, and so avoid DJB's other offerings

      Some people find cutting and pasting quotes from web pages difficult in the absense of hands on experience with something. On the other hand, some people have no problems at all. A whole lot of people make a lot of decisions with minimal research effort.

      --
      For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
    4. Re:Reasons why DJBDNS is not more common by Christianfreak · · Score: 1

      It doesn't allow free reign to set the records up exactly how you want (trivially for example, it forces you to adopt a mandatory naming convention for MX records - though the convention is pretty sensible)

      No it doesn't. On the mx line where it says 'a' or 'b' on your mx record you can put anything you want. Instead of getting a.mx.domain.com you'll get mail.domain.com or whatever else you put there. Not hard at all.

      As for the syntax I think its just a matter of getting used to it. BIND has a lot of other config lines and things that I think for the most part are unnessicary and confusing.

      I agree on your other two points.

    5. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0

      > > Its config file syntax is even more human-unfriendly than BIND's

      > I've got to disagree with you when I can parse a zone file like this:

      He said "human-unfriendly", not "Perl-unfriendly". Your piece of code just reinforces the argument.

    6. Re:Reasons why DJBDNS is not more common by Russ+Nelson · · Score: 1

      Its config file syntax is even more human-unfriendly than BIND's

      So create a front-end for it, if you think it needs to be prettier. The semantics are much more human-friendly. You get in-zone names for MX and NS records by default. You get serial numbers updated by default. You never have a "do I need a dot at the end of this name or not" problem.

      It doesn't support caching

      djbdns does support caching. Anyway, you should be using different programs to cache and serve up authoritative data. Some of BIND's security problems were caused by its combination of cachine and authoritative data, so that is no longer a recommended configuration.

      Yes, you can't distribute modified version of djb's software. On the one hand, that's a pain in the ass. On the other hand, djb has a very good track record for security, so do you really WANT to distribute modified versions?
      -russ

      --
      Don't piss off The Angry Economist
    7. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 1, Insightful

      He said "human-friendly". That's a computer program.

      That's a hallmark of djb programs. File formats are very easy for machines to parse. Easy to parse tends to equate with being less human friendly.

    8. Re:Reasons why DJBDNS is not more common by Havokmon · · Score: 1
      All you need is this page to understand the entire format of any zone file

      ROFL, I like Dan's offerings, but I think you just quoted his axim on documentation as well ;)

      --
      "I can't give you a brain, so I'll give you a diploma" - The Great Oz (blatently stolen sig)
    9. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0

      <sarcasm>You know, a binary format would be even easier to parse!</sarcasm>

      Some of us value human readability over how many lines of code it takes to parse a format.

    10. Re:Reasons why DJBDNS is not more common by ajs · · Score: 4, Insightful

      Some people find DJB difficult to get on with and/or were turned off by the whole problem around (non) distribution of modified versions of qmail, and so avoid DJB's other offerings

      I have to say that this is the largest and most insurmountable reason for me against using either his DNS server or his mail server.

      I was a big fan of his back in the days of UUCP, but his unwillingness to let distributions of BSD, Linux, etc. modify and distribute his software (without some kind of source-based patching hack sans binaries) was a snub to all of us who have contributed to open source software over the years, and a clear indication of a lack of concern over the larger needs of his audience.

      Let me be clear: he's WELL WITHIN HIS RIGHTS, and he's even going out of his way to distribute his stuff, which is great. But to say "I'm going to play ball with you, but only if you use my ball, and in the following ways" doesn't fly for me. There are many good alternatives to his code, and they all have their own advantages and disadvantages. Thanks for playing, though.

    11. Re:Reasons why DJBDNS is not more common by jhoffoss · · Score: 1
      5. Most people find DJB nazi's difficult to get on with.

      There are a few on my local LUG list that, when possible, respond to questions with things like "rm bind; install djbdns" or "rm sendmail; install qmail". What's even more nauseating are the responses to other questions that are sourced eighteen different ways to cr.yp.to/djb-is-god/blah/blah.

      I'm sorry, but these people seem like they're members/leaders of djb's cult spouting cr.yp.to as their bible.

      --
      Linux: The world's best text-adventure game.
    12. Re:Reasons why DJBDNS is not more common by Saucepan · · Score: 1
      <sarcasm>You know, a binary format would be even easier to parse!</sarcasm>
      What? No it wouldn't. Have you ever tried to write code for a binary format? Among other things you need to worry about packing, integer bit widths, and byte order, none of which are standardized across compiler/OS/machine architecture. There's reasons IT as a whole is switching en masse over to text-based formats like XML (and it sure isn't for performance).

      Anyway djb's file formats are universally trivial for even a human to read once you know the invariably-simple notation, and unlike other ad-hoc fomats they have the advantage of rigorous semantics.

    13. Re:Reasons why DJBDNS is not more common by geniusj · · Score: 1

      I've found dan's documentation to be quite good. Most of his documentation is in a step by step format, and after following it you have something that works.

    14. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0
      Umm, have you ever tried to write code for a text format? At least in C (which is what these system-level daemons tend to be written in, after all), you have to do all this buffer management in order to handle variable length strings. Oh, wait, you mean I can't input strings of arbitrary length? Your program sucks.

      Then you have the whole line ending fiasco, and what about multiple character sets and other internationalization issues? Oh, you mean I can only use ASCII? Your program sucks.

      Then text formats aren't necessarily easy to parse, either. Most of the text parsing is done either by third party libraries, by language constructs, complicated regular expressions, or custom parser generators like lex+yacc. Trying to write a text parser by hand involves creating a complicated state machine to handle all the state tracking for the language parsing, at least if you're doing it right. Doing it poorly, of course, is always the easy thing to do. And then your program sucks.

      Text formats are valuable because they can be interchanged easily, modifiable by humans, and are usually flexible enough for future extension (due to the unlimited stream processing model), not because they're easier to parse. You don't actually have to parse XML, as there are many libraries that will do it for you. XML is sufficiently rigid and self-consistent that it's easily parseable by computer (part of the original design motivation).

      Maybe the binary formats you've tried to use involve dumping in-memory structures directly to disk (never a good idea even when you're going to be running a single program on one machine). That makes about as much sense as dumping raw strings to disk.

      To debunk each of your objections one by one (assuming C, which I gather you assume since you're talking about compilers and multiple architectures; higher level languages obviously have all this abstracted out):
      • Packing isn't relevant except as pertains to in-memory structure, and as mentioned before, you should never dump in-memory structures to disk. What are you going to do about pointers if you followed that scheme?
      • Bit widths are also irrelevant, as C standard I/O works with bytes/characters. While the in-memory representation of a byte/character is undefined (as long as it's at least 8 bits), it is still the smallest indivisible unit (there's no I/O on a scale smaller than 8 bits), so it's not relevant. If you're talking about converting to and from integers larger than a byte, you'd have that problem with text, too; just because you have 5485485848548 in a text file doesn't mean you can do anything useful with it on a 32-bit machine, without using something like GNU MP (which is overkill in most cases).
      • Byte order is easily handled with the hton functions (which are available even on Windows; basically, any network-oriented program needs them), or using a byte order mark (the approach taken by UTF-16 files, which, BTW, also have to be supported by any conforming XML parser--well, what do you know, XML has byte order issues, too, surprise, surprise). Without any known exceptions, machines are either little endian or big endian, and you can easily write conversion routines/macros yourself, and test easily for byte order at configuration time or run time. Byte order obviously doesn't matter for byte-oriented data.

      Binary formats are rarely chosen for performance reasons (except in cases like databases, where being able to seek to arbitrary points in a blob of data is useful). Binary formats are easier to write, which is why many programs which aren't intended for universal distribution make use of them. Binary formats can be the right tool for the job in many circumstances. Now that we have XML parsing libraries, it's less true that binary is easier, but when the overhead of a fairly complex external parser is unwarranted, binary formats are reasonable and easy to hack together.

      Besides, text formats suck at representing truly binary dat

    15. Re:Reasons why DJBDNS is not more common by Nevyn · · Score: 1
      It doesn't support caching

      djbdns does support caching. Anyway, you should be using different programs to cache and serve up authoritative data. Some of BIND's security problems were caused by its combination of cachine and authoritative data, so that is no longer a recommended configuration.

      I remember it being non-trivial. BIND has had more than a few code problems, so this is more an indication of experience/talent/awareness/whatever than which features are good. And it might now no longer be "recommended", but only the largest organisations follow that recommendation (hell look at the article, over 50% of the bind servers, over a third of all DNS servers, are returning packets with the RA bit set).

      And, to be frank, a lot of recommendations to do with DNS are of the form. X has traditionally been done way Y, so it's recommended you do X way Y ... no sorry we don't have any real data to back that up.

      --
      ustr: Managed string API with ave. 44% overhead over strdup(), for 0-20B
    16. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0

      Let me be clear: he's WELL WITHIN HIS RIGHTS, and he's even going out of his way to distribute his stuff, which is great. But to say "I'm going to play ball with you, but only if you use my ball, and in the following ways" doesn't fly for me. There are many good alternatives to his code, and they all have their own advantages and disadvantages. Thanks for playing, though.

      But what are those alternatives besides bind and djbdns? Are there any other good ones? Do you have any experience? Because talking from my experience there's either bind or djbdns.

    17. Re:Reasons why DJBDNS is not more common by ajs · · Score: 1

      Those are the two most widly used. Then there's the Windows DNS and many special-purpose servers (usually caching only, though I'm pretty sure there are one or two other full implementations).

    18. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0

      In other words, you recommend/personally use bind, right? I'm asking because I am starting a server soon and I'll have to choose something. Thanks.

    19. Re:Reasons why DJBDNS is not more common by ajs · · Score: 1

      I use bind, yes. I would probably not poke a stick at the MS server, much less use it in production.

    20. Re:Reasons why DJBDNS is not more common by Anonymous Coward · · Score: 0

      Thanks a lot.

  16. BIND is like weeds! by whitelabrat · · Score: 2, Interesting

    How the heck do you get rid of BIND? It's everywhere unless your a MS Windows shop that is ruled by DDNS... but most folks I know won't expose DDNS directly to the internet, cause you know why... BIND often acts as an intermediate.

    I know there are better alternatives out there, but why aren't they more popular?

    - When you insult a troll, he wins.

  17. sendmail shows this to be true by millahtime · · Score: 2, Insightful

    The fact that sendmail is also frustrating, is default install on Linux and BSD, and is the most popular for mail shows that this theory is pretty much true.

    I also know I am amungst the lazy ranks.

    1. Re:sendmail shows this to be true by dekemoose · · Score: 3, Insightful

      Wrong. Bind and Sendmail are defaults because they are the most prevalent. They are the most prevalent because they've been around a long time. Sendmail was the MTA of choice on UNIX years before Linux was common, ditto Bind for dns. Since they have the history, there are a lot of people skilled with using both of these packages, despite the "difficulty" setting them up.

    2. Re:sendmail shows this to be true by idiotnot · · Score: 2, Interesting

      Many Linux distros have ditched sendmail by default, and NetBSD now ships postfix in the base system. In fact, the only big linux distros that I can think that still ship sendmail by default are slackware and redhat/fedora.

      I *hate* bind with a neverending passion. I still use it because I'm not ambitious enough to change the environment I've got.

      Is it laziness? No, not really. It's just not wanting to mess things up. I did recently move a large mail server off Irix/sendmail to FreeBSD/qmail, and, while it worked pretty much as I wanted it to, wasn't a one-day task.

    3. Re:sendmail shows this to be true by grahamlee · · Score: 2, Interesting
      sendmail...is default install on Linux and BSD

      Oh? I appear to have Postfix as the default MTA on my SuSE and Darwin/BSD machines, not sendmail. The only machine I own with a sendmail default MTA is running NeXTSTEP 3. It didn't come with the m4 macros for editing sendmail.cf - now editing *that* was a fun half hour.

    4. Re:sendmail shows this to be true by stilwebm · · Score: 2, Interesting

      It's worth noting that as of OS X 10.3, Postfix has replaced Sendmail as the default MTA. NetBSD is integrating it in to the base install and letting the user decide between Sendmail or Postix, the default being neither is enabled at startup. Both use BIND 9 as their named by default, however.

    5. Re:sendmail shows this to be true by Anonymous Coward · · Score: 1, Informative

      Mandrake has shipped Postfix as the default MTA for years (since at least the 7.x days). I much prefer Postfix to Sendmail, which is one of the reasons why I mainly use Mandrake instead of Red Hat. I am lazy too... :-) I could install Postfix on Red Hat and tweak a lot of other things to be the way I like them (I've been using Linux since the kernel 0.99 days), but Mandrake out of the box is much closer to the way I like things.

    6. Re:sendmail shows this to be true by random_static · · Score: 2, Insightful
      as has been noted, postfix seems to be edging out sendmail as the default MTA in most distros.

      i don't think the situation is all that analogous with DNS servers, though. sendmail is and always was an unbelievable mess to set up and maintain; the mere fact that a bunch of m4 macros was considered an improvement on the config system that preceded them should tell you something. (if it doesn't, you haven't had much exposure to m4. count that a blessing and keep away from the thing.)

      by comparison, BIND versions >= 8 are simple, straightforward and eminently sensible both to configure and to keep running. as well, BIND's had its share of security problems, but nothing has nearly as awful a security track record as sendmail, not by a long shot.

      finally, the cricket book is about half the size of the bat book, maybe less. i don't know about you, but that tells me BIND is a smaller, easier to learn system than sendmail.

    7. Re:sendmail shows this to be true by Anonymous Coward · · Score: 0

      amungst the lazy? I guess using your forefinger to reach the u key is easier than using your ring finger to reach the o key ...

    8. Re:sendmail shows this to be true by Anonymous Coward · · Score: 1, Funny

      Its because you're a pussy... Thats why you don't like sendmail. People like you stray from sendmail becuase they can't hack a cf file. If you can't hack sendmail rulesets by hand, you shouldn't be running a core internet service. Sendmail is the only real mta software out there.

      From Zero To Flaimbait in 0.21 seconds.
      -AC

    9. Re:sendmail shows this to be true by MobyTurbo · · Score: 1
      NetBSD now ships postfix in the base system.

      NetBSD offers both sendmail and postfix. An interesting exception to it's usual "no bloat" policy.

    10. Re:sendmail shows this to be true by elemental23 · · Score: 1

      Just to add to the list, Debian installs Exim by default, not sendmail.

      --
      I like my women like my coffee... pale and bitter.
    11. Re:sendmail shows this to be true by Anonymous Coward · · Score: 0

      Bind and Sendmail are defaults because they are the most prevalent.

      Yeah - They are the defaults because there was no choice for most of the history of commercial UNIX - Sun, IBM, HP, SGI, AT&T, whoever sent a damn distribution and it had ls, cat, ps, bind, sendmail, rm, etc.
      They are the defaults because all the systems followed that basic pattern, they were part of the UNIX-y userland crap that you "get".
      Only recently have systems where choosing alternatives as part of your "dist" become commonplace. As those modular systems become more popular and people want multi-user DNS and mail management and administration tools packaged in with DNS and mail servers, those old standards that stood because of lack of effective choice, will steadily fall in usage.

  18. The reason DjbDNS hasn't been updated in forever.. by Sevn · · Score: 5, Informative

    Is because it has been done forever. Instead of the exploit a year phenomenon you have with Bind, there haven't been any yet. When Bind can take 10,000 requests per second on a dual Xeon box (used for MAPS) and not melt into a smoky plastic dog treat, let me know. Don't get me wrong. Djb is slightly, well, he comes across as a bitter man with something to prove. And I can't stand qmail. But he hit the nail on the head with DjbDNS. I've got nearly 240 domains with a combined total of over 125,000 records hosted with no problem.

    --
    For every annoying gentoo user, are three even more annoying anti-gentoo crybabies. Take Yosh from #Gimp for example.
  19. Why they keep BIND around by reaper · · Score: 5, Insightful
    • It's in practically every distro by default
    • Not a whole lot of people really need the hassle of installing another DNS server
    • It is the standard by which other implementations get judged
    • It supports just about every obscure feature known to the DNS world
    • If you know how to hack the config files, it makes manually setting up tons of vhosts dirt simple
    • The name is just so powerful
    • Certain other dns server authors(*cough*djb*cough*) always manage to piss off too many people, even when they are proposing a superior solution to a problem.
    --
    - Dan
  20. One Ring by soloport · · Score: 2, Funny

    "To rule them all.
    And in the darkness BIND them."

    Like, Duh... So obvious.

    1. Re:One Ring by stud9920 · · Score: 2, Funny

      One Token ring ?

    2. Re:One Ring by bugnuts · · Score: 1

      No, silly... a Tolkien Ring.

  21. Hasn't been updated in years?? by embo · · Score: 5, Interesting

    ...since D. J. Bernstein's hasn't been updated for years...

    Maybe because it hasn't needed updating.

    http://cr.yp.to/djbdns/guarantee.html

    1. Re:Hasn't been updated in years?? by Anonymous Coward · · Score: 3, Informative

      Maybe because it hasn't needed updating.

      He meant the *survey* hasn't been updated, not the software. Even if it wasn't obvious from the language (and I think it was!) it should have been obvios from the link.

    2. Re:Hasn't been updated in years?? by Lxy · · Score: 3, Funny

      Maybe because it hasn't needed updating.

      a qmail user are you? :-)

      --

      There is no reasonable defense against an idiot with an agenda
      :wq
    3. Re:Hasn't been updated in years?? by WoodstockJeff · · Score: 2, Informative
      What needs updating with DJBDNS is DJB's attitude. If he'd allow binary distributions, I'm sure several major Linux distros would make it the DEFAULT DNS server for workstation installs, and optional for server installs.

      As it is, I read the "quick how-to" files on setting your system up to work with djbdns, and find them far more confusing than BIND zone files and configuration files ever were. You don't just have to worry about one program - unless you're ONLY running the caching server.

      This doesn't mean I'm not looking at alternatives... I dislike having to restart all the servers every time I add a domain, and having to restart the master every time I modify a domain, with BIND.

    4. Re:Hasn't been updated in years?? by dougnaka · · Score: 1
      The files compared to BIND as confusing is interesting. When I first migrated from BIND I thought the same thing, but it's really pretty simple, here's a sample DNS file:

      =www.pirateraps.com:67.41.185.14:3600
      =mail.pirateraps.com:67.41.185.14:3600
      .pirateraps.com:67.41.185.14:a:43200
      .pirateraps.com:64.90.206.19:b:43200
      +pirateraps.com:67.41.185.14:3600
      @pirateraps.com:67.41.185.14:a::3600

      The first character on a line is the type of record, = is an A record, + is an alias, . is a dns server, and @ is a MX/mail record, that's cake.
      Then you have the FQDN or domain name, then the resolution IP. Now 1 thing that got me was the mail server name, this says 67.41.185.14 is an MX but didnt specify its name, tinydns puts in the next value .mx. So in this case it's a.mx.pirateraps.com, if I had a second one it would be b.mx.pirateraps.com.
      The next part of the line is the server (a,b,c,d,etc.) for NS and MX entries, and the last part is the TTL. On MX entries there's one more thing between the server(a|b|c) and the TTL and that's the weight.
      Now, to me that's cake.

      --
      My Linux Command of the Day site : LCOD
    5. Re:Hasn't been updated in years?? by WoodstockJeff · · Score: 1
      The zone file might be simple, but getting to the point of USING the zone files isn't - which is what I commented upon.

      If DJB allowed distributors to bundle working copies of his program on their disks, all would be fine and dandy... but I don't want to spend time searching for the proper group of tools needed to get it to compile before I can use it, and most others don't, either. I've never had to compile BIND to put a DNS server up... And I'm not afraid of doing so, if I had to, but I don't want to.

  22. Other Servers? by Anonymous Coward · · Score: 1, Insightful

    You mean there are other DNS servers? Holy sh*t! I've actually used a couple of different ones on pre OS X Macs. DNS servers more than most other pieces of software are invisible until it breaks. You just never really think about it once you get the sucker running(unless you do something serious as opposed to what I do). Plus in the early days, the Internet was large public research project whose infrastructure was made by task forces rather than market forces, so a task force made a tool for the job and that was that. Combine that with the inertia that builds up behind a successful product and there's little incentive to change. We know it, we like it, it works, and it's free. Why bother with anything else unless you're running Mac OS 8 or something funky like that?

  23. In the article by Anonymous Coward · · Score: 1

    He explains exactly how he fingerprints DNS servers and also gives the percentage of servers that he was not able to fingerprint(mostly due to timeouts).

  24. qmail: never a security lapse. by Russ+Nelson · · Score: 2, Informative

    The question is whether the flexibility is worth the security cost imposed by the extra complexity required to get the flexibility. I say no, and run qmail. It's the only MTA that has never had a security lapse. (actually, Courier might not have had one either, but who runs Courier?)
    -russ

    --
    Don't piss off The Angry Economist
    1. Re:qmail: never a security lapse. by richie2000 · · Score: 1
      who runs Courier?

      *raises hand*

      :-)

      --
      Money for nothing, pix for free
    2. Re:qmail: never a security lapse. by spacey · · Score: 2, Informative

      I second that raised hand.

      Went qmail->courier. A bunch of things the suite as a whole does makes it even easier to setup than postfix. I.e. I can set up virtual users and a virtual domain and have the mail server and lda and imap and pop3 server etc. etc. etc. all work from the same auth database with the same schema, whether the database is ldap, mysql or postgres with very little tweaking.

      -Peter

      --
      == Just my opinion(s)
    3. Re:qmail: never a security lapse. by jonadab · · Score: 1

      > It's the only MTA that has never had a security lapse.

      The only *major* one perhaps...

      > (actually, Courier might not have had one either, but who runs Courier?)

      There are also other less-well-known options that don't have security problems.
      Generally they also don't have tons of features, granted.

      *Eventually* I want to write an entire mail-handling system in Perl. I've got
      a working POP3 server. I want to do IMAP next...

      --
      Cut that out, or I will ship you to Norilsk in a box.
    4. Re:qmail: never a security lapse. by Feyr · · Score: 1

      i also run courier.

      afaik, it has had a few (1 or 2) very minor security lapses in very specific circumstances. though they might not have been in the MTA (i recall one being in maildrop)

    5. Re:qmail: never a security lapse. by abulafia · · Score: 1

      Hm, I use Courier for POP/IMAP, postfix for SMTP/LDA, with the same schema (sitting in postgres). What problems were you having with getting a single schema to work?

      --
      I forget what 8 was for.
  25. Why BIND is popular by Anonymous Coward · · Score: 0

    djbdns simply is not as feature complete. Want zone transfers? Want CHAOS records? Want TSIG keys? Want a reasonable configuration syntax?

    The fact is, djb staunchly refuses to incorporate features into his various software packages, resulting in a product that's simply less useful. I never thought I'd be defending any ISC products, but BIND surpasses djbdns.

    1. Re:Why BIND is popular by Russ+Nelson · · Score: 1

      djbdns does zone transfers. If I need BIND's insecurity to get CHAOS records, I'll do without CHAOS records, thankyouverymuch. The configuration syntax is designed to be parsed by a program. If you don't like it, create your own syntax. Writing a tinydns data file is easy enough.
      -russ

      --
      Don't piss off The Angry Economist
  26. If DJB were.. by jayminer · · Score: 5, Insightful

    If DJB were not such an ass, his software would be on everywhere now. He is smart, you can feel that. But come on, he thinks that if he has thought about something, it's right and it cannot be disproved. You simply can't. He won't accept a thing.

    Look at where daemontools installs itself, and of course the other thingies from him, like djbdns and qmail. The default directories cannot be changed (/service, /package etc.), and if you change them from the source, you violate his license!
    He's still refusing to fix the extern int errno; problem, because he thinks that it is not a problem. (Everybody should follow his standards, not glibc or anything like that) He still does not apply QMAILSCANNER patch into qmail. You need to go and get netqmail for that, or apply the patches it provices manually. You cannot distribute a patched qmail, therefore you cannot distribute a proper qmail package for your distribution without begging him!

    djbdns assumes that you have a.ns.yourdomain.com b.ns.yourdomain.com etc. The add-ns program does not even get any argument about that. (Of course, you can edit the files manually).

    And as far as I know, many distributions kicked his software out, including several *BSDs.

    1. Re:If DJB were.. by arcade · · Score: 2, Informative

      Normally I don't like AOL! -messages, but I really want to echo what you say. I used to love qmail back in '98, and love the rest of djb's software too.

      After working with his software for some years, I've come to senses. His software is excellent, but he don't maintain it. He maintains that you have to apply a host of third party patches. You cannot modify the sources and redistribute them.

      In the long run, it sucks.

      Postfix and Exim are my current favorite MTA's. BIND is just the standard dns server. I've considered looking into djbdns - but I'm afraid that I'll burn myself if I try it. I don't trust DJB and his software at all - after watching how qmail has detoriated through non-updates during the last 6 years.

      --
      "Rune Kristian Viken" - http://www.nwo.no - arca
    2. Re:If DJB were.. by zyche · · Score: 1
      IIRC, OpenBSD has refused to include qmail in its portstree since DJB refused to state a licence for it. He thinks that no licence = public domain.

      Or something like that...

    3. Re:If DJB were.. by quantum+bit · · Score: 1

      Postfix and Exim are my current favorite MTA's.

      Agreed. Postfix has rapidly gone from somebody's pet project for a more secure mail server to one of the best MTAs out there. It's extremely stable and robust, and very flexible and feature-rich too. What you can do with it is second only to sendmail -- and I don't really consider writing code in a turing-complete configuration script to be configuration anyway (and Postfix can already do everything that sendmail's canned m4 macros can).

    4. Re:If DJB were.. by Dwonis · · Score: 1

      How's postfix's security record? i.e. Can I set up a postfix server, then go on an 18-month holiday and be confident that my box will still be working when I get back (like I can with qmail)?

    5. Re:If DJB were.. by brj · · Score: 1

      I've got to agree with your "ass" comment. It's all about attitude. If he weren't such an ass, and if his followers didn't have that same attitude, I might consider it.

    6. Re:If DJB were.. by GPLDAN · · Score: 1

      I know a couple people who were DJB's students at UIC. They weren't too happy with his instruction, let's just say that.

    7. Re:If DJB were.. by quantum+bit · · Score: 5, Insightful

      How's postfix's security record? i.e. Can I set up a postfix server, then go on an 18-month holiday and be confident that my box will still be working when I get back (like I can with qmail)?

      You can be very confident that it will be. Postfix uses privilege separation, runs as its own user account (not root), and is designed with a chroot environment in mind. It's also very componentized and designed so that a breach in one component can be isolated without a risk to the others. To the best of my knowledge, there has never been a remote code execution vulnerability in Postfix.

      The last major security problem was a year ago and was just a DoS possibility. Even qmail has DoS problems. Before the DoS, in 2002 there was a problem that might allow someone to use Postfix to portscan another system (no risk to the system running Postfix). Both of these were in the older 1.1 version. The 2.x series, released in 2002, has never had a security problem bad enough to warrant an advisory for.

      The only other thing I could find is djb ranting about a Postfix problem that has been fixed for over 6 years.

    8. Re:If DJB were.. by Simon+Lyngshede · · Score: 1

      I considered using Postfix, simply to get any from qmails no license thing, but found it a major pain to play around with. When you come from qmail, the configuration files in Postfix can be really annoying and stupid. It isn't as bad as in sendmail, but close.

    9. Re:If DJB were.. by Anonymous Coward · · Score: 0

      "Bugs happen. Perhaps more unusual is that the two problems reported
      today by Michal Zalewski were fixed nine or more months ago and
      that the fixed code has been publically available all that time.

      Number one was fixed as the accidental side effect of a code reorg.
      Number two was fixed by an explicit bugfix (not thought to be
      security related at the time). Unfortunately, number two did not
      feature in Michal's draft advisory that I worked off last week;
      I'd happily have fixed some technical inaccuracies in his text.

      This episode is a reminder that bugs don't necessarily go away even
      when they are fixed. Once the source code goes out the door you
      no longer control what happens with it. The result is that people
      can discover old fixed bugs in "brand-new" software.

      This phenomenon is far from new. As someone told me in private
      email, Robert Morris Sr. lamented that he personally had fixed some
      of the security bugs in the UNIX utilities back in the late '70's,
      but they were still being exploited almost 20 years later.

      Wietse
      "

      This is one reason I do not trust postfix. Bugs just don't happen. Bad programmers just happen.

    10. Re:If DJB were.. by Anonymous Coward · · Score: 0

      erhmm Debian distributes a tool that fetches the original qmail source, patches it and makes a debian package you can install... same goes for t inydns/daemontools...

      which is pretty neat because his tools is simple, they just work - there is a REASON why he haven't patched or updated anything in years :P ...

    11. Re:If DJB were.. by Paul+Crowley · · Score: 2, Interesting

      What you can do with it is second only to sendmail

      In what way is it behind sendmail? Genuinely curious...

    12. Re:If DJB were.. by quantum+bit · · Score: 1

      Well, "beind sendmail" is something that I would definitely put in quotes. IMHO, anything useful that sendmail can do, postfix can do also. The only area where sendmail is more flexibile is for doing things like REALLY complicated and arbitrary routing where you basically have to write a program to make the decisions in real-time. Anything sane postfix should be able to handle with regex rules.

      That and things like playing Towers of Hanoi in the sendmail .cf file...

    13. Re:If DJB were.. by Anonymous Coward · · Score: 0

      No, its called copyright law. He believes in that. Read up on it at http://cr.yp.to/

    14. Re:If DJB were.. by random_static · · Score: 2, Informative
      postfix certainly has a lot more configuration than qmail. (or what i remember of qmail - it's been a few years now, for me.) but it's not really that hard of a configuration, at least not if you use any non-bernstein software. unless you've thoroughly soaked in dan's one-line-per-file, all-machine-parsable, damn-human-readability configuration syntax kool-aid, postfix is fairly ordinary as Unixish config files go.

      the only real quirks are that postfix uses about a dozen different files for different purposes / subsystems in the herd of daemons that make it up, and that a few of 'em have to be "byte-compiled" into berkeleyDB format to improve access speed before the daemons proper will read 'em. getting used to these is no harder than getting used to djb's, shall we generously call it, unusual mindset on what makes a config file good.

      and, frankly, several of djb's config files look a lot more like sendmail.cf to me than any of postfix's ones. it's the same machine-readability-über-alles principle in 'em both, if you ask me. postfix generally doesn't play that mindgame on you, certainly not nearly as much.

    15. Re:If DJB were.. by eternal · · Score: 0

      I just dropped qmail after 5 years because no updates and had to hack to much shit to get a up2date MTA. Went to surgemail

    16. Re:If DJB were.. by velkro · · Score: 1

      You just contradicted yourself. You state there are tools to patch his software, and then in the next sentence state they don't need to be patched or updated.

      I agree with the distros: If I can't patch it and ship it, I don't ship it.

    17. Re:If DJB were.. by flinkflonk · · Score: 1

      This is one reason I do not trust postfix. Bugs just don't happen. Bad programmers just happen.
      Strangely, the same kind of people who post stuff like this (anonymously nonetheless) are saying djbdns is bugfree. DJB is a better programmer than Wietse Venema exactly how and why?
      In his (Wietse's) own words: "I consider myself to be a very cautious programmer, so I guess my code hasn't more than about one bug per 10000 lines." (he said that when he spoke at SANE98, presenting postfix (then still called vmail) and probably numerous other times). I think this is quite good because humans are after all just that, human. Even DJB, as much as he wants to show the world he's a machine.
      On the other hand, has DJB fixed the numerous bugs in qmail that violate RFC821 and RFC822 (hey, these are only 22 years old by now)? For example something as trivial as the timezone bug? If not, I think DJB is a Bad Programmer (tm) and nothing you can say can get me from that.
      Regarding djbdns, it might be a good package, but since I am not allowed to change it, it's as useful to me as, say, Microsoft Word would be for the same purpose. I think it has to do with his ego, because who knows, somebody might take his code and make it both readable AND functional :)

  27. The alternatives by Florian+Weimer · · Score: 5, Insightful

    The alternatives have not-so-subtle incompatibilities with BIND and existing practice, are not proven in the field, or are unmaintained by the original developer. In fact, BIND is often deliberately incompatible with its previous versions, so it shouldn't be too hard to beat it in this area, but apparently it is.

    tinydns, which was mentioned by the story submitter, is unmaintained, like most (if not all) software that Mr Bernstein has ever released. (This is especially problematic because Mr Bernstein refuses to license the software for a fork.) It does not even compile on modern systems, and it uses a non-standard zone file format. In the days of BIND 4 and BIND 8, all that pain was probably justified, but with BIND 9, things are rather different.

    In my experience, in the area of caching full resolvers, BIND 9 simply lacks serious competition, feature-wise, and in terms of ease of administration and interoperability. For authoritative-only servers, RIPE's nsd is an alternative, but BIND 9 is typically not such a big trouble that running two different name servers is really needed.

    1. Re:The alternatives by ldspartan · · Score: 1

      This is especially problematic because Mr Bernstein refuses to license the software for a fork.

      Bullshit. DJB doesn't allow forks of the same name. qmail was recently forked into something called 'netqmail' that integrates the most popular, bug-fix packages that are out there.

      --
      lds

    2. Re:The alternatives by quantum+bit · · Score: 2, Insightful

      qmail was recently forked into something called 'netqmail' that integrates the most popular, bug-fix packages that are out there.

      ...which can only be distributed as a set of patches against the original code. This means no binary packages, either. djb's license forbids the distribution of modified versions. qmail is not open source. It's actually a lot closer to Microsoft's shared-source license.

    3. Re:The alternatives by Russ+Nelson · · Score: 1

      Um .... tinydns doesn't need to be maintained, because people aren't finding security holes or bugs in it on a weekly basis. Really, your expectation that software has bugs and needs to be maintained bangs square up against djb, and stops.
      -russ

      --
      Don't piss off The Angry Economist
    4. Re:The alternatives by sheriff_p · · Score: 1

      Which modern systems are those exactly? I've never had any trouble getting it to compile...

      When you say unmaintained ... surely that's just because there's been nothing to change about it? Are there outstanding bugs?

      +Pete

      --
      Score:-1, Funny
    5. Re:The alternatives by Florian+Weimer · · Score: 2, Informative

      Um .... tinydns doesn't need to be maintained, because people aren't finding security holes or bugs in it on a weekly basis.

      tinydns doesn't even compile on modern GNU/Linux systems. Surely this is a bug in tinydns, isn't it?

    6. Re:The alternatives by Florian+Weimer · · Score: 5, Informative

      Which modern systems are those exactly? I've never had any trouble getting it to compile...

      Systems with a recent version of GNU libc.

      When you say unmaintained ... surely that's just because there's been nothing to change about it? Are there outstanding bugs?

      It's not bugs, it's lack of features: IPv6 support, CIDR support for dnscache configuration, maybe even DNSSEC even you want to give it a try.

    7. Re:The alternatives by PlusFiveTroll · · Score: 1

      DNSSEC, sweet, doesnt do much although....
      DNSSEC: theory and practice
      You must be the one spilling so much tripe on his mailing lists over the years.

    8. Re:The alternatives by Florian+Weimer · · Score: 2, Insightful

      Yes, I know that DNSSEC has its drawbacks, but so far, DJB has only argued against it, without providing a real alternative (or even fully describing it).

      Others offer (well, sort-of) working DNSSEC implementations, which might be a reason to use these implementations instead of tinydns. Of course, the overall need for DNSSEC implementations is pretty low on the current Internet, even though everyone wants a secure DNS (kind of a chicken-and-egg problem).

    9. Re:The alternatives by shepd · · Score: 1
      I'm still trying to understand how:

      tar -zxvf new-qmail-or-djbdns-hack-full-version-includes-ori ginal-6.66.tar.gz
      less BIG-IMPORTANT-README

      ... [snip] ...
      STEP #1 - Run the following:
      zcat patch.gz | patch
      prior to installing.

      STEP #2 - Install as normal
      Makes this software something from depths of hades. Can you enlighten me?
      --
      If you could be told what you can see or read, then it follows that you could be told what to say or think - BoC
    10. Re:The alternatives by Anonymous Coward · · Score: 0

      >tinydns doesn't even compile on modern GNU/Linux systems. Surely this is a bug in tinydns, isn't it?

      Not as long as it compiles on slackware, which is still being maintained, daily. Perhaps you run some old sort of shitty distro that comes with a hacked up and totally beta copy of GCC, and probably a patched to hell kernel to boot, but why the hell should we care about that?

      I don't care if your distro is popular, McDonald's serves the world's most popular burger, and you don't see people suggesting there's something wrong with your digestive tract being less-than-proper rather than the burger being made of absolute trash if it gives you the shits.

    11. Re:The alternatives by geek · · Score: 1

      What are you talking about? It compiles fine on everything I've tried. It even compiled on OSX Panther.

    12. Re:The alternatives by quantum+bit · · Score: 1

      ... Makes this software something from depths of hades. Can you enlighten me?

      I never said that it was. I don't have a problem with that method of distribution. It's his software, he can require users of it to dance a jig before installing for all I care. I was just pointing out that by most definitions, it's not "Open Source" (see section 3). It's more of a look-but-don't-touch license.

    13. Re:The alternatives by AndyRobinson · · Score: 1
      I'm still trying to understand how ... Makes this software something from depths of hades.

      It doesn't. But it does mean that an otherwise useful / good / promising bit of software isn't maintained or developed as much as it could be.

      The real thing for me - and by the sounds of it quite a few other people - is that I just don't really understand DJB's reasons. If he released it under a commercial license I could see that he'd want to keep the money. If he's worried about maintaining the 'purity' of the original work, he can keep distributing the 'official' version as is but allow other people to patch it. If he doesn't like the GPL there's about a million other licenses he could use, etc, etc.

      Of course he wrote it so it's his software, his copyright and he can do what ever he likes with it. I just don't quite understand what he gains from not letting people improve upon it and then distribute any improvements in a more convenient way.

      That doesn't make DJB the devil incarnate or anything - it's just a shame, that's all.

    14. Re:The alternatives by PitaBred · · Score: 1

      Oh, it compiles on Slackware. As soon as you edit the source to make it happy with the errno bugs. ANY modern distro of Linux isn't happy with TinyDNS. It's a pain in the ass, and the license is dumb. I'll stop now before I reiterate too many things.

    15. Re:The alternatives by Farce+Pest · · Score: 1
      glibc fix:
      sed -i -e 's/extern int errno;/#include <errno.h>/' djbdns-1.05/error.h
      IPv6 support Available with a patch, if you really need it, and most people don't. CIDR support for dnscache Largely irrelevant. For common sizes (/24, /16, /8), you touch one file. Worst case is something like 10.0.0.0/25:
      for i in `seq 0 127`; do ln 127.0.0.1 10.0.0.${i}; done
      (Uses hard links to save inodes, and assumes you allow localhost to use the cache.) DNSSEC If you really think you need it, use BIND. You said (in another comment), "Of course, the overall need for DNSSEC implementations is pretty low on the current Internet," and with BIND still being as wide-spread as it is and still hardly any use of DNSSEC, I don't see how it's a really compelling issue for djbdns/tinydns/dnscache.
      --
      This message has been scanned for memes and dangerous content by MindScanner, and is believed to be unclean.
    16. Re:The alternatives by random_static · · Score: 1
      maybe not the depths of hades, but it definitely leaves the door to pandemonium unlocked and ajar.

      having to install software by means of source tarball and bunch of patches makes it that much harder to integrate with your favourite package management system. (rpm, apt, whathaveyou. maybe the gentoo users have something like a solution to this - does emerge track what it installs where and when, like RPM does? i sure hope so!)

      this matters to those of us who use one machine to do more than one thing, because tracking which files belong to which package installed at what date gets painful when you have a lot of packages all installed by tarball plus patches, especially if it's done over a long span of time or by more than one person. you want to keep track of that, because otherwise you can't ever be really sure some random file is needed; that the new tarball you just did "make install" on didn't trample some file in /usr/etc or wherever that another tarball needed not to have trampled; or that "make uninstall" won't wipe out a .so you'll need the next time the server must be rebooted. package managers track all that metadata for you and make handling a multi-use server or workstation a lot easier, because they give you one single place to go to for finding it all.

      sure, you can build your own source RPM to do this for you. it is possible to maintain your own .spec files for insert-random-number of packages you want to use whose maintainers would like for you to install by tarball instead. but unless doing that and that alone are all your job duties, you'll probably just download postfix in the vendor-provided RPMs instead and forget about it, because that very same server has all these other software packages that won't maintain themselves, either, and your life is just too short.

    17. Re:The alternatives by Electrum · · Score: 1

      are not proven in the field

      directNIC is running MyDNS and is currently serving 3.2 million queries per hour.

    18. Re:The alternatives by Russ+Nelson · · Score: 1

      The solution to that is obvious: don't run GNU/Linux. Run Linux instead.
      -russ
      p.s. my point being that GNU broke the C library. How is that djb's fault?

      --
      Don't piss off The Angry Economist
    19. Re:The alternatives by ZeekWatson · · Score: 1
      What are you talking about? It compiles fine on everything I've tried.

      Lemme guess. You didn't try to compile it on anything so that makes "It compiles fine on everything I tried." a true statement.

      slashdot logic triumphs no doubt. But in the end you are clueless or lying.

    20. Re:The alternatives by geek · · Score: 1

      Back to your cave troll. There is a reason you don't get a karma modifier, and this post is it. Now go sniff mommies panties and pop some more zits.

    21. Re:The alternatives by dododge · · Score: 1

      The stock versions of DJB's programs (qmail, djbdns, daemontools, and so on) usually include his error.h file, which contains this bug:

      extern int errno;

      According to the Unix standard (SUSv3), that produces undefined behavior. On glibc-based systems it won't even compile cleanly. The fix is trivial; just replace the line with:

      #include <errno.h>

      and the problem goes away. Why he doesn't do this in the released versions, I don't know.

  28. Because it works. by morten+poulsen · · Score: 2, Insightful

    BIND - like Sendmail - is popular because it works. They might be ugly, buggy (as in security problems), whatever, but they are old and people know them.

  29. Anything but ... by anaplasmosis · · Score: 1, Interesting

    ... djbdns. Nothing to do with the software and everything to do with the attitude of its author.

    1. Re:Anything but ... by Russ+Nelson · · Score: 0, Redundant

      That would matter if you needed something from the author. Don't look at djbdns as a complete solution. Look at it as a toolkit for creating a dns server. It's like anything else in Unix -- it's designed to be part of a solution, pasted together using scripting. THAT is why Unix has been successful, not because of monolithic programs like BIND and sendmail.
      -russ

      --
      Don't piss off The Angry Economist
  30. I need a new DNS server by bgarcia · · Score: 1
    I'm currently using bind, but it doesn't work well at all for my current situation.

    I have a small home network. I also have a VPN to my work network. I would like to forward all DNS queries matching a particular domain or IP address range to the DNS servers at work.

    For all other DNS queries, I probably should forward them to my ISP's DNS servers, but I'm not too particular about that.

    My current problem is that my VPN isn't always running, and if BIND starts when the VPN is not up, then BIND doesn't work right. I have to restart it when the VPN is up, and then it is fine.

    So, any suggestions for a DNS server that can handle this situation?

    --
    I'm a leaf on the wind. Watch how I soar.
    1. Re:I need a new DNS server by csirac · · Score: 1

      dnsmasq

      Just works off you're /etc/hosts file. Uses /etc/resolv.conf for the upstream DNSs. Want DNS cacheing goodness on the dnsmasq box? Add localhost to /etc/resolv.conf.

    2. Re:I need a new DNS server by mhesseltine · · Score: 1
      My current problem is that my VPN isn't always running, and if BIND starts when the VPN is not up, then BIND doesn't work right. I have to restart it when the VPN is up, and then it is fine.

      So, any suggestions for a DNS server that can handle this situation?

      Um, edit the scripts that handle your VPN connection to include restarting BIND when your VPN connection comes up/goes down?

      --
      Overrated / Underrated : Moderation :: Anonymous Coward : Posting
    3. Re:I need a new DNS server by V.+Mole · · Score: 1

      I like dnsmasq and use it on my small home network, but it doesn't meet the requirements of the original poster: forwarding queries to specific servers based on domain name or ip. I realize that such a desire is fundamentally at odds with the way DNS works, but I've had many situations where such a capability would make life a lot easier.

    4. Re:I need a new DNS server by Anonymous Coward · · Score: 0

      http://cr.yp.to/djbdns/dnscache.html will do exactly this.

    5. Re:I need a new DNS server by bgarcia · · Score: 1
      That doesn't solve the problem.

      BIND is hosed for doing non-forwarding queries when it is started without the VPN being up. I know, you expected regular DNS queries to keep working normally, but they don't.

      --
      I'm a leaf on the wind. Watch how I soar.
    6. Re:I need a new DNS server by bgarcia · · Score: 1
      It sounds like that should work.

      I didn't see a download link, nor did I see a license. Kind of strange for what appears to be the official site to not have these things.

      --
      I'm a leaf on the wind. Watch how I soar.
    7. Re:I need a new DNS server by silas_moeckel · · Score: 1

      This sounds like pretty basic forwarding. Why do you have to restart your bind when the VPN is up? Are you trying to make it run as a secondary or something? Check out something like (this was the first match on google) http://www.zytrax.com/books/dns/ch7/zone.html you just specify one for the forward and reverse domains of your office to your office nameservers.

      Most people that complin about bind dont seem to know how to use it funny as it's got to be the most well documented and standard off all DNS servers.

      --
      No sir I dont like it.
    8. Re:I need a new DNS server by Anonymous Coward · · Score: 0

      Dnsmasq does meet the requirements of the original poster:

      dnsmasq --server=/somedomain.net/1.2.3.4

      will send queries for *.somedomain.net to the server at 1.2.3.4 and all the rest to ISP nameservers in /etc/resolv.conf

    9. Re:I need a new DNS server by bgarcia · · Score: 1
      Why do you have to restart your bind when the VPN is up?
      Because BIND wasn't designed to do forwarding, and the feature is pretty broken. If I start BIND without the VPN being up, ALL DNS resolution fails, not just resolution of the VPN-related addresses.
      --
      I'm a leaf on the wind. Watch how I soar.
  31. Re:probably reliability by Anonymous Coward · · Score: 0

    DNS/Bind is standard and reliable full featured DNS and is supported as part of the base OS. And it has a better security record than many other proprietary systems.

    Why would anyone use anything else?

  32. Offtopic by ipjohnson · · Score: 1

    are you still maintaining the qmail web site?

    1. Re:Offtopic by Russ+Nelson · · Score: 1

      yes. http://qmail.org/news.html or http://qmail.org/news.rdf and there's a Slashdot news feed for it.

      --
      Don't piss off The Angry Economist
    2. Re:Offtopic by ipjohnson · · Score: 1

      So would you be the person to report broken links?

      The reason I ask is because the links to the Clarkson submission's are broken. I'm sure there aren't to many AFS sites that run Qmail other than Clarkson so it really doesn't make to much of a difference.

      Do you still live up in the north country?

    3. Re:Offtopic by Russ+Nelson · · Score: 1

      Haha! Yeah, well, talk to Clarkson's IT department. Clueless weenies. Who ever heard of outsourcing your IT department? I guess that was better than Liz Rivet, who was Ms. Complete Disaster.

      I'll nuke it. Yes, I still live in Potsdam.
      -russ

      --
      Don't piss off The Angry Economist
  33. 5. DJBDNS is not Open Source by Paul+Crowley · · Score: 1

    Don't bother telling me about non-open source software to solve this problem, I have open source software that works. The same goes for Qmail.

    Though I think the way DJB licenses his gratis software is a shame, I'm not going to take part in the great flamefests about the man - to me, as a cryptographer, he stands as an indisputable contributor of genius to the field.

    1. Re:5. DJBDNS is not Open Source by flynn_nrg · · Score: 1

      Well, it is open source. Perhaps you mean it's not free software. Different meaning.

    2. Re:5. DJBDNS is not Open Source by Paul+Crowley · · Score: 1

      Read at least the first sentence of the Open Source definition, please.

      I also mean it's not "free software", but that term isn't as precisely defined, and some people (IMHO mistakenly) interpret it to mean merely "gratis software". The term "open source" was invented in order to act as a synonym for "free software" in this sense that did not have this ambiguity.

  34. What's wrong with bind ? by noselasd · · Score: 1

    Seriously. I use it, never had a problem with it. Not that hard to
    configure if you know how to read.
    In fact it's really amazingly much better than the alternatives. bind
    seems to support more features than most of them.
    ddns is important to me, works nicely used with dhcpd, I don't see
    how I would achieve that using other dns servers.

    1. Re:What's wrong with bind ? by Nonesuch · · Score: 1
      What's wrong with BIND?
      1. Root holes.
      2. Single monolithic application to serve multiple purposes.
      3. Memory hungry (process size grows unpredictably).
      4. Inefficient storage of in-memory copies of authoritative zones.

      Personally, when I am looking for software to run a critical service, I look for software that supports the feature set I need without any extraneous bells and whistles, and I prefer the "toolkit" approach, if I just need an authoritative server, I just want to run a program that does only that one thing, but does it exceedingly well.

      Many of the worst sins of BIND 8 have been expunged in BIND 9, but I do not doubt that we have not seen then end of BIND root exploits.

    2. Re:What's wrong with bind ? by Anonymous Coward · · Score: 0
      First off, I'll just say that I know JS about dns servers, but I just got to point out that your #1 reason for BIND sucking is that it has root exploits, which you then go on to say in your last sentence that they actually don't exist.

      Your last sentence basically says that BIND sucks because it might have root exploits in the future, but you can also say that about the one you advocate.

  35. method used in the survey by ubiquitin · · Score: 1

    Did the survey start with a long list of domain names, then seek out the DNS servers hosting them, or was it an IP scan, to randomly sample DNS servers, Netcraft-style. The choice of methods here will make a big difference on how your results turn out, especially given any biases which will be inherent in a domain name list. Thanks to Don Moore for the work, the DNS-server version percentage breakdowns were particularly revealing. More than half of bind installs are release candidates? Also, the prevalence of Windows2000 over other Windows flavors in doman name server roles says a LOT about how the "trustworthy computing" initiative is playing out for Microsoft. Now matter how you slice it (availability, confidentiality, integrity), the domain name system is one component of any networked security strategy.

    --
    http://tinyurl.com/4ny52
  36. licencing issues with djbdns by ozzy_cow · · Score: 2, Informative

    The reason bind, not djbdns is includedi with every distro is because djbdns can not be distributed in modified/binary form . I don't really agree with it, but hey, thats how Dan J. Bernstein wants it.

    Anyway, compiling djbdns is mad easy (unlike qmail) check this out

    I use djbdns anywhere I need DNS server.

    1. Re:licencing issues with djbdns by Monkey · · Score: 1

      License issues aside, if I remember correctly, when you compile qmail, it actually compiles the UIDs of the qmail accounts into the binaries. This would make distributing binaries useless since the UIDs could be different on every system. Additionally, djb's refusal to follow modern day UNIX file system layout conventions didn't go over well with the big UNIX vendors.

      My biggest bitch with qmail is that they don't release the main source distro with the glibc errno patches in it. I have to patch the shit out of all the qmail packages just to get it to compile on a modern linux box.

    2. Re:licencing issues with djbdns by ozzy_cow · · Score: 1

      you are correct about qmail, but that's not the case with tinydns. its mad easy to compile, install and configure. how i see it, only problem in it's wide spread use is the licence.

  37. By that argument by mrhandstand · · Score: 2, Insightful
    Windows is the most popular desktop environment!

    Here at /. we all know how THAT article would go over!

    Seriously, I have nothing against BIND. But you should always that there are liars, damn liars, and statictians.

    --
    Always value the individual over the system. --Bruce Lee "I don't need a Sig - I have a custom 191" - me
    1. Re:By that argument by Anonymous Coward · · Score: 0

      But Windows is the most popular desktop environment. Or are you forgetting the definition of popular? Despite what all us /. zealots may think (many of which are using Windows anyway, and apparently just like to whinge at Microsoft to be "cool"), Windows is by far the most popular environment for your average PC user, who are themselves by far the largest segment of the computing business (by volume, if not by value).

  38. We Tried BIND, but.... by buzzoff · · Score: 4, Interesting

    BIND just wouldn't work. It worked at first, until I dumped a bunch of hosts into my zone (only a couple thousand, which isn't much in the grand scheme of things). After it stopped working I happened to get in touch with some of the developers. They just kept telling me to upgrade to the next release.

    Some of the problems? Sometimes the CPU would peg at 100% like the program was in a loop, the server would quit resolving after about ten minutes, and the server wouldn't replicate.

    My zone files were standard and by the book. The particular developer I was talking to the most (generally) tried to blame the A records I had added (without knowing which ones). I quadruple-checked the entries, all of which followed the RFC. I reinstalled the program, tried it on totally different servers, etc. The problem persisted.

    After screwing around with BIND for two weeks I gave up. I switched over to MSDNS. Guess what? The EXACT same file that wouldn't work with BIND worked with MSDNS. This was BIND 9.2. We've been running MSDNS for a few years now with hardly any issues. We ran into some cache pollution once, but once I checked the stupid box to prevent it the problem went away.

    Its a pain having to mess with the registry for simple tasks, but I guess its worth it for a working product. We're building everything programatically just like we were for BIND. Microsoft did good when it decided to use flat zone files. If only they would make everything so simple...

    --
    "Never tell me the odds"
    1. Re:We Tried BIND, but.... by Anonymous Coward · · Score: 0

      *sigh*

    2. Re:We Tried BIND, but.... by Anonymous Coward · · Score: 2, Informative

      > This was BIND 9.2

      That was probably the problem! BIND 9.x is much(!) worse than BIND 8.x at reading config files. We converted 19,000 domains over to 9.x last summer, and it took us about 8 man-months to do it. We even bought a support contract from the ISC. Their (useless) reply was always to just attempt to start BIND then try to decode the error logged, rinse and repeat. That's unbelievably tedious when you have over 200,000 lines worth of config files, and the error messages usually are very vague or just plain wrong. They worked just fine with BIND 8.x! Some of the files hadn't needed changing since last 1995! This was an upgrade that should have taken an afternoon, but because of the regression in the parser in BIND 9.x, it took about 320 times that long. A big FU to the ISC for so horribly messing-up the config file parsing in BIND 9.x!

    3. Re:We Tried BIND, but.... by Anonymous Coward · · Score: 0

      Truth forged from pain is so compelling...
      I love it. Thanks
      And I love that their high cost support sucked, and it was probably more "assholish" than people blame djb for being.

    4. Re:We Tried BIND, but.... by huskymo · · Score: 1

      I beg to differ. BIND 9 isn't worse at reading zone data files, it's just much stricter. If it wouldn't read your zone data files, that's likely because you were taking advantage of BIND 8's sloppy zone data file parsing to do something illegal like attaching multiple CNAME records to the same owner name.

  39. They use BIND for same reason others use Windows by Secrity · · Score: 2, Insightful

    I believe that most people use BIND because it is already used by most people. For the most part, people are afraid of being different. There are some things the people just use blindly even though there may be superior alternatives available; such as BIND, MS Windows, MS Office, Sendmail.

  40. One word: "milter" by Anonymous Coward · · Score: 1, Informative

    milter, that is.

  41. DJB is lazy by fimbulvetr · · Score: 0, Flamebait

    DJB is lazy. The fact that you need environment variables to run the dns server.

    WTF? Environment Variables? Is he smoking crack?
    Ever heard of a conf file?

    And what about the fact that I need to add a new folder to / to run any of his software? Ever heard of /usr/local? perhaps /usr? Maybe even /opt? But his own special partition? Are you nuts?

    This doesn't count the fact of people finding *LEGIT* security flaws in his other software *ahem qmail*, and he refuses to admit it. Even M$ admits to most security flaws brought to their attention.

    1. Re:DJB is lazy by Russ+Nelson · · Score: 1

      Why parse a conf file when Unix gives you configuration for free?

      A subdirectory (not folder) in root does not create a special partition. Where did you get your clue? At Wal*Mart?

      There are no security flaws in qmail. Prove it! Break into qmail.org and post the root password here.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:DJB is lazy by fimbulvetr · · Score: 1

      Well that's a good question. Let's look.
      Well, postfix, sendmail, bind, pam, *nix, cron, csh, cups, dhcpc, clamav, fstab, make, init, lynx, login, man, mplayer, mysql, postgres, apache, tomcat, oracle, sshd, all use a conf file. Imagine if they all used env. variables. It's called normalizing. Welcome to the real world my friend.

      You're right, it doesn't make a seperate partition, not a DISK partion. You some how imagined I meant a disk partition when in reality, I never said DISK parition, for those who don't pay attention a partition is:

      # Something that divides or separates, as a wall dividing one room or cubicle from another.

      From: dictionary.com

      Seems as if a new folder (/service) fits under the definition of partition just fine.
      Sorry buddy, even though a common dictionary is available at walmart, I didn't get the definition there.

      You're under the impression that a "security flaw" implies getting a root password. Methinks you have a distorted perception of reality. A security flaw encompasses just about any type of DOS, as well as getting access as an (un)privileged user.

      Here:

      http://www.insecure.org/sploits/qmail.DOS.rcpt.h tm l
      Can't read that one? Never been to a *nix site?

      Here's a plain text one:

      http://www.hoobie.clara.net/security/exploits/qm ai l_dos.c

      Prepare your response next time, and you might be able to argue with a script kiddie.

    3. Re:DJB is lazy by Anonymous Coward · · Score: 0

      Guess you never heard of unix process accounting.

    4. Re:DJB is lazy by Anonymous Coward · · Score: 0

      It's "password".

    5. Re:DJB is lazy by Russ+Nelson · · Score: 1

      Gee, and all the programs you cite are less secure than djbdns. Cause and effect?

      You are pretty clue-free. Nobody but nobody thinks a directory in the root of a filesystem creates a partition. Well, okay, you *are* that nobody. Let me say instead that nobody *else* calls it a partition. Nobody with a clue that is, anyway.

      If you offer service to all comers (which an SMTP server does), then you are subject to DOS attacks. There is nothing you can do to stop somebody from opening connections from enough machines to suck up all your connections. If you run qmail-smtpd with proper resource limits, it will fail to consume too much memory. Duh.

      --
      Don't piss off The Angry Economist
    6. Re:DJB is lazy by fimbulvetr · · Score: 1

      Alright, you had no comeback for the nobody has a clue partition issue.

      No, not any SMTP server is subject to a DOS attack.
      SMTP servers can be susceptible to a DDOS attack, however. SMTP servers like postfix can tar pit incoming connections, as well as lower connections on a per-ip bases. It is also smart enough to sanity-check data.

      I *never* said those programs were more or less secure than qmail, that would be blasphemy. I can't see anymore reason to discuss this with you, clearly you're now just making shit up.

    7. Re:DJB is lazy by qtp · · Score: 1

      This doesn't count the fact of people finding *LEGIT* security flaws in his other software *ahem qmail*, and he refuses to admit it.

      Got a link?

      I've been searching all night to find this "security flaw" that's been mentioned in several posts by a few posters here on /.

      All I've found is a method to crash an smtp session, but qmail keeps running and the remote gets disconnected (haven't tried it yet myself), and none of the reporting posts claimed or implied that the flaw in any way makes qmail any less secure.

      The guy may rub a few people the wrong way, but he's one of the top 1% of programmers. His implementations might be unusual, but they work, are reliable and secure, and you can freely use and modify them (by patching). What else can you ask for?

      --
      Read, L
    8. Re:DJB is lazy by Russ+Nelson · · Score: 1

      Uhhhhh, I'm talking facts, and you're accusing me of being religious. Whatever!

      --
      Don't piss off The Angry Economist
    9. Re:DJB is lazy by fimbulvetr · · Score: 1

      Talking facts? Really?

      There are no security flaws in qmail.

      That was an outright lie. I proved it.

      Nobody but nobody thinks a directory in the root of a filesystem...(exception..blah blah blah)

      Wrong. You can't prove this. This is NOT FACT BASED.

      If you offer service to all comers(which an SMTP server does), then you are subject to DOS attacks

      Wrong. I've introduced an MTA to you that is smarter than that. It's called tarpitting. ...you're accusing me of being religious...

      Wrong. At not place in any of my posts did I ever imply that you were religious. I believe you are, but nowhere did I *accuse* you of it.

      Listen man, I don't know how you got to be the webmaster behind qmail, but you clearly have no idea what you are doing here.

    10. Re:DJB is lazy by Russ+Nelson · · Score: 1

      I see that you cannot be convinced by facts. That is fine, but I think most people will say that you lost this argument.
      -russ

      --
      Don't piss off The Angry Economist
  42. BIND is ***MORE*** frustrating than SQL??? by swordgeek · · Score: 2, Insightful

    Seriously, MyDNS requires an SQL database. This is NOT a way of making things easier!

    I've never understood what problem people have with BIND. It's as simple as it could possibly be. Everything makes clear sense. The config files are plaintext. It's backwards compatible almost to eternity. I use it because it's the best solution, not the only one.

    --

    "People who do stupid things with hazardous materials often die." -- Jim Davidson on alt.folklore.urban
    1. Re:BIND is ***MORE*** frustrating than SQL??? by Russ+Nelson · · Score: 1

      Parse an arbitrary BIND zone file.
      -russ

      --
      Don't piss off The Angry Economist
    2. Re:BIND is ***MORE*** frustrating than SQL??? by Anonymous Coward · · Score: 0

      Okay. I'm waiting.

    3. Re:BIND is ***MORE*** frustrating than SQL??? by demon · · Score: 2, Informative

      Yeah, except for the fact that (a) it's then incredibly difficult to allow customers to manage DNS on their own - something that I've come to really appreciate (we have several customers who host their DNS with us, but want to manage their zone contents themselves), and (b) the way that software like cPanel does it is not a good solution (we have one customer who handles his own DNS on a box running cPanel, and I'm regularly having to fix that for him). Also, (c) the half-way solutions of making a database, and using a bunch of scripts to regenerate the zone files periodically is always a mess - if the scripts should break, updates don't get applied, but if they do, hand-editing the zone files isn't a viable option.

      I use PowerDNS for our DNS servers at work, and I and our customers are very pleased with it. We have a frontend (that I wrote) that integrates with our billing system, so users can log in and make changes to their domains, and have them take effect immediately. They never have to worry about trailing dots, domain serial numbers, or getting the SOA format right, not to mention multiple CNAMEs assigned to a single name (which will cause BIND to throw the zone out) or other mistakes like that - our frontend prevents errors like that. It's made DNS provisioning and management so much easier - provisioning is error-free now. Why would anyone want to use BIND? Seriously?

      --

      Sam: "That was needlessly cryptic."
      Max: "I'd be peeing my pants if I wore any!"
  43. Milter. by numbski · · Score: 1

    I need miltering. Specifically spamass-milter. A few others, but primarily that.

    --

    Karma: Chameleon (mostly due to the fact that you come and go).

    1. Re:Milter. by bolthole · · Score: 1

      if spamassassin is your primary concern, then switch to postfix. it has spamassassin integration now, as far as I hear.

  44. Re:The reason DjbDNS hasn't been updated in foreve by Jepler · · Score: 1
    When Bind can take 10,000 requests per second on a dual Xeon box (used for MAPS) and not melt into a smoky plastic dog treat, let me know.

    10k requests per second doesn't sound like that much.

    Just for fun, I wrote a program that calls Python's socket.gethostbyname() 10,000 times, and ran it against a very old (AMD K6, 350MHz, single processor, 384 megs RAM) machine on the local network. The runtime was 13 seconds, and named got about 90% CPU usage during that time.

    If your modern dual Xeon box isn't 13 times faster than this years-old box, I kinda feel like you must have gotten ripped off. Y'know, Moore's Law and all.
  45. Some other reasons by Anonymous Coward · · Score: 2, Insightful

    "Why is it so hard for alternate DNS servers to gain favor ?"

    Can be rewritten as:

    "Why people don't switch to djdns (which install in stupid places, is mostly unmaintained, is written by an offensive asshole, and that you cannot fork/modify) ?"

    or

    "Why people don't switch to MyDNS (that just reached version 0.11, indicating that it is really stable) ?"

    Jezus. What are people thinking ? He versions his software as 0.11 and then complains publically on /. that people don't want to use it for the most core function of the Internet.

    1. Re:Some other reasons by TheLink · · Score: 1

      "Why people don't switch to djdns (which install in stupid places, is mostly unmaintained, is written by an offensive asshole, and that you cannot fork/modify) ?"

      Unmaintained? It ain't broke, so there's no need to fix it every year, unlike plenty of other software.

      Sure, there are plenty of people who find DJB offensive. But you'd think that because of that there'd be plenty of people hoping to rub his face in the dirt by finding security holes in his software. So far I don't even see anybody finding security bugs in djbdns. Please do point them out. He has a USD500 guarantee on his software. While the awarding of the USD500 bucks could be disputed, you'd be pretty famous in the IT security field if you do find a valid one.

      In contrast finding a security bug in ISC's software is just going to give you like a week or two of fame.

      Can't fork/modify? I'm not going to bother figuring out what copyright laws apply in your country wherever it is.

      --
    2. Re:Some other reasons by timeOday · · Score: 1
      OK, let's ask a different question then, why isn't there a good DNS server available?

      It seems like such a stupid-simple service, yet somehow Bind manages to make it hard. "Now type in the same information.... backwards!" Huh!?

      For domains with simple needs, it should be possible to get by with a config file that looks very much like /etc/hosts. Then add option configuration directives on top of that for the fancy stuff, e.g. if somebody thinks their changes are propagating too slowly, they can find out about TTL.

    3. Re:Some other reasons by GoneGaryT · · Score: 1
      You are djb!

      I claim my $5.

  46. bernstein by Anonymous Coward · · Score: 1, Interesting

    the guy who wrote this is a cs prof at my university. He's a nut. They actually put him on probation after he failed most of his undergrad classes. The head of the CS dept attempted to take the final exam for a *freshman* class bernstein was teaching and determined he couldn't do it.

    Bernstein seems to be a smart guy, but he sure is crazy.

    1. Re:bernstein by Lorphos · · Score: 2, Informative

      He's also terribly arrogant :-( He often has his reasons for rejecting proposals, but not always and he's very bad on communications.

    2. Re:bernstein by Anonymous Coward · · Score: 0

      its just funny he was failing UIC freshmen with no programming experience for not being able to take a final exam someone with a PhD in CS would have a hard time with.

      then he didn't understand why this was a problem

    3. Re:bernstein by TheLink · · Score: 1

      He has his reasons, and extremely often he is right. (I think he's wrong about that proposal about the next gen email method tho, not that it matters).

      Yeah he is arrogant and often obnoxious but I actually regard this as a feature in this case.

      Why? He must have pissed off thousands of people by now (many of them fairly smart too). The way these people can get back at him where it hurts him is to find a security flaw in his program and rub his nose in it.

      The fact that I haven't seen any qmail and djbdns exploits (ala remote root or remote user ) despite all that is gives me more confidence in the security of his software. :)

      --
    4. Re:bernstein by Anonymous Coward · · Score: 0
      I've seen you make this argument twice now, and I still have three pages of comments to look through. Why do you assume that if someone doesn't like someone that they'll waste their time hunting through software they have no intention of using anyway just to try to find an exploit? That sounds awfully obsessive-compulsive, and paranoid. I believe most people would ignore the software than become an obsessive nut. That is what stalkers do.

      Besides, do you think anyone outside of a subset of a CS community would know or even care if this fella has his nose rubbed in it?

    5. Re:bernstein by TheLink · · Score: 1

      "software they have no intention of using anyway "

      Uh in my experience the "users" aren't the ones who try to find exploits. Joe average is unlikely to ever create an exploit for anything unless it involves beer.

      I'm talking about a different group of people here. Just look at the various sites dealing with security vulns and exploits. I've seen at least one or two exploit writers who insult Theo[1] of OpenBSD whenever they get a chance to release an exploit. Which is not that often.

      Who would care? The IT security community would care. A number of large sites use qmail. Yahoo used to use it - now it seems to use something similar- maybe modified qmail.

      [1] Someone should arrange another Theo vs DJB when things get boring ;).

      --
  47. External DB by geohump · · Score: 3, Interesting

    One small reason your DNS server (MyDNS) isn't catching on is that it requires an external DB server process to be set up and running on the system.

    I took a look at your system with the intent to try it out but I stopped as soon as I saw that requirement.

    True, Its not that huge an extra requirement, but it is an extra step and an extra external dependency.

    Adding an internal db (like dbm) to your system so that its self contained would increase the likelyhood of adoption for MyDNS.

    Having to run a fairly costly, (In terms of system resources), 3rd party DBMS system in order to have an active DNS server seems a little upside down to me.

    1. Re:External DB by Nohea · · Score: 2, Interesting

      I use BIND 9. I have a homebrewed DNS SQL db w/all the zone info, and run a perl script to export and generate all the bind zone files.

      It is sometimes convenient to be able to do updates using SQL. However, there is no dependency on the DB server for serving DNS - a very mission-critical service.

      1. if the DB server dies, DNS will hum along normally.

      2. If i get hit by a truck, any unix sysadmin can ignore the SQL DB and hand-edit the zone files.

    2. Re:External DB by ruhk · · Score: 1

      I'd say go one step further. Use a DB interface layer that groks small, internal stuff like DBM etc., as well as MySQL, PostgreSQL, MS-SQL, etc.

      That way the administrator has the flexibility to work his DNS the way he wants.

      --



      404 Error: .sig not found.
  48. tinydns/djbdns is non UNIX by GodWasAnAlien · · Score: 1

    djbdns has not been accepted, because it's too non-standard. The main thing is the folders. He creates and uses a folders called /service, /command and /doc, instead of following any UNIX filesystem standard. I guess he is suggesting that we abandon /usr, /bin, /lib, and just throw everything at the root level.

    1. Re:tinydns/djbdns is non UNIX by Anonymous Coward · · Score: 0

      Funny, You gave DJB root access on your machine and he setup djbdns? How much did he charge you to do this?

    2. Re:tinydns/djbdns is non UNIX by Anonymous Coward · · Score: 0

      I won't tell. But I'm planning on getting that back and more by exposing a security flaw.
      ha.

  49. Re:The reason DjbDNS hasn't been updated in foreve by Anonymous Coward · · Score: 0

    Not 10K times, 10K at the same time. 10K connections in 1 second. You do know what per second means don't you?

  50. DNS Server by Anonymous Coward · · Score: 0

    ... and as the article author looks over the raw data, he notices one lone "BoredDNS" installation...

  51. WARNING! Parent is pedantic asshat! by Anonymous Coward · · Score: 0

    He said "on a related note" and then talked about neatness, which your post mentioned as well.

    Don't be a pedantic asshat about on-topic posting.

  52. Re:The reason DjbDNS hasn't been updated in foreve by SuiteSisterMary · · Score: 1

    Did your test script look up the same hostname 10,000 times? Did it look up different hostnames from 350 different domains? Or any different domains?

    --
    Vintage computer games and RPG books available. Email me if you're interested.
  53. hi Don.. quick notes. by joeldg · · Score: 1

    This is Joel (at IC)..
    I personally feel that BIND/Sendmail both have actually weathered quite well and made it through a lot of checking over the years. All the bugs/sploits etc have kind of made both of those packages like the equivalent of a "software cactus" and people feel secure in knowing they have "weathered the storm".

    DJB's software is great (i.e. qmail and me go way back, when is yours, IRIS, going to go opensource eh? IRIS could give sendmail a run for it's money.) but he seems to, on purpose, want to make it hard to modify and use (i.e. use for distro's) so he is slowly being shut out. Not to mention the fact that he is not bothering to update it or work on it.

    If a significant exploit in BIND came out, or a string of significant exploits came out you would see a shift I think. (i.e. Software Darwin'ism) but this has not happened in a while.

    In addition, if something new were to be added to DNS, a new way to add things in DNS that for some reason BIND could not support and people wanted to use it, then it would also go the way of the dodo, but time will tell.

    I would be interesting to see a timeline survey with important markings of significant exploits to watch the usage change.

    Anyway.. cheers.
    -joeldg

  54. Better survey on the entire .de zone by Peter Koch by Raindeer · · Score: 1

    At the last ripe meeting Peter Koch gave a presentation on what I think was a methodologically better survey as the one presented here. The survey is at: http://www.ripe.net/ripe/meetings/ripe-48/presenta tions/ripe48-dns-survey.pdf

  55. Re:De Facto (IT Majors) by Octorian · · Score: 1

    Yeah, this is a group I find rather interesting. Not that all of them are like this, but rather that most of them are.

    I tend to see most IT majors, and even ones I am friendly with, as those who want to work in the areas of systems administration and networking. However, they also come across as the types who will be in the perpetual "wanting to learn" mindset, and rarely leaping above that to the "now I know the fundamentals, so let me expand my knowledge" phase.

    At my old college, RPI (Troy, NY), I found myself in a situation where I knew a lot of Computer Science majors who were quite knowledgable in the fields of networking and systems administration, whether or not they planned to persue a career along those paths. I rarely saw any IT majors, save the rare exception, involved in the ACM or any of the tech groups I was in. (our IT program had a variety of "concentrations," with some closer to CompSci or CompEng than typical of IT, though very few students chose those concentrations)

    Now I'm living around a different school, UCF (Orlando, FL), and see a radically different situation. The CompSci students have absolutely no interest or knowledge whatsoever in networking or sysadmin stuff (beyond the odd high-level vague course), and the IT students do, on paper. I am friends with more IT students than CS students, however. But what I do notice, is that while I was a CompSci major myself, I know a lot more about SysAdmin and Networking topics than any of the IT or CS majors around here. (Thankfully enough are interested that I have given presentations on subjects, though it makes it harder to find people to involve in technical projects.)

  56. I've got no problem with BIND by butane_bob2003 · · Score: 1

    Except for it's ugly, cryptic configuration. It's so ugly and cryptic that bindconf (GUI config tool) creates it's own config files and overwrite's BIND's files, instead of trying to locate and parse the main config and zone files. This is a big problem if you make changes to BIND's files using vi (or whatever you prefer). Next time you make a change with the GUI your earlier changes get blown away. Hey bindconf folks: bad idea!

    --


    TallGreen CMS hosting
  57. Re:WARNING! Parent is pedantic asshat! by kfg · · Score: 0, Flamebait

    My, we're a spunky little bag of pubescent testosterone today. . .

    . . .and then talked about neatness, which your post mentioned as well.

    . . .who needs to work on his reading compreshension.

    KFG

  58. MOD PARENT UP by kermyt · · Score: 0, Redundant

    no mod points today.

  59. Re:MyDNS/MySQL by ScytheBlade1 · · Score: 2, Insightful

    Random question: am I the only one who loves MySQL to death, but thinks that it's also horribly overused for EVERYTHING?

    I mean....yes, it's incredibly fast. Scalable. Low overhead. But when everything from e-mail to DNS depends on MySQL....it gets a little sickening :P

    You don't need a datbase server for everything, no matter how it is that you can say "I run my DNS servers off of a MySQL database." It's still way overused.

  60. I USED to use djbdns... by D'Arque+Bishop · · Score: 4, Interesting

    Like the subject says, I USED to use djbdns for my home DNS server. After a while, when I upgraded the OS on said home DNS server, I got rid of djbdns and moved to BIND. Why, you may ask?

    1) I didn't like the fact that I had to use two separate IP addresses for caching and domain hosting. Maybe there was a workaround for it, but at the time I didn't know what it was and it frustrated me to high heaven that I needed two IP addresses on a box that I would have liked to have only used one.

    2) The log files didn't print out timestamps in any kind of human-readable format. If I want to see what my system's doing, I don't have time to run the timestamps through some kind of translator.

    3) Due to a directory existing where axfrdns didn't expect one in the log directory (and it was a name that it didn't even use), axfrdns did not work at all. I didn't find that out until a power issue brought the DNS server down and the secondary servers didn't have the correct DNS information. Once I removed the directory, axfrdns started working again.

    4) Believe it or not, I find BIND zone files to be a bit more readable than tinydns's zone files. It also helps when I'm not forced to name my domain name servers a.something-or-other in the zone file. (Why add a CNAME or A for the one you want to use in the first place?)

    5) daemontools.... ugh. Let's not even go there.

    Go ahead and mark me as flamebait or what you will. If djbdns works for you, great. But for me, I found djbdns to be much more frustrating than BIND, and since I've migrated over to BIND I haven't had a bit of problem.

    Just my $.02...

    1. Re:I USED to use djbdns... by Anonymous Coward · · Score: 0

      2) The log files didn't print out timestamps in any kind of human-readable format. If I want to see what my system's doing, I don't have time to run the timestamps through some kind of translator.

      they are in tai64 so that it is easy to read and parse for the computer.

      Look up tai64n and do cat logfile | tai64n

    2. Re:I USED to use djbdns... by peyote · · Score: 2

      Not flamebait, just ill-informed.

      1) djbdns uses separate IP addresses for caching and content-serving for security. Google on BIND and cache poisoning.

      2) The timestamps are in machine-readable form for good reason--they are easier to parse in, e.g., a statistics package. If you want to see what your system "is doing" right now, why do you need a human-readable timestamp? If you need to see what your system "is doing" over time, what better way than a statistics package? You "don't have time" to pipe "tail -f /var/log/dnscache/current" through tai64nlocal to get a human-readable timestamp... yet you have time to post silly arguments to /.?

      Besides, if you were all that hot and bothered about it, why not just switch from multilog (the logging daemon, which is NOT a part of djbdns) to splogger and send your log messages to syslog (or into oblivion, same difference sometimes)?

      3) I've never had this problem. Of course, if everyone else used djbdns instead of the Buggy Internet Name Daemon, axfrdns would be obsolete. rsync+ssh is the way to go. ;-) But honestly, I find your comment to be unmoving: "I did something wrong, and axfrdns broke. Therefore, axfrdns sucks." Whatever.

      4a) Of course BIND's zone files are more readable. Like the timestamps in the log files, the zone files are meant to be machine-readable to encourage web or script frontends.

      4b) You are NOT forced to name your authoritative servers anything. You obviously did not read the Fine Manual. (Hint: it's right here.)

      5) What's wrong with daemontools? Unlike inetd, I've NEVER had exhaustion attacks with programs managed by daemontools. I find it all quite elegant.

      I will NEVER go back to the monstrosity that is BIND. djbdns is so much more flexible, intelligent in its design, and it just RUNS. We're approaching 20k DNS records in our database... may not be much, but djbdns handles it all without blinking.

  61. tinydns/djbdns is ultimate UNIX by Nonesuch · · Score: 1
    djbdns has not been accepted, because it's too non-standard. The main thing is the folders.
    Actually, Bernstein's use of folders and files for configuration and control goes back to the earliest roots of Unix, where the vision was that the single root hierarchical filesystem concept would extend to every object in the system (See the "Plan 9" operating system for an example of where this can lead).

    He creates and uses a folders called /service, /command and /doc, instead of following any UNIX filesystem standard. I guess he is suggesting that we abandon /usr, /bin, /lib, and just throw everything at the root level.
    By default, djbdns installs binaries in /usr/local/bin and the actual service configurations can be created anywhere you choose. Actually, you are thinking of DJB's daemontools. While they work well together, daemontools is not absolutely required to run djbdns.

    When you

  62. [Obvious] by changa · · Score: 0, Troll


    If this was on fark would we be using the [Obvious] tag?

  63. Switched from BIND to MSDNS? by Nonesuch · · Score: 2, Interesting
    We Tried BIND, but.... (Score:2, Interesting) by buzzoff (744687) on Friday June 04, @08:46AM (#9334123) BIND just wouldn't work. It worked at first, until I dumped a bunch of hosts into my zone (only a couple thousand, which isn't much in the grand scheme of things). After it stopped working I happened to get in touch with some of the developers. They just kept telling me to upgrade to the next release.
    I've never seen a problem such as you describe in running BIND under UNIX.

    After screwing around with BIND for two weeks I gave up. I switched over to MSDNS. Guess what? The EXACT same file that wouldn't work with BIND worked with MSDNS. This was BIND 9.2. We've been running MSDNS for a few years now with hardly any issues. We ran into some cache pollution once, but once I checked the stupid box to prevent it the problem went away.
    Based on this, I'm guessing you were running BIND under Win32, then switched to MSDNS under the same Win32 system?

    Personally, when I first encounter massive performance problems on a dedicated production-critical service, I would have contacted the developers and asked them what platform they recommend for running a dedicated server, and switched the base OS to the platform they best support.

    Based on the above philosophy, I've ended up actually running more MS-Windows servers in the data center, as many speciality software vendors preferentially support Windows 2000 over UNIX-like systems. And of course any time you run two different applications from two different vendors on the same Windows box, antime a problem is encountered with Vendor A's application, as soon as the support engineer discovers that another package is running on the same box, Vendor B's application immediately becomes the root cause of the problem :)

    1. Re:Switched from BIND to MSDNS? by buzzoff · · Score: 1

      Yes, I was running BIND under Windows 2000 Server. My philosophy for choosing software is OS first, app second. I believe what you're describing is app first, OS second. In my thinking, if I can find something that meets our needs that runs on Windows I will choose it first for the sake of consistency and compatibility. Every shop I've seen that is split fairly evenly between Windows and Linux is trying to consolidate things due to high administrative costs. The software we run on Linux around here tends to be very specialized, which is where Linux shines IMHO. Security apps such as event loggers, sniffers, SNMP, etc. tend to fit well into this category. Day to day apps, such as DNS, are handled pretty well by our Windows servers. Basically it boils down to a lazy or over-worked developer. He admitted that he didn't have time to look at the issue without payment, and he even said the problem could be in the software but it would be a difficult fix. I gathered he didn't WANT to fix the bug(s). I originally installed MSDNS with the full expectation it would fail just like BIND. When it didn't, I started to talking with other Windows admins who were using MSDNS and deduced that it would meet our needs.

      --
      "Never tell me the odds"
  64. dude, tinydns syntax is WAY better by honold · · Score: 1

    have you looked at a zone file lately, or dealt with scripting/automation related to them? .domain.com::ns1.domain.com
    @domain.com::mail.dom ain.com:10
    =domain.com:1.2.3.4
    =www.domain.com:1 .2.3.4

    . for soa, @ for mail, = for alias...how much more intuitive or simple can it get?

    1. Re:dude, tinydns syntax is WAY better by NoMercy · · Score: 2, Insightful

      by actually using the words instead of symbols? Also you neglect the ::'s and :'s which is probably even more confusing when youve got IPv6 addresses thown in too :/

  65. ease of use by mr.dreadful · · Score: 1

    With regards to two threads that seem to running here: how easy is BIND to use and how easy is sendmail to use. Like most self respecting geeks I learned how to set and manage these services, but ultimately decided I had more important things to do with my time. For BIND I started using Mice and Men's QuickDNS, which (I believe) is built on top of BIND. Very Easy to use and their support rocks. I finally bailed on that and just started using the free DNS service my domain host provides. I just didn't need more then 8 different addresses to resolve (thank you NAT), so why bother? One less machine to run and service to worry about... Similar story with Sendmail... used it forever, but finally switched to CommuniGate Pro, which is way easier to deal with and runs like a champ. I've probably saved myself the cost of the license just in saved time alone, not to mention that now I can delegate some of this work to junior IT memebers.

  66. Re:MyDNS/MySQL by walt-sjc · · Score: 1

    There are other reasons not to want to use your DB for everything. What if it goes down / gets corrupted? What if some wacked query for some other application makes your DNS server unresponsive?

    The best way to use a DB in maintaining zone files is to store the master copy there, but then dump a BIND zone file out for production. Many huge ISP's do this.

  67. NonSequitur? by EvilStein · · Score: 1

    Damn, that is OLD!

    Version 0.9

    Released March 1st, 1999

    And people are STILL running it. heh.

  68. Are you crazy? by Anonymous Coward · · Score: 1, Informative

    Did you RTFA?

    Because there it says:
    70.105% 24,335,752 BIND
    15.571% 5,405,266 TinyDNS

    That must account at least for some exposure...

  69. dnsmasq? by mOdQuArK! · · Score: 1

    I haven't seen any comments on dnsmasq - it seems to be a small, easy-to-configure caching nameserver suitable for use on a home network (or maybe a small business). It also has some hooks for handling DHCP-assigned IP addresses.

    Has anyone had any bad experiences using it?

    1. Re:dnsmasq? by Anonymous Coward · · Score: 0

      I have a friend who recommends it. I would probably use that, but I already have a dnscache+bind setup.

    2. Re:dnsmasq? by tylernt · · Score: 1

      It serves hostnames out of the dhcp.leases file... that rocks! Seems much simpler than DDNS. Thank you mOdQuArK! :)

      --
      DRM 'manages access' in the same way that a prison 'manages freedom'
  70. average #domains served per server by Anonymous Coward · · Score: 0

    Bind: 72
    TinyDNS: 446
    Mickysoft: 21

    I guess if you want to serve more than 21 domains, you have to buy an extra Windoze server to handle the load :-)

  71. Why BIND beats out DJB by Syberghost · · Score: 1

    It follows the RFCs.

  72. DNS Server? by BigForbis · · Score: 1

    Who needs those. Remembereing a boat load of IP addresses is so much more useful.

    --
    Remember, 50% of people are below average...
  73. RE: ADS/BIND Problems. by jaseuk · · Score: 1

    BIND does not work properly with ADS if you have multiple domain controllers on seperate subnets.

    Microsoft DNS will return the domain controller on your subnet as the topmost entry in your AD domain. Bind returns them in round robin order. Needless to say that this causes big problems in larger networks as users end up logging on to in-appropriate servers.

    When I was investigating this problem the BIND answer was that sorting results is a problem for the client resolver and not the dns server.

  74. Re:The reason DjbDNS hasn't been updated in foreve by Lehk228 · · Score: 1

    13 times faster than 350 mhz would be 4.55 Ghz, so no it probably isn't 13 times faster

    --
    Snowden and Manning are heroes.
  75. Re:Feature Complete? by symbolic · · Score: 2, Insightful

    This is a major weakness of Open Source because since software is under constant development and bug fixing and security hole patching is priority, few programs ever become feature complete.

    Hm..I consider most software to be an evolutionary process. You start out with a need, you write the software, and then someone else sees a little bit further out and says, "gee, I like what you've done, but it would be so much more useful if it [insert most wanted feature here]". I can't think of a single piece of software I've used that had everything I wanted. I don't think there will ever by one, either. It's like the bear and the mountain - each new version is another mountain, and once we get to the other side, we're apt to see more things we'd like the software to do for us.

  76. why use bind? (vixie's comment) by Anonymous Coward · · Score: 0

    bind was the first unix dns implementation and its user base has a lot of inertia. ISC supports it, both for free and for fee. it follows RFC's. there's DLZ for folks who need sql-driven zone or config data (and we're working with DLZ's author to integrate it into an upcoming BIND9 release). BIND4 and BIND8 were subject to exploit-of-the-year syndrome but BIND9 (released in Y2K) has been exploit free.

    but the number one reason folks do use, or should use, BIND is that ISC wants to help you use it, including answering questions, accepting contributed code, adding requested features whenever possible, using a BSD-style license, and otherwise working to ensure BIND's relevance.

    if you prefer something else, that's cool. but according to ISC's own survey, most servers on the internet today run BIND, and we at ISC could not possibly be any more pleased about that than we are. making DNS work, and keeping the specifications in the hands of what you now call "the open source community" has been our goal from day 1.

    paul vixie

  77. Why I keep using it... by Mustang+Matt · · Score: 2, Interesting

    I see people bash bind and praise djbdns, but I personally have never had a problem with bind. It was relatively easy to setup and it's relatively easy to maintain and has a decent amount of power to it. Granted, I'm just doing simple tasks of dns for sites and nothing very complicated.

    I'm not oppossed to switching but given that my time is already crunched, I will probably keep using bind so I don't have to spend the time learning how to setup djbdns.

    Now if some huge security hole was discovered that affected me directly and there was an actual need to switch, I would spend the time and do it.

    Until then I'll probably keep using bind since my distro gives me the choice to choose my dns server.

    BTW, this same post could be used for sendmail.

    --
    The man who trades freedom for security does not deserve nor will he ever receive either. - Benjamin Franklin
  78. Re:The reason DjbDNS hasn't been updated in foreve by Anonymous Coward · · Score: 0

    While the poster's test has some other problems (which isn't exactly unexpected for a quickie test; if all you folks are so smart, why don't you post your own tests and results?), this isn't one of them. DNS isn't connection oriented (most of the time); for your standard gethostbyname-type operation, it basically services a bunch of UDP packets. A DNS server will have one 'socket' open to the DNS port, and then dispatch accordingly as it receives datagrams. Having more than one socket bound to the port would be impossible, and having more than one file descriptor map to the same socket is usually less-than-useful because of synchronization overhead (although it can be done, especially with UDP datagrams, since they act like atomic requests).

  79. Re:MyDNS/MySQL by jap · · Score: 1

    Yeah, and then they have to wait hours before that BIND zone has been reparsed and reloaded if updated.

    And powerdns does grok bind zonefiles, btw.

  80. Posadis by delus10n0 · · Score: 1

    I've been running Posadis on a Windows 2000 server for about three months now, and it's been nothing but awesome. Rock solid stable, and easy to config. Took me a while to find the rare gem, though. It's hard to find an open-source/free DNS server for Windows.

    --
    Not All Who Wander Are Lost
  81. When is anything ever this obvious? by blair1q · · Score: 1

    What would you like to do?
    [ ] Install and configure a non-default DNS server?
    [ ] Surf the web for Pr0n now!

    [Back][Next][Finish][Cancel]

  82. Re:MyDNS/MySQL by walt-sjc · · Score: 1

    Yeah, and then they have to wait hours before that BIND zone has been reparsed and reloaded if updated

    That's an implementation design issue, not a technical limitation of the concept.

  83. infoblox by asad · · Score: 1

    that's why you have companies like www.infoblox.com making it easier for people to use bind.

    --
    Vidi, vici, veni. (I saw, I conquered, I came)
  84. people don't care! by Xtifr · · Score: 1

    Not lazy (or not just lazy): more to the point, most people don't care! Most people want the service, but don't care about the fiddly details of how it works. If it comes with the system and works, why should they mess around looking for alternatives? If there's hundreds of books on it, why switch to something else, especially if you don't care?

    At most places I've worked, DNS is a tiny part of what's going on in the organization. A critical part, but a tiny part. Often, there's no particular person assigned to maintain the DNS. Instead, it's simply a (small) part of the duties of the admin or ops team. And since it's a team responsibility, and the team members may change over time, better and easier to stick with something widely known (e.g. bind). Especially since nobody really cares, as long as it works.

    Lots of places I've worked at have had several dedicated email adminstrators, and email is their primary (only) responsibility, so they care! So alternate email systems like qmail and postfix and whatnot are not uncommon. But DNS is just something that most people don't care about as long as it works.

    Me, I use /etc/hosts files, at least at home, where I am in charge, and there's barely a half-dozen machines to worry about. :)

  85. Re:MyDNS/MySQL by WarWizard · · Score: 1

    No. I have apache, proftp, postfix, courier, and mydns all pulling from 4 tables. For apache 1.3.x I found mod_shapvh that lets you pull vhosts from mysql. The rest of them all have native support. I also use libpam-mysql and libnss-mysql for having users owning files when they don't have accounts /etc/passwd. Yes.. its a sick sick MySQL fetish.

  86. Everything else sucks, that's why. by sudog · · Score: 1

    Comaptibility with the majority of name servers is crucial--name one name server software daemon which is entirely compatible with BIND, offers its own set of features and functionality that is superior to BIND, and is open source.

  87. gentoo plays very nice with qmail and djbdns by ElectronSlut · · Score: 1

    The qmail and djbdns ebuilds provided by gentoo automagically download DJB's sources as well as all of the popular patches (including qmailscanner), and then apply the patches and build it all very cleanly for you. No fuss, no muss, no license violations, no FUD.

    Then again, I guess a lot of people are still a little afraid of gentoo (if not quite as much as DJB's scathing condescending wrath).

  88. Why am *I* using BIND? by cduffy · · Score: 2

    Simple: support for views, and licensing that allows redistribution.

    I absolutely, positively require view support, which nobody but BIND that I know of supports. TinyDNS might, but I can't so much as consider it due to the license; we're distributing servers with a fairly custom software environment, and DJB's terms make that a no-no. (This is also why we're using runit rather than daemontools).

    Support views in something that supports pulling info (not just zone info, but definition of what the zones are, what the views are, what the ACLs are, etc a la named.conf) directly from a database and I'll be happy as a clam. 'Till then, I run BIND.

  89. This is simply NOT TRUE by Pan+T.+Hose · · Score: 1

    Personally, I use one called djbdns. It's extremely small and basically bug free! The author actually will pay $50,000 to whoever finds the first exploit in it or something.

    You might want to read the first line of the djbdns security guarantee:

    "I offer $500 to the first person to publicly report a verifiable security hole in the latest version of djbdns."

    $500 is hardly $50,000 but even if it was $50,000, please keep in mind that a hypothetical non-public exploit of tinydns would be worth much more than $50,000 for anyone who would want to use it seriously. Please remember that by compromising DNS server you can effectively control mail and websites, even without compromising the mail and web servers themselves. I have already seen web traffic for compromised domains routed through proxy servers controlled by attackers (or smtp traffic redirected via external relays, for that matter). This might be very powerful and can be quite hard to detect, especially when you provide correct dns info to internal network.

    With all due respect to D. J. Bernstein, even though I do believe that his name server is probably the most secure one in use today, his cracking contest is hardly meaningful. There is an interesting article, The Fallacy of Cracking Contests by Bruce Schneier, published in the December 1998 issue of The Crypto-Gram Newsletter:

    You see them all the time: "Company X offers $1,000,000 to anyone who can break through their firewall/crack their algorithm/make a fraudulent transaction using their protocol/do whatever." These are cracking contests, and they're supposed to show how strong and secure the target of the contests are. The logic goes something like this: We offered a prize to break the target, and no one did. This means that the target is secure.

    It doesn't.

    Contests are a terrible way to demonstrate security. A product/system/protocol/algorithm that has survived a contest unbroken is not obviously more trustworthy than one that has not been the subject of a contest. The best products/systems/protocols/algorithms available today have not been the subjects of any contests, and probably never will be. Contests generally don't produce useful data. There are three basic reasons why this is so.

    1. The contests are generally unfair.

    Cryptanalysis assumes that the attacker knows everything except the secret. He has access to the algorithms and protocols, the source code, everything. He knows the ciphertext and the plaintext. He may even know something about the key.

    And a cryptanalytic result can be anything. It can be a complete break: a result that breaks the security in a reasonable amount of time. It can be a theoretical break: a result that doesn't work "operationally," but still shows that the security isn't as good as advertised. It can be anything in between.

    Most cryptanalysis contests have arbitrary rules. They define what the attacker has to work with, and how a successful break looks. Jaws Technologies provided a ciphertext file and, without explaining how their algorithm worked, offered a prize to anyone who could recover the plaintext. This isn't how real cryptanalysis works; if no one wins the contest, it means nothing.

    Most contests don't disclose the algorithm. And since most cryptanalysts don't have the skills for reverse-engineering (I find it tedious and boring), they never bother analyzing the systems. This is why COMP128, CMEA, ORYX, the Firewire cipher, the DVD cipher, and the Netscape PRNG were all broken within months of their disclosure (despite the fact that some of them have been widely deployed for many years); once the algorithm is revealed, it's easy to see the flaw, but it might take years before someone bothers to reverse-engineer the algorithm and publish it. Contests

    --
    Sincerely,
    Pan Tarhei Hosé, PhD.
    "Homo sum et cogito ergo odi profanum vulgus et libido."
  90. Another reason is by burbilog · · Score: 1

    Another reason is that tinydns, daemontools and other DJB's utilities are very inconsistent. Try to get -h output from these utilities or read man page. Something like man svc! Or may be svc -h? Ooops. This is standard drill for any unix utility. To read documentation for these you have to search the net! AFAIR tcpserver gives short description of its arguments but no man page anyway. And DJB knows how to write man pages, he did it for qmail for example. Fuck.

    1. Re:Another reason is by Anonymous Coward · · Score: 0

      DJB doesn't like man pages, so he doesn't use them. He thinks documentation should be in HTML format instead. The fact that man pages are an established standard apparently doesn't make any impact on him.

    2. Re:Another reason is by burbilog · · Score: 1
      DJB doesn't like man pages, so he doesn't use them. He thinks documentation should be in HTML format instead. The fact that man pages are an established standard apparently doesn't make any impact on him.

      Okay, but let's take cdb. Its "documentation" contains seven lines:
      cdb 0.75, beta.
      20000219
      Copyright 2000
      D. J. Bernstein

      cdb home page: http://cr.yp.to/cdb.html
      Installation instructions: http://cr.yp.to/cdb/install.html

      And what if you've got to use it somewhere without internet connectivity? :(

  91. It's more than laziness by Merk · · Score: 1

    When something is much more popular than its alternatives, you get a number of benefits:

    • Lots of information on the 'net from other users of the software, in case you need help
    • Lots of tools to work with the software
    • The most important one, I think: lots of other software expects that standard software

    For example, there are packages to connect BIND with DHCP servers, allowing dynamic DNS for DHCP clients. You're unlikely to find those as easily for another DNS server. The same thing was true for sendmail -- there were tons of programs that expected to be able to use /usr/bin/sendmail. That required people writing other mail programs to stub out this binary.

  92. Re:MyDNS/MySQL by Anonymous Coward · · Score: 0

    @ Parent of yours: you can also use bind zone files, PostGre, LDAP, and _many_ others...

    "There are other reasons not to want to use your DB for everything. What if it goes down / gets corrupted? What if some wacked query for some other application makes your DNS server unresponsive?"

    Ever heard of "backing things up"? Replicating? Fallover? I'm not backing you up.

  93. Say what? by Inoshiro · · Score: 1

    I don't understand how a sample of roughly 24 and 1/3rd million is a "tiny number"

    Perhaps you have a very weird definition of "tiny" that really means big.

    --
    --
    Internet Explorer (n): Another bug -- that is, a feature that can't be turned off -- in Windows.
    1. Re:Say what? by Just+Some+Guy · · Score: 1
      The tiny numbers in question are like:

      71.5 domains/server

      which to me seemed analogous to saying that IIS is better than Apache, because the average IIS server gets 50 hits per day, and the average Apache server only gets 40 (numbers obviously fabricated). At loads that small, any reasonably competent package should be able to hand the task.

      --
      Dewey, what part of this looks like authorities should be involved?
  94. Re:MyDNS/MySQL by Anonymous Coward · · Score: 0


    Random question: am I the only one who loves MySQL to death, but thinks that it's also horribly overused for EVERYTHING?


    No, I think this is precisely the niche for MySQL , as MySQL is not and never will be an SQLDBMS ala Postgresql, Oracle, etc. Those applications don't represent everything that some idiots are trying to push MySQL into.
    If MySQL fanboys would simply be happy with using it for their small, mostly read-only applications (DNS/LDAP/auth/non mission critical message board) database and quit trying to convince me that its an Oracle killer, I would consider that ideal.

    It might as well be good for something. Basically MySQL is like a Berkeley DB with a slightly more general/useful out of the box interface (The limitations of SQL don't really become a big issue for the ideal MySQL applications). And since it is still fast and low overhead with that ready to go interface (relative to BDB), why shouldn't it be used?

  95. Comment removed by account_deleted · · Score: 1

    Comment removed based on user account deletion

  96. re: Yoooo I've got a big slashdot epenis by ZeekWatson · · Score: 1

    You are a liar and calling me a troll doesn't change anything.

    In fact when you get called on your lies you start insulting my mother, my face, and bragging about your massive slashdot epenis regarding your modifier points???

    WTF? You have no credibility.