Netdev List
 help / color / mirror / Atom feed
From: Dan Williams <dcbw@redhat.com>
To: Ravi Aysola <ravi.mlists@gmail.com>
Cc: netdev@vger.kernel.org
Subject: Re: network namespace and DNS lookups
Date: Tue, 18 Dec 2012 11:22:59 -0600	[thread overview]
Message-ID: <1355851379.30992.12.camel@dcbw.foobar.com> (raw)
In-Reply-To: <CAFaHj6HT0c59us_7F9Uh7BYh_YXGRt30=yLOrV=hcrG29YO-qA@mail.gmail.com>

On Tue, 2012-12-18 at 10:49 -0500, Ravi Aysola wrote:
> I think I sent my earlier email a bit prematurely.  I do have
> /etc/netns/<namespace-name>/resolv.conf
> files under each of my namespaces. Now the question is, how does a
> user space process
> (say bind)  look at a namespace specific resolv.conf instead of
> default one?  Have any of
> these standard applications been modified to work with namespace
> specific config files?

Wouldn't that be the glibc resolver's domain?  DNS lookups aren't done
by the kernel, but by glibc in userspace.  And glibc is also what reads
resolv.conf, so most things DNS-namespace related would need to happen
there.

Dan

> thanks again
> ravi/
> 
> On Tue, Dec 18, 2012 at 10:09 AM, Ravi Aysola <ravi.mlists@gmail.com> wrote:
> > Has there been any work in any of the recent kernels to limit the DNS lookup
> > to a particular network namespace?  Do we have any facility to specify the
> > DNS resolvers on network namespace basis (such as /etc/ns/resolv.conf)?
> >
> > thank you
> > ravi/
> --
> To unsubscribe from this list: send the line "unsubscribe netdev" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html

      reply	other threads:[~2012-12-18 17:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-18 15:09 network namespace and DNS lookups Ravi Aysola
2012-12-18 15:49 ` Ravi Aysola
2012-12-18 17:22   ` Dan Williams [this message]

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=1355851379.30992.12.camel@dcbw.foobar.com \
    --to=dcbw@redhat.com \
    --cc=netdev@vger.kernel.org \
    --cc=ravi.mlists@gmail.com \
    /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