From: Laszlo Ersek <lersek@redhat.com>
To: Rebecca Cran <rebecca@bluestop.org>,
edk2-devel@lists.01.org, Jaben Carsey <jaben.carsey@intel.com>
Subject: Re: [PATCH] StdLib: Update resolv.conf to use Google's DNS servers
Date: Fri, 8 Mar 2019 10:26:24 +0100 [thread overview]
Message-ID: <f428975a-88c9-58c2-a6fe-44e32a897b5b@redhat.com> (raw)
In-Reply-To: <20190308021455.89858-1-rebecca@bluestop.org>
On 03/08/19 03:14, Rebecca Cran via edk2-devel wrote:
> The current servers listed appear to be unusable. I suspect most
> people will get correct DNS servers via DHCP, but the defaults
> should work for anyone.
>
> Contributed-under: TianoCore Contribution Agreement 1.1
> Signed-off-by: Rebecca Cran <rebecca@bluestop.org>
> Reviewed-by: Jaben Carsey <jaben.carsey@intel.com>
> Reviewed-by: Laszlo Ersek <lersek@redhat.com>
> ---
> StdLib/Efi/StdLib/etc/resolv.conf | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/StdLib/Efi/StdLib/etc/resolv.conf b/StdLib/Efi/StdLib/etc/resolv.conf
> index 3ac16ac230..724e6297b2 100644
> --- a/StdLib/Efi/StdLib/etc/resolv.conf
> +++ b/StdLib/Efi/StdLib/etc/resolv.conf
> @@ -1,13 +1,13 @@
> #
> # Domain name
> #
> -domain intel.com
> +domain example.com
>
> ;
> ; Name Servers
> ;
> -nameserver 206.63.63.61
> -nameserver 216.251.100.1
> +nameserver 8.8.8.8
> +nameserver 8.8.4.4
>
> ; nameserver 10.248.2.1
> ; nameserver 10.22.224.204
>
Thanks! Looks good. We should push this soon, after the
edk2-stable201903 tag is made. Jaben, please let me know if you need me
to push this.
Thanks
Laszlo
next prev parent reply other threads:[~2019-03-08 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-08 2:14 [PATCH] StdLib: Update resolv.conf to use Google's DNS servers Rebecca Cran
2019-03-08 9:26 ` Laszlo Ersek [this message]
2019-03-08 20:17 ` Laszlo Ersek
-- strict thread matches above, loose matches on Subject: below --
2019-02-23 3:38 [PATCH] " Rebecca Cran
2019-02-23 3:41 ` [PATCH] StdLib: " Rebecca Cran
2019-02-25 10:11 ` Laszlo Ersek
2019-02-25 14:40 ` Rebecca Cran
2019-02-25 15:56 ` Carsey, Jaben
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-list 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=f428975a-88c9-58c2-a6fe-44e32a897b5b@redhat.com \
--to=devel@edk2.groups.io \
/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