Craig Sanders wrote:
On Fri, Apr 20, 2012 at 03:30:58AM +0000, James Harper wrote:
Buffalo WZR-HP-G300NH2AP Wireless N 5 x Gigabit ports 64MB RAM 32MB Flash USB2 port <$100 (according to shopbot)
the WBMR-HP-G300H with ADSL2+ for about $120 looks interesting, but i'd still rather use debian on a netbook.
Please note that at this time (and AFAIK), OpenWRT cannot drive ADSL2+ modem chipsets. Nor can any other open-source Linux. Standard practice is to get a ADSL2+ modem, put it in bridged mode, and have the WRT speak PPPoE to it. There is *ONE* driver in the linux kernel for ADSL2+, and that is the Traverse Solos. It is a two-port PCI (*not* PCIe) card that contains a DSP chip, and a little FPGA running (a svn snapshot of) Traverse's code to translate between the kernel driver and the DSP. I have a traverse solos in a rackmount doing ADSL2+ to different ISPs at work. It's comparatively expensive, and a little quirky, but on the whole I have been pleased with it. (The Traverse Viking one-port card does not take this approach; it is basically the standard "ethernet <--> bridged ADSL2+ modem" components on a single card.)
I'd question whether bind9 would be the right choice to run on a little router like that, maybe better off having something that can just run as a secondary if you can.
i need something capable of acting as a primary authoritative name-server for my domains, not just a cache.
I migrated from bind9 to nsd3 and have been extremely satisfied with it. My only criticism is that "nsdc reload" will cause the daemon to do a fork dance, which upstart can't cope with. (Upstart can only handle double-forking if it happens when the service initially starts.)
nsd would be my next best choice but when i tested it a few years ago, it was still fairly buggy, had more annoying quirks than bind9, and didn't use any less RAM than bind9
I haven't measured performance, but the only quirk I've noticed was the above. Well, and the source of nsdc is fugly.
of these, dnsmasq would probably be my next choice....but i'd have to give up using ISC's dhcpd.
dnsmasq can be used to serve your zones to the world, but it is shit at that job. It is a reasonable caching resolver. You can, of course, run a separate zonefile-serving DNS daemon and a recursive resolver DNS daemon -- just do it on separate hosts, or on separate ifaces of the same host. Of course, the latter would mean you need to HUP or restart the internet-facing zonefile server every time ppp0 bounced...