venam suggested to use your Raspberry Pi for adblock via DNS.[1] While
  I don't like the idea of blocking ads via DNS (you can't  block  on  a
  URL  basis,  just  host names), I do think that having one central DNS
  server for my machines is a good idea. Why didn't I do this before?

  Next step: Move DHCP to the Pi. Maybe I'll do that this afternoon.


                           ____________________


  Done. Now I've got proper DNS and DHCP on my local network.

  Should have done this a long time ago. Seriously.

  Well, without a Raspberry Pi it's not much fun. I don't want to run  a
  full-blown server.


                           ____________________


  Greatly  simplified my network setup today. Now that I've got a proper
  DHCP server at home, I use DHCP everywhere. Even my printer  now  uses
  DHCP. Together with DNS, this makes everything so easy.

  I  also  discovered  that  dhcpcd[2]  not  only  has a resolvconf hook
  (that's  to  be  expected,  it's  the  same  author),   but   also   a
  wpa_supplicant hook. Thus, on every Arch box, I can do this:

    1   # systemctl enable dhcpcd@$iface

  That's my whole network config now.

  "$iface"   being   "en"  for  wired  connections  and  "wl"  for  wifi
  connections.   Given   a   proper   "wpa_supplicant-wl.conf",   dhcpcd
  automatically starts wpa_supplicant and you're done.

  If you configure all your wifi networks in one config, then it doesn't
  even matter where you are. At  work?  Then  wpa_supplicant  picks  the
  right  network  (depending  on  the  SSID).  At  home? Then it chooses
  another network.

  In fact, you can enable "dhcpcd@wl" just once and then you  just  turn
  on your laptop -- bam, connected. No user action required.

  This  used to be sooooo much more complicated. Apparently, I was doing
  it wrong.

  (Yes, of course, a lot of complexity now lives on my Raspberry Pi. But
  that's  just  one  system. I used to maintain my "/etc/hosts" on every
  node... I always thought: "Nah, I just got two or three nodes, a full-
  blown DNS/DHCP server isn't worth the effort. Boy, I was wrong.)


                           ____________________


  Speaking  of  DHCP. I just stumbled upon an interesting thread[3].  Of
  course, if you're using DHCP, you blindly trust your network. This can
  be fatal.

  ____________________

  1. http://nixers.net/showthread.php?tid=1663

  2. http://roy.marples.name/projects/dhcpcd/

  3. https://bbs.archlinux.org/viewtopic.php?id=198323