[ Date Index ] [ Thread Index ] [ <= Previous by date / thread ] [ Next by date / thread => ]
> Rob Beard wrote: >> b) Get a Linksys WRT54GS or similar and run OpenWRT on it (they're >> quiet as mice). c) Get maybe one of those other Linksys devices, >> the NSLU2? and run Debian on it (again, another quiet option I >> would expect). I don't trust Linksys anymore. Back when I was first trying to get a router with a 100Mbps internet port they lied to me (or more accurately, they utterly failed with version management, and so I was looking at a V4 datasheet (the only one available), but a V2 device- if they change hardware specs that someone might care about then they should update the model number on the front- even just append "v4" to it, instead of hiding it underneath). So I ended up buying exactly what I didn't want, and had to sell it and start the search again. Maybe they're a great company, but how can I be sure that their datasheets will be correct now? >> d) Get a Viglen MPC-L and run something on that. I've been wondering about that for a while, but I was hoping that Netgear weren't quite so stupid to make me have to buy a new router just to do internal DNS. Grant Sewell wrote: > Doesn't have to be a WRTable router just to do internal DNS. My > router - shockingly a Speedtouch - does internal DNS and forwards any > un-internally-resolvably DNS requests to my ISP's DNS servers. > Didn't have to update any firmwares or anything. Indeed, the more I > look at some of the routers out there that businesses use, the more I > appreciate just how much my little Speedtouch router does. I have a SpeedTouch at home where my server is. That does local DNS fine (it currently has a bug with MX records, but that's a different story). Up until now I had never thought that any manufacturer would be so scrooge to leave out the local DNS. Simon Robert wrote: > I don't know much about this stuff either, so I maybe barking up the > wrong tree on the wrong planet... I don't really understand why the > option to automatically use the ISP's DNS server isn't OK for you. It does automatically use the ISPs DNS server, by forwarding as any other router (with or without local DNS) does. That's fine. However, I have 2 machines- 'excalibur' and 'centauri'. I want to be able to type 'ssh centauri' from excalibur and it to just work. What my SpeedTouch at home does is lookup in it's own tables for 'centauri.[localdomain]', and if it has it, returns the right IP (which could be static or assigned by the routers DHCP server). If it can't find anything in it's tables (e.g. 'www.google.com.[localdomain]', which bizarrely enough DNS servers do try before forwarding), it will forward the request to my ISPs DNS server. However, this cheap Netgear rubbish just forwards the request straight to the ISP, without checking for local names (because it's not keeping track of any- it just assigns IP address by DHCP and forgets who has what). Currently what I'm doing is statically assigning all my IPs and then adding all the entries to /etc/hosts on each machine. This sucks. Especially since that approach breaks as soon as I boot one into Windows, and it's a right pain when my flatmate wants to access my machine (so he had to add my machines to his hosts and I had to add his and now it will all break if anything changes). -- The Mailing List for the Devon & Cornwall LUG http://mailman.dclug.org.uk/listinfo/list FAQ: http://www.dcglug.org.uk/linux_adm/list-faq.html