About this list Date view Thread view Subject view Author view Attachment view

From: Jacques Gelinas (jack_at_solucorp.qc.ca)
Date: Thu 08 Aug 2002 - 21:16:12 BST

On Thu, 8 Aug 2002 09:55:48 -0500, Johnny Carlsen wrote
> On Wed, 07 Aug 2002 20:02:35 +0000
> "Lyn St George" <lyn_at_zolotek.net> wrote:

> Q: Having problems with dns resolving (nameservers) in your vserver?
> A: Remove the S_DOMAINNAME from you config file - not sure why, but it
> works ;)

S_DOMAINNAME is related to NIS. Most server do not use NIS. It is generally
used to share user entries.

Now if you specify S_DOMAINNAME, you are setting the NIS domain and
NIS is also used (but less and less) to resolve name like the DNS. In fact, if you
look at the file /etc/nsswitch.conf, you will find a line like

hosts: files nisplus nis dns

This tells the resolver (a part of glibc doing name to IP resolution) to first look
in /etc/hosts (files), then check the NIS+ server (using the NIS domainname)
and the old NIS server (using S_DOMAINNAME again) and finally, use the DNS.

Since you do not have any NIS server on your network, NIS request will fail
potentially with some timeout. If you are patient enough, you will see DNS
resolution work.

So removing (S_DOMAINMAME=nothing) the NIS domain name should
fix the issue.

Oddly, the NIS domainname (set by the domainname command) is totally
unrelated to DNS domain name. For some reason, this goes in the kernel
while the DNS preferred domain name goes in /etc/resolv.conf and not
the kernel at all.

Jacques Gelinas <jack_at_solucorp.qc.ca>
vserver: run general purpose virtual servers on one box, full speed!

About this list Date view Thread view Subject view Author view Attachment view
[Next/Previous Months] [Main vserver Project Homepage] [Howto Subscribe/Unsubscribe] [Paul Sladen's vserver stuff]
Generated on Wed 06 Nov 2002 - 07:03:42 GMT by hypermail 2.1.3