I'm glad C.T. found my suggestion to use DNSMasq useful. I missed copying my original reply to the list, but in case some else is interested I documented how I manage my home DNS at http://pedroivan.com. Next in my list is to document how I manage mail to deal with my internal domain and the external domains simultaneously while dealing with multiple users (wife, kids, and myself). -- Pedro On Fri, Jun 22, 2007 at 08:34:29AM -0400, C.T. Paterson wrote: > I'll just reply to all here... > > On 21/06/07, Pedro I. Sanchez <psanchez [ at ] colcan [ dot ] biz> wrote: > >I would suggest you use dnsmasq in you local network > > Tried it - loved it...and it explains why the guy at work who is > helping maintain a DNS (but didn't set it up) had no idea what I was > talking about when I got into zone files, etc. I think he uses > something similar. > > I also hear that it's available for Slack - which is extra good news > for my home network. > > > On 21/06/07, Michael Walma <michael [ at ] walma [ dot ] org> wrote: > > > >You haven't mentioned how big your network is, nor if you are hosting > >your own domain which needs to be reached from the outside. In either > >case, if your network is small, my advise would be to avoid DNS > >altogether for the internal network and rely instead on file based > >address resolution via /etc/hosts on each machine on the local net. > > I was intentionally vague on the details as I'm approaching this with > two outcomes in mind. The real impetus for this is some DNS issues > I'm having at a small company I work at. I'm not in IT - but the IT > guys I've been working with have a predominantly Windows background, > and so I'm trying to provide assistance as an interested party. > > As I was doing so - I also know that I have a LAN at home that I > manage by populating each machine's /etc/hosts file with everyone > else's address - and it's a bit of a pain in the rump. I wondered how > hard it would be to set up a DNS myself. > > Plus, of course - it's a transferable skill... > > In both cases - we're talking about machines that are not accessible > from outside the LAN. > > >You might then only want to configure bind for two purposes: to act as a > >caching nameserver (nice but hardly essential); or to act as the > >authoritative nameserver for your domain, which is also not likely to > >be necessary, since your ISP (or others like twisted4life.com) will do > >it for you. > > My ISP is pretty "no-frills", so I'd be surprised if they would take > this on on my behalf (they have DNS machines, of course, but not > populated with my machines). > > >For most small-scale purposes, you really don't need to get yourself > >into a 'bind'. > > You know, punning is fightin' words where I come from...and here I was > hoping we could resolv this like men. > > >PS - If you are using a router which serves IP addresses via DHCP to the > >localnet, you might want to see if it can do static IP assignment via > >MAC address recognition. > > I've got a switch/router that does exactly that... > > > On 21/06/07, Bryan Larsen <bryan [ dot ] larsen [ at ] gmail [ dot ] com> wrote: > > > >In fact, your problems might be due to conflicts between avahi and your > >local DNS. > > I'll look into that - thanks. > > > > Thanks all, folks. To update; I have successfully set up my work > machine (running Kubuntu) as a DNS with dnsmasq, and in the coming > days I'm hoping to instruct my server at home (Slackware) to perform > the same job for my LAN. > > Cheers. > > -- > "My country is the world, and my religion is to do good." > -- Thomas Paine > _______________________________________________ > Linux mailing list > Linux [ at ] lists [ dot ] oclug [ dot ] on [ dot ] ca > http://www.oclug.on.ca/mailman/listinfo/linux