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

On Fri 02 Mar 2018 at 23:56:02 (+0100), Pascal Hambourg wrote: > Le 28/02/2018 à 21:13, David Wright a écrit : > >>># > >>># /etc/interfaces.d/directcable for west 2018-02-25 > >>> > >>>auto eth0 > >>>iface eth0 inet static > >>> address 192.168.2.15/24 > >> > >>Fine. You could also add

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

Le 28/02/2018 à 21:13, David Wright a écrit : # # /etc/interfaces.d/directcable for west 2018-02-25 auto eth0 iface eth0 inet static address 192.168.2.15/24 Fine. You could also add "allow-hotplug eth0" in case eth0 would be discovered late. OK. Tried that here. The ip a is before

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

On Wed 28 Feb 2018 at 19:42:27 (+0100), Pascal Hambourg wrote: > Le 28/02/2018 à 18:14, David Wright a écrit : > > > >$ cat /etc/network/interfaces /etc/network/interfaces.d/directcable > ># This file describes the network interfaces available on your system > ># and how to activate them. For more

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

Le 28/02/2018 à 18:14, David Wright a écrit : $ cat /etc/network/interfaces /etc/network/interfaces.d/directcable # This file describes the network interfaces available on your system # and how to activate them. For more information, see interfaces(5). source /etc/network/interfaces.d/* # The

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

On Tue 27 Feb 2018 at 20:59:17 (+0100), Pascal Hambourg wrote: > Le 25/02/2018 à 18:35, David Wright a écrit : > >On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: > > > On disadvantage is that these addresses are not globally unique (the > link local prefix exists on all

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

Le 25/02/2018 à 18:35, David Wright a écrit : On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: On disadvantage is that these addresses are not globally unique (the link local prefix exists on all interfaces) and must be appended with an interface name. Not an issue here. The

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

On Sat 24 Feb 2018 at 09:49:27 (+0100), Pascal Hambourg wrote: > Le 22/02/2018 à 22:57, David Wright a écrit : > >On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: > >>Le 23/01/2018 à 18:08, David Wright a écrit : > >>> > >>>[My Laptop] --- wireless connection IPv4 --- [Router] ---

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

On 2018-02-24, Pascal Hambourg wrote: > > Anyway, we have a saying here which roughly translates to : "you cannot > force an unthirsty donkey to drink". I looked it up (because neither me nor hubby--de vieille souche--recognized it right off). On ne saurait faire boire

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

Le 22/02/2018 à 22:57, David Wright a écrit : On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: Le 23/01/2018 à 18:08, David Wright a écrit : [My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem | / | | CAT5

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

On Tue 23 Jan 2018 at 20:56:31 (+0100), Pascal Hambourg wrote: > Le 23/01/2018 à 18:08, David Wright a écrit : > > > >[My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem > > | / | > > | CAT5 cable IPv6/

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

I didn't read all the answers (only half of those). But I have the same problem and I now think it has nothing to do with named, bind (4 8 or 9). During Stretch installation with netinst, Network-manager configured once for all /etc/hostname and /etc/resolv.conf. As I have only one routable

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

Le 23/01/2018 à 18:08, David Wright a écrit : [My Laptop] --- wireless connection IPv4 --- [Router] --- Internet Modem | / | | CAT5 cable IPv6/ | | / | wireless/wired [My

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

On Tue 23 Jan 2018 at 16:06:01 (-), Andy Hawkins wrote: > Hi, > > In article <20180123144327.GA6815@alum>, >David Wright wrote: > > This would all be a step in the wrong direction here. Point (2) was > > that using IPv6 over CAT5 avoids swamping the

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

Hi, In article <20180123144327.GA6815@alum>, David Wright wrote: > This would all be a step in the wrong direction here. Point (2) was > that using IPv6 over CAT5 avoids swamping the router. (Of course, > that's already been snipped out of the thread.) If the

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

On Tue 23 Jan 2018 at 13:41:31 (+), Joe wrote: > On Tue, 23 Jan 2018 11:12:41 + (UTC) > Curt wrote: > > > On 2018-01-23, Andy Hawkins wrote: > > > Hi, > > > In article <20180122185135.GA12212@alum>, > > >David

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

On Tue, 23 Jan 2018 11:12:41 + (UTC) Curt wrote: > On 2018-01-23, Andy Hawkins wrote: > > Hi, > > In article <20180122185135.GA12212@alum>, > >David Wright wrote: > >>> You should be able to do that with IPv4 too. If

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

On 2018-01-23, Andy Hawkins wrote: > Hi, > In article <20180122185135.GA12212@alum>, >David Wright wrote: >>> You should be able to do that with IPv4 too. If DHCP address allocation >>> fails, >> >> Elaborate on this please. What do you

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

Hi, In article <20180122185135.GA12212@alum>, David Wright wrote: >> You should be able to do that with IPv4 too. If DHCP address allocation >> fails, > > Elaborate on this please. What do you mean by "fails". > What am I meant to want to fail? If a host

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

On Mon 22 Jan 2018 at 17:21:23 (-), Andy Hawkins wrote: > Hi, > > In article <20180119151835.GA8374@alum>, >David Wright wrote: > > I have one valuable use for IPv6 which is point-to-point connections. > > I plug a CAT5 cable into the two ends and use

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

Hi, In article <20180119151835.GA8374@alum>, David Wright wrote: > I have one valuable use for IPv6 which is point-to-point connections. > I plug a CAT5 cable into the two ends and use predefined functions > to bulk-transfer files with scp. Why? > 1) I don't

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

Le 19/01/2018 à 06:10, D. R. Evans a écrit : Pascal Hambourg wrote on 01/18/2018 02:41 PM: Note : ping is not a proper DNS tool becaus it calls the libc resolver for name resolution, which may use other name sources than DNS. Use dig, host or nslookup instead. I admit that I'm quite

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

Le 19/01/2018 à 16:14, Rob van der Putten a écrit : If you have got your own IPv6 /48 combined with RFC1918 IPv4 then split horizon DNS is probably a good idea; https://en.wikipedia.org/wiki/Split-horizon_DNS Why ? My home network also has private IPv4 + global IPv6 addresse and I use

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

On Fri, Jan 19, 2018 at 04:14:38PM +0100, Rob van der Putten wrote: AFAIK Bind is the only named with a good split horizon implementation. most implementations will let you bind to a particular IP so you can run different configurations on internal & external IPs. bind has a lot of

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

On Fri 19 Jan 2018 at 08:47:25 (-0500), Greg Wooledge wrote: > On Fri, Jan 19, 2018 at 11:45:23AM -, Andy Hawkins wrote: > > Apologies for the slight thread hijack. > > > > What would people recommend for a home LAN DNS server that is authoritative > > for a single domain, providing A, ,

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

Hi On 19/01/18 15:08, Andy Hawkins wrote: 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

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

Hi, In article <102059aa-fd21-11e7-9b6a-00163eeb5...@msgid.mathom.us>, Michael Stone wrote: > If you said why you were looking to abandon a (presumably working?) > solution that might help explain your requirements. If your goal is > simple integration between DNS

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

Hi, In article <20180119134725.lk5gywprdit4s...@eeg.ccf.org>, Greg Wooledge 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

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

On Fri, Jan 19, 2018 at 12:27:57PM -, Andy Hawkins wrote: Hi, In article , john doe wrote: What would people recommend for a home LAN DNS server that is authoritative for a single domain, providing A, , PTR

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

On Fri, Jan 19, 2018 at 08:47:25AM -0500, Greg Wooledge wrote: 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,

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

On Fri, Jan 19, 2018 at 11:45:23AM -, Andy Hawkins wrote: > Apologies for the slight thread hijack. > > What would people recommend for a home LAN DNS server that is authoritative > for a single domain, providing A, , PTR (both IPv4 and IPv6), NS and > CNAME records to that domain? My

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

Hi, In article , john doe wrote: >> What would people recommend for a home LAN DNS server that is authoritative >> for a single domain, providing A, , PTR (both IPv4 and IPv6), NS and >> CNAME records to that

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

On 1/19/2018 12:45 PM, Andy Hawkins wrote: Hi, Apologies for the slight thread hijack. In article <20180118214314.442arvnrw4xbx...@eeg.ccf.org>, Greg Wooledge wrote: The pacakge for ISC's BIND is called bind9. This would certainly do the job, but it's

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

Hi, Apologies for the slight thread hijack. In article <20180118214314.442arvnrw4xbx...@eeg.ccf.org>, Greg Wooledge wrote: > The pacakge for ISC's BIND is called bind9. > > This would certainly do the job, but it's massively overkill for a simple > home LAN DNS

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

Greg Wooledge wrote on 01/18/2018 02:43 PM: > > The pacakge for ISC's BIND is called bind9. > > This would certainly do the job, but it's massively overkill for a simple > home LAN DNS server. Nevertheless, if it's what you already know, there > is benefit in using the known but overengineered

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

Pascal Hambourg wrote on 01/18/2018 02:41 PM: > > named is not a package name. The package name is and has always been > bind9. Note that there are other recursive DNS server packages such as > unbound. Ah! It's been so long since I've built a system that didn't install bind automatically

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

On Thu, Jan 18, 2018 at 02:34:50PM -0700, D. R. Evans wrote: > Can someone please point me to intelligible instructions as to how to have the > stretch box respond correctly to remote DNS requests coming in over the local > network? Install a name server. Make sure it's listening on your LAN

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

Le 18/01/2018 à 22:34, D. R. Evans a écrit : I am trying to configure a debian stretch box to provide certain services to my home network. (In the past this was a wheezy box, and I had everything working fine. I have not changed the configuration of any other machine; so, for example, DNS