[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: stretch and DNS name resolution service for other devices on a LAN



Hi,

In article <[🔎] 20180119134725.lk5gywprdit4s3da@eeg.ccf.org>,
           Greg Wooledge<wooledg@eeg.ccf.org> wrote:
> My only experience is with bind8, bind9, and tinydns (from djbdns).
> I've never used IPv6 for anything.  None of the networks that I deal
> with use IPv6, period.  They don't even have the option.
>
> I have to wonder what kind of home you live in, that requires local
> IPv6.  Most homes are small enough that you can get by with the roughly
> 2^24 addresses available in the private IPv4 ranges (10/8, 192.168/16,
> and 172.16/12).
>
> So, my first pick would be tinydns, and forget about IPv6.  But I may
> not be the best person to try to address whatever your needs are.

I guess I don't *need* IPv6, but as a technology geek it's just something I
wanted to play around with. I've set up a tunnel with Hurricane Electric
that gets me a fully routable IPv6 prefix that I can assign an address from
to each of the devices on my LAN.

I do use a 192.168/16 for my local IPv4 addressing, but given that moving
forward IPv6 is likely to become more and more available, I thought it worth
having a play with. I can now (if I want) allow IPv6 access to every device
on my internal network without having to worry about NAT and port forwarding
to get connections through my firewall.

Thanks for the pointer to tinydns, I'll take a look.

Andy


Reply to: