4 ms·
One of the most common problems we see is DNS misconfiguration. It seems most folks just haven't read the grasshopper book. If you're doing anything on the In
by SwellJoe 17y ago
One of the most common problems we see is DNS misconfiguration. It seems most folks just haven't read the grasshopper book. If you're doing anything on the Internet, you need a basic understanding of DNS.
Once you grasp the fundamentals, most DNS problems become completely transparent, but I've seen people spend weeks trying to solve DNS problems due to lack of understanding.
- there 17y agodns is the cause of many seemingly unrelated problems. some services (like sshd) do reverse dns lookups on connecting ips. a misconfigured dns server somewhere (or improper delegation) along the path can make this initial connection take up to 30 seconds while waiting for dns timeouts. it may look like an extremely slow/busy server, but in reality it's just sitting there doing nothing waiting for a dns reply. tools like dnstracer (http://www.mavetju.org/unix/dnstracer.php http://www.mavetju.org/unix/dnstracer.php) and dig are very useful for diagnosing these issues, but you really need to understand the fundamentals of how dns and delegation work.
- SwellJoe 17y agoYes, I should have been emphatic that part of the problem with not understanding DNS is that if you don't understand it, you might not even realize that your problem is DNS-related. Whenever I hear, "X is slow!", my first response tends to be, "Are you sure it's not DNS instead of X?" About 50% of the time, DNS misconfiguration is at least a component of the problem if not the entirety of it. DNS touches every service on the Internet. If you get it wrong, you break every service, sometimes in subtle ways.
- anApple 17y agoThanks, we just got a fixed ip at work and I was wondering why the initial connection to our servers took longer than usual. Our new ip doesn't have a dns entry.
- Huppie 17y agoI'm not sure which book you are talking about but my guess would be "DNS and Bind". http://oreilly.com/catalog/9780596100575/ http://oreilly.com/catalog/9780596100575/
- SwellJoe 17y agoYes, it's one of the handful of books that built the O'Reilly reputation for stellar books about Open Source software. And it's one I would recommend for everyone building anything on the Internet. Unless you have a full-time system administrator, it should be considered required reading. You probably don't need the whole thing, but I can't think of any better source for the bits you do need to know.
- omouse 17y agoCould you name that book? Do you have know of any other books people should read for sys-adminning?
- sparky 17y agoDNS and Bind (now in its 3rd edition) by Liu, Albitz, and Loukides. It's an O'Reilly book. http://www.amazon.com/DNS-BIND-Cricket-Liu/dp/1565925122 http://www.amazon.com/DNS-BIND-Cricket-Liu/dp/1565925122
- SwellJoe 17y agoThere are very few generally useful books about system administration. DNS and BIND just happens to cover a subject that touches everything we do on the Internet; and covers topics that are often poorly understood, and difficult for most folks to get right through intuition and dumb luck. It doesn't hurt that BIND is damned near universal in usage, so odds are extremely high it's the DNS server you use. The Frisch book is probably a great start for general concepts, though: http://www.amazon.com/Essential-System-Administration-Third-Frisch/dp/0596003439/ref=pd_bxgy_b_img_b http://www.amazon.com/Essential-System-Administration-Third-... It's been ten or more years since I've read it, but it's been updated every few years, and is probably due for a new edition any day now actually. The concepts it covers (backups with standard UNIX tools, for example) are somewhat timeless. It's probably not required reading, though, if you don't actually want to be a system administrator. Most books are just re-hashes of the documentation for a particular service, like Apache or Postfix or Sendmail or whatever, so I don't really have any strong opinions in that direction. When I had problems with Sendmail in the distant past, I found the O'Reilly book useful, but I've never needed third party docs for Postfix, which I've been using for the past eight years or so. Books about specific software are also often quickly dated by new versions of the software. So, that's a long-winded way of saying, "Not really."
- tptacek 17y agoOr, you can skip the O'Reilly book --- and most of the mistake you could make with the simplest BIND setup --- and just use djbdns.
- SwellJoe 17y agoWhile I respect your opinion on most topics, I believe you're way out of your element here. I'm talking about fundamental misunderstandings of the protocol, not stupid typos in the configuration file: Glue records wrong at the registrar, incorrect NS records, non-existent MX records, misunderstanding of propagation/caching/TTL, no PTR, etc. These are the kinds of problems I see all the time. djbdns doesn't make the person doing the configuration understand those things any better than BIND does.
- tptacek 17y agoI'm pretty sure somewhere in my resume there's something relevant to this conversation, but I can't remember. Meanwhile, the reason I brought up djbdns is that it has automatic best-practice behavior for a lot of basic DNS config issues, like matching PTR records, or setting up reasonable TTLs and SOA field values. It's right there in the data format. That's apart from where the dots and semicolons go in the database files. Which yeah is a mistake I managed to make a lot, even after writing a dynamic DNS server for our ISP, and is a problem that djbdns makes go away completely. Sorry. You're going to have to add this to the list of topics I'm insufferable about. ;)
- SwellJoe 17y agoI'm pretty sure somewhere in my resume there's something relevant to this conversation Hey, what a coincidence...me too! http://www.amazon.com/Book-Webmin-Learned-Stop-Worrying/dp/1886411921 http://www.amazon.com/Book-Webmin-Learned-Stop-Worrying/dp/1... I've also been a contributor on an alternative DNS server in the distant past...back when it was fashionable to hate BIND. Meanwhile, the reason I brought up djbdns is that it has automatic best-practice behavior for a lot of basic DNS config issues, like matching PTR records, or setting up reasonable TTLs and SOA field values. It's right there in the data format. BIND also has reasonable defaults, and there are tools (Webmin, for example, just to throw something out there completely and utterly at random) that make it easy to get all of the "reasonable default" things you've mentioned right. You're going to have to add this to the list of topics I'm insufferable about. OK. But you're still wrong.