Simple DNS server (was Re: [nzlug] mdadm and lvm on a live distro?)

[Warren]

On 2007/03/11 12:53, "Robin Sheat" <robin at kallisti.net.nz> wrote:

> On Sunday 11 March 2007 10:41, Warren wrote:
>> <flamesuit>gedit??? vi, surely? :-P</flamesuit>
> He wanted a GUI tool :)

Oh ... In that case ... GVim :-) ... Anyhow ...

> 
>> From what I understood, this was an internal / RFC 1819 kinda install, so
>> what better a way to get to learn how to do DNS, but by getting in there
>> and breaking it?
> Definitely true. What I do on a LAN is run pdnsd (I think that's the one),
> which is a really basic DNS cache that can source it's data from /etc/hosts.
> So I run that, point all the clients to that as their DNS server, and then
> just update /etc/hosts on that machine to add a new mapping. I think it'll do
> reverse, too, automatically. On my home LAN, I'm using DNSMasq which combines
> DHCP and DNS, so machines get the name that they're advertising, and then all
> the other machines on the network can ask for them by that without any file
> editing being involved.

That all sounds good - there are some really good tools out there when you
go looking.

> 
>> Of course, you could also look at the ability to deliberately break the
>> internet (grab a hosts file that lists a whole heap of ad servers and add
>> that in... That would be an interesting if not nasty exercise ...)
> It wouldn't work (alas). It's them that gets to specify where their
> nameservers are, and unless they're likely to point them to you, nobody's
> going ask you where they are.

My lan is set all via DHCP (some static, some dynamic) - all point to my
internal bind DNS server ... As all the clients see every domain on that
server as being "authorative", I can put anything I like.  If I put
"xtra.co.nz" on there, then I could really botch up my connection to the
internet.

But - I can see major issues in trying to kill all adservers (eg.
ads.inl.co.nz) - especially seeing as you can't just pull an entire zone any
more.

Anyhow - I digress :-)