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<mst...@debian.org> 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 in

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 <ebd7ecce-a194-921d-1f28-74469c78c...@mail.com>, john doe<johndoe65...@mail.com> wrote: What would people recommend for a home LAN DNS server that is authoritative for a single domain, providing

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 t

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

Hi, In article <ebd7ecce-a194-921d-1f28-74469c78c...@mail.com>, john doe<johndoe65...@mail.com> 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),

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

ob, 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 tool rather than learning a new tool. What would people recommend for a home LAN DNS server that is authoritative for a single domai

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<wool...@eeg.ccf.org> wrote: > The pacakge for ISC's BIND is called bind9. > > This would certainly do the job, but it's massively overkill for a

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

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 a

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

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

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

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 requests from machines on the LAN are still sent

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

all-back transport to work around UDP packet size > issues. Compared to UDP, TCP transport for DNS wastes system and network > resources. Yes and no. For a single query, UDP is indeed more efficient. You can have long-standing TCP connections though (multiple queries through the same TCP chan

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

discovered TCP seems to be recommened for DNSSEC so Ive enabled TCP port 53  and so far not had a problem! AFAIK TCP is just a fall-back transport to work around UDP packet size issues. Compared to UDP, TCP transport for DNS wastes system and network resources.

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

On 27/12/2017 13:18, Bernhard Schmidt wrote: Current BIND9 defaults to doing DNSSEC verification. DNSSEC needs large packets. You might have an issue with UDP fragments being dropped at your firewall/NAT Gateway? Thanks for this tip. Looking into it I discovered TCP seems to be recommened

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Andrew Wood <aw...@comms.org.uk> wrote: Hi, > I have a server which acts as a DNS server for our LAN. All our internal > servers have A records on it using a .local domain and it forwards all > other requests out to the root servers using the in built list provided > with

Re: BIND DNS problem after upgrading from Wheezy to Squeeze

Andrew W wrote: > > > Does anyone have any ideas please? > I had the same experience - I think (after trying this and that) the solution was ntp (time was behind on the server), but I am not really 100%. I was thinking first it has something to do with ipv6 or firewall, but after updating

BIND DNS problem after upgrading from Wheezy to Squeeze

I have a server which acts as a DNS server for our LAN. All our internal servers have A records on it using a .local domain and it forwards all other requests out to the root servers using the in built list provided with BIND. All clients on the LAN have this machine set as their only DNS

BIND DNS problem after upgrading from Wheezy to Squeeze

I have a server which acts as a DNS server for our LAN. All our internal servers have A records on it using a .local domain and it forwards all other requests out to the root servers using the in built list provided with BIND. All clients on the LAN have this machine set as their only DNS

Re: 9.2 DNS Confusion

the the above quote. This is called interleaved quoting. I've used various ways to disable IPv6 the GRUB amendment you mention is one, resolver issue appeared to still exist for me but I will check. Adding ipv6.disable=1 to the kernel command line should prevent the resolver to send DNS queries

Re[2]: 9.2 DNS Confusion

Hi Pascal, Surprised, no not really. Broken DNS, yes as I say not assigning blame anywhere but yes it's the Juniper and given I can do squat about that lets move on to another solution :) Gai.conf, didn't suggest this did disable IPv6 I just replied to a suggestion by another. I've used

Re: 9.2 DNS Confusion

Le 26/11/2017 à 14:23, Simon Slaytor a écrit : Today I Wiresharked the network and I can what's happening now. When I don a plain ping www.apple.com the resolver is sending 2x requests to the FW's DNS proxy the first for an IPv4 A record and the 2nd for an IPv6 record! You sound

Re[3]: 9.2 DNS Confusion

Ok a small update on this which might help sort my problem. Today I Wiresharked the network and I can what's happening now. When I don a plain ping www.apple.com the resolver is sending 2x requests to the FW's DNS proxy the first for an IPv4 A record and the 2nd for an IPv6 record

Re[2]: 9.2 DNS Confusion

Simon Slaytor" <si...@slaytor.com> Cc: debian-user@lists.debian.org Sent: 17/11/2017 16:39:57 Subject: Re: 9.2 DNS Confusion On Thu, Nov 16, 2017 at 07:55:18PM +, Simon Slaytor wrote: Hi Folks, Long time Debian user and up until now I've not had to reach out for help as I've

Re: 9.2 DNS Confusion

tion boxes and I'm > having the mother of all DNS issues. My network is simple: > > My network > 2 x Juniper SSG-140 (Active/Passive) HA 1xTrust 1xDMZ 1xUntrust interfaces > IPv4 only IPv6 is not enabled. > 2 x Netgear GSM724 Switches > > The Junipers do DNS proxying for the Tru

9.2 DNS Confusion

Hi Folks, Long time Debian user and up until now I've not had to reach out for help as I've always found the answer after a short Google. I've recently made the move from 8.x to 9.2 for my production boxes and I'm having the mother of all DNS issues. My network is simple: My network 2 x

Re: servidor de DNS externo sin clave correcta

31. Oct 2017 06:39 por javier.debian.bb...@gmail.com: > El 31/10/17 a las 10:11, Oscar Martinez escribió: >> buenas tardes lista estoy frente a un problema interesante tengo un servidor >> de DNS externo el coordinador de redes renunció y se llevó todas las claves >&

Re: servidor de DNS externo sin clave correcta

El 31/10/17 a las 10:11, Oscar Martinez escribió: buenas tardes lista estoy frente a un problema interesante tengo un servidor de DNS externo el coordinador de redes renunció y se llevó todas las claves de los equipos en particular el equipo a donde queremos acceder no tenemos la clave y

Re: servidor de DNS externo sin clave correcta

"nuestro temor es que si al tratar de tumbar y cambiar la clave del equipo podríamos perder la configuración del servicio de DNS. alguien podría ayudarme" Si sólo cambias la clave no. El 31 de octubre de 2017, 9:11, Oscar Martinez <omartinez...@gmail.com> escribió: > buenas

servidor de DNS externo sin clave correcta

buenas tardes lista estoy frente a un problema interesante tengo un servidor de DNS externo el coordinador de redes renunció y se llevó todas las claves de los equipos en particular el equipo a donde queremos acceder no tenemos la clave y contiene el servicio de DNS externo nuestro temor es que

Re: connectivité DNS secondaire et transfert de zones impossible

bonjour, Le Thu, 5 Oct 2017 10:18:18 +0200, Pascal Hambourg a écrit : > Le 05/10/2017 à 06:37, Etilem a écrit : > > > > bonjour, > > > > après avoir fait, il y a un mois environ, une migration de jessie > > vers stretch sur deux serveurs DNS, > > >

Re: Can't find the DNS Servers

On Fri 06 Oct 2017 at 09:03:05 (-0400), Greg Wooledge wrote: > On Thu, Oct 05, 2017 at 08:35:22PM -0500, David Wright wrote: > > On Thu 05 Oct 2017 at 08:55:33 (-0400), Greg Wooledge wrote: > > > On Wed, Oct 04, 2017 at 07:23:51PM -0500, David Wright wrote: > > > > Well, thank you. But this

Re: Can't find the DNS Servers

On Fri 06 Oct 2017 at 01:22:18 (-0400), Gene Heskett wrote: > On Thursday 05 October 2017 22:56:33 David Wright wrote: > > One advantage of Powerlines is that they aren't bothered by > > microwaves which knock out nearby 2GHz devices. > > As in cooking microwaves? If its leaking that badly, have

Re: (solved) Can't find the DNS Servers

t; >>from another computer and found that the "hosts:" line was missing "dns and > >>mdns4'. I added these to the end of the line and everything now works fine. > >>I can't thank all of you enough for your support. > > > >I could be wrong but I think y

Re: Can't find the DNS Servers

On Thu, Oct 05, 2017 at 08:35:22PM -0500, David Wright wrote: > On Thu 05 Oct 2017 at 08:55:33 (-0400), Greg Wooledge wrote: > > On Wed, Oct 04, 2017 at 07:23:51PM -0500, David Wright wrote: > > > Well, thank you. But this doesn't explain the paragraph above my comment. > > > I'm just trying to

Re: Can't find the DNS Servers

esday 04 October 2017 14:35:25 David Wright wrote: > > > > > As I just posted, I thought the OP was already using a DNS > > > > > server in the Actiontec router. (I don't have that choice.) > > > > > > > > Why not David? > > > > >

Re: Can't find the DNS Servers

s I just posted, I thought the OP was already using a DNS server > > > > in the Actiontec router. (I don't have that choice.) > > > > > > Why not David? > > > > Because I have a "plastic" router with a server for DHCP but not DNS. > > > >

Re: Can't find the DNS Servers

oblem resolutions, compared to being able to ask Google "how > do I set up NAT on Debian stretch", or whatever issue you're currently > trying to solve. I had assumed that the OP still had internet access from their other machines. > As far as /etc/hosts vs. setting up an internal

Re: (solved) Can't find the DNS Servers

udp port 53 or tcp port 53 or udp port 5353 While doing: getent hosts go.dev Reco Hooray, Solved. Rico, your question about nsswitch.conf was the key. I printed out the file from another computer and found that the "hosts:" line was missing "dns and mdns4'. I added t

Re: (solved) Can't find the DNS Servers

t; > > >tcpdump -nvi any udp port 53 or tcp port 53 or udp port 5353 > > > >While doing: > > > >getent hosts go.dev > > > >Reco > > > > > Hooray, Solved. > Rico, your question about nsswitch.conf was the key. I printed out the f

Re: (solved) Can't find the DNS Servers

ter 60 seconds): > > > > tcpdump -nvi any udp port 53 or tcp port 53 or udp port 5353 > > > > While doing: > > > > getent hosts go.dev > > > > Reco > > > > > Hooray, Solved. > Rico, your question about nsswitch.conf was the ke

Re: (solved) Can't find the DNS Servers

, Solved. Rico, your question about nsswitch.conf was the key. I printed out the file from another computer and found that the "hosts:" line was missing "dns and mdns4'. I added these to the end of the line and everything now works fine. I can't thank all of you enough f

Re: Can't find the DNS Servers

, or whatever issue you're currently trying to solve. As far as /etc/hosts vs. setting up an internal DNS server, most home LANs are probably small enough that I would simply use /etc/hosts. Things may change if you live in a mansion with a staff, or you're the landlord for an apartment building, or

Re: connectivité DNS secondaire et transfert de zones impossible

Le 05/10/2017 à 06:37, Etilem a écrit : bonjour, après avoir fait, il y a un mois environ, une migration de jessie vers stretch sur deux serveurs DNS, - un primaire (dns.etilem.net) et - un secondaire (ns1.etilem.net), je rencontre un problème de connectivité du service DNS

Re: Can't find the DNS Servers

04AM -0500, David Wright wrote: > > > > > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > > > > > A correct way to fix this is to "persuade" your DHCP server not to > > > > > > provide DNS information. > > > > > > Even

connectivité DNS secondaire et transfert de zones impossible

bonjour, après avoir fait, il y a un mois environ, une migration de jessie vers stretch sur deux serveurs DNS, - un primaire (dns.etilem.net) et - un secondaire (ns1.etilem.net), je rencontre un problème de connectivité du service DNS secondaire. j'ai l'habitude de me servir du

Re: Can't find the DNS Servers

t 04, 2017 at 11:59:04AM -0500, David Wright wrote: > > > > > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > > > > > A correct way to fix this is to "persuade" your DHCP server > > > > > > not to provide DNS information

Re: Can't find the DNS Servers

t; On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > > > > A correct way to fix this is to "persuade" your DHCP server not > > > > > to provide DNS information. > > > > > Even more correct way is to force your DNS-at-DHCP to use > > &

Re: Can't find the DNS Servers

this is to "persuade" your DHCP server not to provide DNS information. Even more correct way is to force your DNS-at-DHCP to use 8.8.8.8 as forwarder DNS. Since it's unnaturally complex to do so in a consumer-grade routers, a hack is in order. But won't that send local host lookups to go

Re: Can't find the DNS Servers

ay to fix this is to "persuade" your DHCP server not > > > > to provide DNS information. > > > > Even more correct way is to force your DNS-at-DHCP to use > > > > 8.8.8.8 as forwarder DNS. > > > > Since it's unnaturally complex to do so in a c

Re: Can't find the DNS Servers

d were isc-dhcp-client and > > > > > resolvconf. You are right about the br1 entry not being needed. the > > > > > virtual > > > > > machine works fine without it. > > > > > > > > So, what we have now is a definite improvement o

Re: Can't find the DNS Servers

ave the same problem. Attached are the new files. Already installed were isc-dhcp-client and resolvconf. You are right about the br1 entry not being needed. the virtual machine works fine without it. So, what we have now is a definite improvement over the last time, but some twists are needed. While &

Re: Can't find the DNS Servers

017 at 11:59:04AM -0500, David Wright wrote: > > > > > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > > > > > A correct way to fix this is to "persuade" your DHCP server not to > > > > > > provide DNS information. > > >

Re: Can't find the DNS Servers

On Wed 04 Oct 2017 at 13:21:02 (-0400), Greg Wooledge wrote: > On Wed, Oct 04, 2017 at 11:59:04AM -0500, David Wright wrote: > > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > > A correct way to fix this is to "persuade" your DHCP server not to > > >

Re: Can't find the DNS Servers

2017 at 09:11:37 (+0300), Reco wrote: > > > > > A correct way to fix this is to "persuade" your DHCP server not to > > > > > provide DNS information. > > > > > Even more correct way is to force your DNS-at-DHCP to use 8.8.8.8 as > > > &g

Re: Can't find the DNS Servers

fix this is to "persuade" your DHCP server not to > > > > provide DNS information. > > > > Even more correct way is to force your DNS-at-DHCP to use 8.8.8.8 as > > > > forwarder DNS. > > > > Since it's unnaturally complex to do so in a co

Re: Can't find the DNS Servers

On Wed, Oct 04, 2017 at 08:59:46PM +0300, Reco wrote: On Wed, Oct 04, 2017 at 11:59:04AM -0500, David Wright wrote: On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > A correct way to fix this is to "persuade" your DHCP server not to > provide DNS information. > Ev

Re: Can't find the DNS Servers

now is a definite improvement over the last time, but > > some twists are needed. > > > > While "dns-nameserver" stanzas are working now, your DHCP server also > > advertises its own: > > > > > # Dynamic resolv.conf(5) file for glibc resolver(3

Re: Can't find the DNS Servers

On Wed, Oct 04, 2017 at 11:59:04AM -0500, David Wright wrote: > On Wed 04 Oct 2017 at 09:11:37 (+0300), Reco wrote: > > A correct way to fix this is to "persuade" your DHCP server not to > > provide DNS information. > > Even more correct way is to force

Re: Can't find the DNS Servers

and > > resolvconf. You are right about the br1 entry not being needed. the virtual > > machine works fine without it. > > So, what we have now is a definite improvement over the last time, but > some twists are needed. > > While "dns-nameserver" stanza

Re: Can't find the DNS Servers

gt; In your diagnostic command-and-response session, be sure to include > the results of your attempts to ping your nameserver by IP address, > and of performing a DNS lookup using that nameserver. See examples > above. > > In the event that one of the commands does not work as e

Re: Can't find the DNS Servers

On Wed, Oct 04, 2017 at 08:55:51AM -0400, Michael Stone wrote: > If you are not using resolvconf, a reliable way to stop the isc dhcp client > from updating resolv.conf is to create > /etc/dhcp/dhclient-enter-hooks.d/xlocal-nodnsupdate containing > > #!/bin/sh > make_resolv_conf(){ :; } You

Re: Can't find the DNS Servers

On Wed, Oct 04, 2017 at 08:24:16AM -0400, Greg Wooledge wrote: On Wed, Oct 04, 2017 at 09:11:37AM +0300, Reco wrote: Locate /etc/dhcp/dhclient.conf. Replace inside it: request subnet-mask, broadcast-address, time-offset, routers, domain-name, domain-name-servers, domain-search,

Re: Can't find the DNS Servers

bian.org has address 149.20.4.15 www.debian.org has address 128.31.0.62 www.debian.org has IPv6 address 2001:4f8:1:c::15 ^^ This shows a DNS name resolution attempt using resolv.conf but not libc's resolver. wooledg:~$ getent hosts www.debian.org 2001:4f8:1:c::15 www.debian.org ^^ This shows a &q

Re: Can't find the DNS Servers

Hi. On Wed, Oct 04, 2017 at 08:24:16AM -0400, Greg Wooledge wrote: > On Wed, Oct 04, 2017 at 09:11:37AM +0300, Reco wrote: > > Locate /etc/dhcp/dhclient.conf. Replace inside it: > > > > request subnet-mask, broadcast-address, time-offset, routers, > > domain-name,

Re: Can't find the DNS Servers

On Wed, Oct 04, 2017 at 09:11:37AM +0300, Reco wrote: > Locate /etc/dhcp/dhclient.conf. Replace inside it: > > request subnet-mask, broadcast-address, time-offset, routers, > domain-name, domain-name-servers, domain-search, host-name > dhcp6.name-servers, dhcp6.domain-search,

Re: Can't find the DNS Servers

the virtual > machine works fine without it. So, what we have now is a definite improvement over the last time, but some twists are needed. While "dns-nameserver" stanzas are working now, your DHCP server also advertises its own: > # Dynamic resolv.conf(5) file for glibc resolver(

Re: Can't find the DNS Servers

it. At least you've now got the external nameservers in your resolv.conf. And does your router do DNS or not? Cheers, David. Symptoms: Any package that needs access to the network sends an error message indicating that it doesn't have access to the internet. Ping doesn't work for names bu

Re: Can't find the DNS Servers

the external nameservers in your resolv.conf. And does your router do DNS or not? Cheers, David.

Re: Can't find the DNS Servers

ork interfaces available on your system # and how to activate them. For more information, see interfaces(5). ## The loopback network interface auto lo iface lo inet loopback ##The primary network interface auto enp4s0 iface enp4s0 inet dhcp dns-nameserver 8.8.8.8 dns-nameserver 8.8.

Re: Can't find the DNS Servers

; > > > auto enp4s0 > > > iface enp4s0 inet dhcp > > > dns-nameserver 8.8.4.4 > > > dns-nameserver 8.8.8.8 > > > > > > Please note the indentation, > > > > … which looks tidy, but the indentation carries no meaning > > (le

Re: Can't find the DNS Servers

Hi. On Mon, Oct 02, 2017 at 11:15:16AM -0500, David Wright wrote: > On Mon 02 Oct 2017 at 10:00:28 (+0300), Reco wrote: > > > To bring order to this chaos, you'll need this e/n/i: > > > > auto enp4s0 > > iface enp4s0 inet dhcp > > dns-names

Re: Can't find the DNS Servers

On Mon 02 Oct 2017 at 06:26:08 (-0400), Gene Heskett wrote: > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > This is the second time I've tried to send this. The first one just > > > disappeared to the bit

Re: Can't find the DNS Servers

On Mon 02 Oct 2017 at 10:00:28 (+0300), Reco wrote: > To bring order to this chaos, you'll need this e/n/i: > > auto enp4s0 > iface enp4s0 inet dhcp > dns-nameserver 8.8.4.4 > dns-nameserver 8.8.8.8 > > Please note the indentation, … which looks tidy, but

Re: E-mail headers 101 (was: Can't find the DNS Servers)

On Monday 02 October 2017 06:39:00 Reco wrote: > On Mon, Oct 02, 2017 at 06:26:08AM -0400, Gene Heskett wrote: > > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > > This is the second time I've tried to send

Re: E-mail headers 101 (was: Can't find the DNS Servers)

On Mon, Oct 02, 2017 at 06:26:08AM -0400, Gene Heskett wrote: > On Monday 02 October 2017 03:00:28 Reco wrote: > > > Hi. > > > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > > This is the second time I've tried to send this. The first one just > > > disappeared to the bit

Re: Can't find the DNS Servers

On Monday 02 October 2017 03:00:28 Reco wrote: > Hi. > > On Sun, Oct 01, 2017 at 07:26:30PM -0700, Gary Roach wrote: > > This is the second time I've tried to send this. The first one just > > disappeared to the bit bucket I assume. So lets try again. > > It did not. Everyone on the list

Re: Can't find the DNS Servers

solv.conf. So, let's get this party started. First, you have "eth0" defined in your /etc/network/interfaces. A simple DHCP configuration that *can*, but *does not* honor your "dns-nameserver" stanzas. The reason being - you put them *after* br1 interface. Second, you have &quo

Re: Can't find the DNS Servers

On 2017-10-02 12:26, Gary Roach wrote: > On 09/27/2017 09:31 AM, Reco wrote: >> On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: >>> On 26/09/17 19:50, Reco wrote: Please post these things from the problematic PC: ip a l ip ro l >>> >>> Can I make a request?

Re: Can't find the DNS Servers

ck network interface auto lo iface lo inet loopback ##The primary network interface allow-hotplug eth0 iface eth0 inet dhcp ##The bridge network interface to qemu virtual machine #auto br1 iface br1 inet dhcp bridge_ports br1 bridge_stp off bridge_fd 0.0 dns-nameserver 8.8.8.8 dns-nameserv

Re: Can't find the DNS Servers

o inet loopback > > ##The primary network interface > allow-hotplug eth0 > iface eth0 inet dhcp > > > ##The bridge network interface to qemu virtual machine > #auto br1 > iface br1 inet dhcp >bridge_ports br1 >bridge_stp off >bridge_fd 0.0 &g

Re: Can't find the DNS Servers

interface to qemu virtual machine #auto br1 iface br1 inet dhcp bridge_ports br1 bridge_stp off bridge_fd 0.0 dns-nameserver 8.8.8.8 dns-nameserver 8.8.4.4 # This file describes the network interfaces available on your system # and how to activate them. For more information, see in

Re: Can't find the DNS Servers

mu virtual > machine over the host OS. Since then the host system does not seem able > to find a DNS server. The really strange thing is that I installed > Kubuntu as the guest OS and that works fine. I suspect that qemu has > glommed onto the eth0 device and won't let the hos

Re: Can't find the DNS Servers

Le 30/09/2017 à 04:18, Gary Roach a écrit : Well the philosophy and stories are nice but my access to the internet is still among the missing. We are waiting for the information asked by Reco several days ago : ip address list ip route list cat /etc/resolv.conf tcpdump -nvi any udp port

Re: Can't find the DNS Servers

. But there is the forcible way and the graceful way. Here is a little experience of mine. I had a host configured with DHCP. As expected, dhclient wrote the IPv4 DNS addresses received from the DHCP server into resolv.conf. My network also had an IPv6 router sending advertisements containing IPv6 DNS

Re: Problème DNS qui commence à me brouter.....

Bonjour Vincent, Tu peux m'en dire plus, je n'ai jamais fait. (dans l'attente de ta réponse je vais chercher) Merci

Re: Can't find the DNS Servers

On Wed, Sep 27, 2017 at 10:16:20PM +1300, Richard Hector wrote: > On 26/09/17 19:50, Reco wrote: > > Please post these things from the problematic PC: > > > > ip a l > > > > ip ro l > > Can I make a request? When giving example commands, can you give them in > full, rather than abbreviated?

Re: Finding the appropriate manpage [Re: Can't find the DNS Servers]

On 2017-09-27, Lck Ras wrote: > On 09/27/2017 06:16 AM, Don Armstrong wrote: >> In almost every case, if you don't know the right man page, apropos (or >> man -k) will help you find it. If that's not good enough, man -K >> dhclient will eventually find all of them. >> >>

Re: Finding the appropriate manpage [Re: Can't find the DNS Servers]

On 09/27/2017 06:16 AM, Don Armstrong wrote: > In almost every case, if you don't know the right man page, apropos (or > man -k) will help you find it. If that's not good enough, man -K > dhclient will eventually find all of them. > > dhclient (8) - Dynamic Host Configuration Protocol

Re: Can't find the DNS Servers

On 26/09/17 19:50, Reco wrote: > Please post these things from the problematic PC: > > ip a l > > ip ro l Can I make a request? When giving example commands, can you give them in full, rather than abbreviated? I believe 'a' and 'ro' are 'address' and 'route' respectively, but 'l' is a bit

Re: Can't find the DNS Servers

the domainname utility to set that for > > what, a decade?, and I could probably remove that line. Belt and > > suspenders I guess. :) > > The domainname(1) command is for NIS, not DNS. > > The "domain" directive in resolv.conf is deprecated (maybe?) in favor

Re: Can't find the DNS Servers

On Tuesday 26 September 2017 15:43:35 Greg Wooledge wrote: > On Tue, Sep 26, 2017 at 03:33:48PM -0400, Gene Heskett wrote: > > > > nameserver 192.168.XX.1 > > > > search host dns > > > > domain coyote.den > > > > I started with Red Hat 5.

Re: Can't find the DNS Servers

ver 192.168.XX.1 > > search host dns > > domain coyote.den > > > > Can you detail these domains called host and dns? > > I keep thinking that it's some relic from libc4 or libc5, before the > adoption of nsswitch.conf, but I am at a loss how to

Finding the appropriate manpage [Re: Can't find the DNS Servers]

On Tue, 26 Sep 2017, Greg Wooledge wrote: > For years, I have been searching back and forth and up and down in > dhclient(8) and dhclient.conf(5) and finding NOTHING. > Turns out the REASON I couldn't find anything was because some bright > spark decided to split the documentation into multiple

Re: Can't find the DNS Servers

On Tue, Sep 26, 2017 at 03:43:35PM -0400, Greg Wooledge wrote: NAME resolver - resolver configuration file SYNOPSIS /etc/resolv.conf ... search Search list for host-name lookup. The search list is normally determined from the local domain name; by default, it

Re: Can't find the DNS Servers

e that line. Belt and > suspenders I guess. :) The domainname(1) command is for NIS, not DNS. The "domain" directive in resolv.conf is deprecated (maybe?) in favor of the "search" list, but the latter is a list of domain names, not places to consult. (If "domain&quo

Re: Can't find the DNS Servers

On Tue, Sep 26, 2017 at 03:33:48PM -0400, Gene Heskett wrote: > > > nameserver 192.168.XX.1 > > > search host dns > > > domain coyote.den > I started with Red Hat 5.0, in the late '90's. And it looks like stretch > may have deprecated the executable

Re: Can't find the DNS Servers

ver 192.168.XX.1 > > search host dns > > domain coyote.den > > > > Can you detail these domains called host and dns? > > I keep thinking that it's some relic from libc4 or libc5, before the > adoption of nsswitch.conf, but I am at a loss how to find > document

Re: Can't find the DNS Servers

ll it to do. > > > > But that day hasn't even shown a cloud of dust on the time horizon I > > can see from a 83 yo in <2 weeks viewpoint. > > > > Because all you so-called experts THINK it works ok the way it is, > > we get badmouthed and called idiots. B

<    1   2   3   4   5   6   7   8   9   10   >