Re: F21 System Wide Change: Default Local DNS Resolver
[Posted May 21, 2014 by n8willis]
| From: |
| Chuck Anderson <cra-AT-WPI.EDU> |
| To: |
| devel-AT-lists.fedoraproject.org |
| Subject: |
| Re: F21 System Wide Change: Default Local DNS Resolver |
| Date: |
| Tue, 29 Apr 2014 11:18:14 -0400 |
| Message-ID: |
| <20140429151813.GC16334@angus.ind.WPI.EDU> |
| Archive‑link: | |
Article |
On Tue, Apr 29, 2014 at 05:15:57PM +0200, Alexander Larsson wrote:
> On tis, 2014-04-29 at 14:15 +0200, Jaroslav Reznik wrote:
> > = Proposed System Wide Change: Default Local DNS Resolver =
> > https://fedoraproject.org/wiki/Changes/Default_Local_DNS_...
> >
> > Change owner(s): P J P <pjp@fedoraproject.org>, Pavel Šimerda
> > <pavlix@pavlix.net>, Tomas Hozza <thozza@redhat.com>
> >
> > To install a local DNS resolver trusted for the DNSSEC validation running on
> > 127.0.0.1:53. This must be the only name server entry in /etc/resolv.conf.
>
> This is gonna conflict a bit with docker, and other users of network
> namespaces, like systemd-nspawn. When docker runs, it picks up the
> current /etc/resolv.conf and puts it in the container, but the container
> itself runs in a network namespace, so it gets its own loopback device.
> This will mean 127.0.0.1:53 points to the container itself, not the
> host, so dns resolving in the container will not work.
>
> Not sure how to fix something like that though...
Is it possible to use a different loopback device like 127.0.0.53 and
then have that point outside the container somehow?
--
devel mailing list
devel@lists.fedoraproject.org
https://admin.fedoraproject.org/mailman/listinfo/devel
Fedora Code of Conduct: http://fedoraproject.org/code-of-conduct