Reddit Reddit reviews DNS and BIND (5th Edition)

We found 15 Reddit comments about DNS and BIND (5th Edition). Here are the top ones, ranked by their Reddit score.

Computers & Technology
Books
Networking & Cloud Computing
Internet & Telecommunications
DNS and BIND (5th Edition)
Check price on Amazon

15 Reddit comments about DNS and BIND (5th Edition):

u/VA_Network_Nerd · 20 pointsr/ITCareerQuestions

Social Engineering: The Art of Human Hacking
All of your security infrastructure is meaningless if I can call Suzy in Accounting and ask her for her password.


TCP/IP Illustrated, Vol. 1: The Protocols
Yes, I know this book is old. This book is the Mutha-Fecking 1969 Camaro 454SS of networking books.
It simply NEVER goes out of style.


Wireshark for Security Professionals: Using Wireshark and the Metasploit Framework
If you don't have a basic understanding of Wireshark and Packet Analysis, you're useless to me.
You don't have to be a wizard. You don't have to look at the Matrix and see Blondes or Red Heads. But you MUST possess a clue.
I have no specific love for this book. Just pick any good looking Wireshark book writen for an InfoSec audience.

DNS and BIND (5th Edition)
The author "Cricket Liu" is THE DNS guy. He literally wrote the book on DNS.

Designing for Cisco Internetwork Solutions Foundation Learning Guide: (3rd Edition)
The Cisco CCDA track will teach you focus on technical requirements, and aligning network functionality to match those requirements. Data Networking is CRITICAL knowledge to InfoSec professionals. But you might find this an easier starting point than CCNA.


u/solid7 · 9 pointsr/linuxadmin

A lot of what has been suggested is great for learning linux. Realize that "out there" very little is served out of a single box (and if it is you're doin it wrong). Production infrastructure likely looks and acts very very differently from your home linux workstation. Just because you know how to type sudo apt-get install apache2 does not mean you are ready for a full ops position... BUT - if you put in the wrench time and pay your dues, you will get there.

Here are some areas that would be good to build your knoweldgebase up in...

  • First and foremost - you must build the ability to learn how to figure things out and build an intuition of what to inspect should something not be working. This comes from having a working knowledge of many different systems in a large heterogeneous environment. This will come with experience.
  • Learn some of the rapid deployment frameworks - cobbler, puppet, cfengine, etc... No one sits around configuring each and every production machine from scratch.
  • Now that you are familiar with (presumably) the installation and configuration of apache, start thinking about setting up caching/proxy infrastructure. Get a sense for what to use for load balancing v.s. caching v.s. increasing availability (and some combination of the three). Become familiar with things such as nginx, mod_proxy, haproxy, squid, varnish, mongrel, etc...
  • You MUST know how dns works. Crickets bind and dns should be considered required reading. Any lack of understanding of how dns works is simply unacceptable for a proper sysadmin.
  • this book is required reading, period.
  • You must become familiar with centralized authentication mechanisms. Most systems utilize something called PAM. Learn how to configure PAM to reference slapd, AD, etc... Kerberos is our current preferred central authentication mechanism, you need to know how to bounce kerberos tickets around. Get slapd (OpenLDAP) up on its legs.
  • When running a linux kernel, learn how to configure netfilter. Under linux, Netfilter is the thing responsible for routing, nat, and packet filtering. Understand that other kernels do not use netfilter (or commonly use something else). Become familiar with the common kernels firewall, routing, and forwarding system(s). Don't make the mistake of saying "the iptables firewall..." in the interview room! Iptables is not a firewall.
  • Know your basic networking. Internet core protocols should be added to your list of required reading. Understand the differences between a hub, bridge, switch, and router. Learn how to "subnet", which means knowing your binary math! I cannot tell you how many times I have seen a messed up network because someone didn't know how to figure out /27 and keyed in the wrong values from a "subnet calculator". Along with networking do a bunch of reading/research on vlans, trunking and stp. Most people cannot tell you what a L2/3 managed switch is or how it differs from a "dumb" switch or router. Don't be one of those people! Learn how to configure routing protocols such as BGP, RIP and OSPF (also, learn basic computational graph theory). You may not end up doing a whole lot of networking, but it's really good stuff to know.
  • Virtualization is important. You need to know the different forms of virtualization (desktop v.s. os-level v.s. para v.s. hyper virtualization). If you are keen to linux, you need to know how xen and kvm work (this is typically what commercial vps's typically use). Also look at vmware and virtualbox for desktop virt. For os-level virtualization, you need to know how to use LxC and jails.
  • Learn how LVM works! Spend some time familiarizing yourself with LVM2 (linux), vinum (BSD), and ZFS's container framework (Solaris/BSD). Know how and when to use raid. Make sure you understand the implications of the different raid configurations.
  • Learn common backup methodology. Raid is not backup, don't make this mistake.
  • Get used to doing everything on the command line, and always think "what if I had to do this on 20,000 servers?".

    So off the top of my head there's a bunch of things you could study. I think that's quite a bit to get your head around, and a deep understanding of some of these topics will only come from working experience. There may be a LOT of work to do in some of those areas. Getting a fully functional xen (or kvm) based system up and on it's legs is not an easy task for the uninitiated. It is my opinion (and everyone else is free to disagree with me) that all good sysadmins/ops/engineers need to "grow up" in some area of lower level technical position. That can be a jr. admin position, the helldesk, or whatever else... This will give you the "systems" working experience that will let you branch into a full fledged admin/op position. Getting some certs under your belt can help you get in the door, but by all means isn't required. Cert's cost money and (the ones worth getting) take time. Personally, I tend to stray away from places that make a big deal out of certs... but that's just me.

    tl;dr: Learn how to learn. Pick something you don't know how to do and leverage a linux system to accomplish that goal - rinse and repeat.
u/4964d3aae7085d86607b · 5 pointsr/dns

The DNS and BIND book is commonly accepted as the DNS bible. It is mostly about BIND but BIND is the reference DNS implementation and all the concepts apply to most DNS servers.



Of course Wikipedia is also a wealth of knowledge in this area.

u/totallygeek · 4 pointsr/networking

The O'Reilly DNS books are great. I highly recommend the BIND and DNS book.

u/haroldp · 4 pointsr/selfhosted

I've been self-hosting DNS for decades. It's totally doable. Reading the grasshopper book wouldn't be a terrible idea.

I finally got off BIND and would encourage everyone else to do the same. I'm using PowerDNS and NSEdit to manage records.

I use a free service as a slave for my secondary DNS server.

u/codename_john · 3 pointsr/webhosting

This helped me grasp the whole DNS thing: https://www.amazon.com/gp/product/0596100574/

u/gawdnfreeman · 2 pointsr/sysadmin

Three esxi servers, each with more than one NIC, and one separate vcenter server is a great starting point. This allows you to tune DRS, HA, and even fault tolerance. Once you get that down, you'll want to be able to tune VMs properly to run most effectively in a virtual environment.

I enjoyed reading these books, though some are "dated" now, the contents are still very relevant. They won't get you anywhere in particular by themselves, but when you combine them with the self-teaching nature of sysadmins I've previously described, these will generously add to your toolset.

HA and DRS deepdive
Sed & Awk

Mastering Regular Expressions. I use rubular.com often.

Pro Puppet

Anything by Bruce Schneier is usually worth your time.

Though I no longer administer a large number of Windows machines, I am a huge fan of Mark Minasi. The Server 2003 book was super helpful in building and maintaining Windows Domains.

I have an old edition of the DNS and Bind book kicking around somewhere.

Understanding the Linux Kernel has largely been useful to me when doing anything "close to the kernel". Not a good beginner's book.

I've never used an apache book, but I enjoyed the Varnish book. This definitely helped me.

Of course, these books don't cover everything, and those listed are relevant to my interests so your mileage may vary. You'll never go wrong teaching yourself new skills though!

EDIT: I forgot about the latest book I've read. I used tmux for a little over a year before purchasing a book on it, and it has improved my use of the program.

u/selv · 2 pointsr/networking

The book DNS and Bind is a good resource.

u/microseconds · 1 pointr/networking

Cricket Liu's book is pretty much the definitive resource on DNS. It has been for years.

u/IAmGalen · 1 pointr/sysadmin

> DNS is simple

On the surface, mayhaps. Dig a little bit deeper-- DNS and BIND - 642 pages

...and deeper-- Internet Systems Consortium DNS RFC - a collection of all 185 ISC recognized DNS related RFCs

u/admlshake · 1 pointr/PowerShell

Learn Powershell in a month of lunches
and DNS and BIND are two I always recommend to people looking to learn about the windows side of things.

u/81300 · 1 pointr/networking

DNS can be confusing, I'd recommend 'DNS and BIND' by Cricket Liu for some light reading on DNS structure, records, and best practice implementation... I found it to be incredibly informative

https://www.amazon.com/DNS-BIND-5th-Cricket-Liu/dp/0596100574

u/stan_qaz · 1 pointr/pihole

If you want to run Bind to learn it I'd install it on another computer and point your pi-hole to it. That way if you break Bind you can tweak the pi-hole and get your DNS back working.

I run a pair of pi-holes pointed to a copy of Unbound on a different server that is then pointed at OpenDNS. I could use the Unbound as a resolver rather than a forwarder but I like some of the OpenDNS features.

Playing with Unbound a bit before jumping into Bind is a good idea, for Bind I'd suggest this 600 page book:

https://www.amazon.com/DNS-BIND-5th-Cricket-Liu/dp/0596100574

A 500 count bottle of aspirin and some ice for your forehead after you start banging it on your desk.

u/Targren · 1 pointr/homelab

No offense, but if you're that unfamiliar with basics like DNS records, please don't try to run your own mailserver.

I'm not picking on you, honest. It's not a task for the green or the faint of heart, and the best case scenario is you end up in blocklists from now until doomsday before too much damage gets done.

I really can't recommend the ORA animal books strongly enough (I just ordered 2 more while getting these links.) The Cricket has all you need to know about DNS, even if you're not using BIND and Safe, though a few years old, is still an excellent resource, just not, perhaps, an exhaustive one.