public inbox for gentoo-user@lists.gentoo.org
 help / color / mirror / Atom feed
From: Alan McKinnon <alan.mckinnon@gmail.com>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Re: Wireless DHCP takes over resolv.conf
Date: Mon, 11 Jul 2016 23:50:48 +0200	[thread overview]
Message-ID: <578414B8.8060904@gmail.com> (raw)
In-Reply-To: <nm11je$ut7$1@ger.gmane.org>

On 11/07/2016 23:03, Grant Edwards wrote:
> On 2016-07-11, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>> On 11/07/2016 22:29, Grant Edwards wrote:
>>> On 2016-07-11, Alan McKinnon <alan.mckinnon@gmail.com> wrote:
>>>
>>>> why don't you go with the dns server addresses supplied by each
>>>> network's dhcp? Presumably the admin put them their because they
>>>> work on that network.
>>>
>>> One might think that, but I find it often not to be the case.  I can
>>> recall many networks where the DNS servers returned by the DHCP server
>>> didn't work well at all, and things got a _lot_ better when I manually
>>> configured a couple working DNS servers (e.g. the Google ones at
>>> 8.8.8.8 and 8.8.4.4).  Around here, Comcast's DNS servers are famously
>>> bad.
>
>> Then shoot the idiot running that wireless network.
>
> You're not actually allowed to do that General Dreedle...
>
>> If he's one of my juniors, tell me so I can fire him (as he's just
>> proved he can't do the job he's paid to do)
>
> And if you're at a customer or vendor site?  A friend's or relative's
> house?  Using a municiple WiFi system?  Using WiFi on an airplane,
> bus, train, whatever?
>
> Sometimes you just need to get along with people and get some work
> done.  You always can't demand that things get done your way or
> somebody's gonna get fired or taken out back and beaten...
>

Pretty much always worked for me. I'm one of the guys that sets things 
up so that guys like you have no reason to ever say "Around here, 
Comcast's DNS servers are famously bad". Replace "Comcast" with the real 
name of my real employer. If my team gets that wrong (and we never have 
thus far), millions of people immediately and at once suffer. So forgive 
me if I'm a tad touchy on the subject.

But seriously, if the dns servers provided by dhcp aren't up to snuff 
then by all means put working ones in your resolv.conf. And also help 
the owner of the network fix his config - there really is no excuse for 
setting up software to tell people to use broken or badly behaved caches.

Alan


  reply	other threads:[~2016-07-11 21:51 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-09 14:53 [gentoo-user] Wireless DHCP takes over resolv.conf Mick
2016-07-09 15:34 ` Fernando Rodriguez
2016-07-09 19:25   ` Mick
2016-07-09 19:53     ` Fernando Rodriguez
2016-07-11  8:32       ` Emanuele Rusconi
2016-07-11 15:31         ` Alan McKinnon
2016-07-11 18:13           ` Mick
2016-07-11 20:07             ` Alan McKinnon
2016-07-11 20:29               ` [gentoo-user] " Grant Edwards
2016-07-11 20:34                 ` Alan McKinnon
2016-07-11 21:03                   ` Grant Edwards
2016-07-11 21:50                     ` Alan McKinnon [this message]
2016-07-11 22:32                       ` Mick
2016-07-12 21:18           ` [gentoo-user] " Emanuele Rusconi
2016-07-12 22:36             ` [gentoo-user] " Grant Edwards
2016-07-12 22:58 ` [gentoo-user] " Marat BN

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=578414B8.8060904@gmail.com \
    --to=alan.mckinnon@gmail.com \
    --cc=gentoo-user@lists.gentoo.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox