Bug 558333 - By Yast isn't impossible insert differren IP address for nameserver and forwarder
Summary: By Yast isn't impossible insert differren IP address for nameserver and forwa...
Status: RESOLVED DUPLICATE of bug 473308
: 558231 (view as bug list)
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: YaST2 (show other bugs)
Version: Final
Hardware: i686 openSUSE 11.2
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Petr Baudis
QA Contact: Jiri Srain
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-11-25 12:14 UTC by Petr Matula
Modified: 2009-12-16 08:04 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Petr Matula 2009-11-25 12:14:03 UTC
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; cs-CZ; rv:1.9.1.4) Gecko/20091016 SUSE/3.5.4-1.1.2 Firefox/3.5.4

After instalation bind.

By Yast isn't impossible insert differren IP address for nameserver and forwarder.

When I inserted dns server ip address by yast, yast automaticly change bind forwarder ip address bind forwarder to the same value.

I want to setup different ip address for nameserver and forwarder.

Reproducible: Always
Comment 1 Petr Matula 2009-11-25 12:17:09 UTC
By Yast is impossible insert differren IP address for nameserver and
forwarder.

When I inserted dns server ip address by yast, yast automaticly change bind
forwarder ip address bind forwarder to the same value.

I want to setup different ip address for nameserver and forwarder.
Comment 2 Lukas Ocilka 2009-11-26 11:48:46 UTC
It's actually a feature, try changing
YaST DNS Server -> Forwarders -> Netconfig DNS Policy
(NETCONFIG_DNS_POLICY entry)
according to `man netconfig`
Comment 3 Petr Matula 2009-11-26 12:30:27 UTC
I tried changing Netconfig DNS Policy to static or auto.When I inserted forwarder ip address by yast, yast automaticly change
nameserver ip address to the same value.

When I disabled Netconfig DNS Policy, i can edit config file /etc/resolve.conf and setup different nameserver ip address.
Comment 4 Marius Tomaschewski 2009-11-27 22:56:20 UTC
Can you describe what you want to do exactly? What do you expect
as result?

It sounds like you would like to use bind as forwarder nameserver
for your system, right?

There is a policy + 3 variables:

NETCONFIG_DNS_POLICY="auto"
 => defines a rule who is allowed to provide settings
    (servers and search list).

NETCONFIG_DNS_STATIC_SERVERS=""
 => defines the dns domain search list

NETCONFIG_DNS_STATIC_SEARCHLIST=""
 => defines the (external) recursive dns servers / forwarder

NETCONFIG_DNS_FORWARDER="resolver"

 => "resolver", "bind", "dnsmasq"

  resolver: writes servers and search list to resolv.conf
  bind:     writes servers to bind's forwarders.conf and
            search list to resolv.conf
  dnsmasq:  writes servers to dnsmasq-forwarders.conf and
            search list to resolv.conf

This means: for ="bind", the nameserver IPs you enter in YaST2,
will be written (by "netconfig update") to the forwarders.conf,
so bind is using them as forwarders.

  ! There are no nameserver entries in resolv.conf then !

They are not needed -- glibc will automatically use the name
server on the local machine, that is, it will use bind.
And bind will use the configured forwarders.

See also "man 5 resolv.conf" and "man 8 netconfig".

In case there is no name server running on the local machine,
just use
   NETCONFIG_DNS_FORWARDER="resolver"
Comment 5 Marius Tomaschewski 2009-11-27 23:07:33 UTC
*** Bug 558231 has been marked as a duplicate of this bug. ***
Comment 6 Petr Matula 2009-11-28 14:22:10 UTC
I've got installed bind and NETCONFIG_DNS_FORWARDER="bind" and glibc don't use the name server on the local machine.

I had to insert "nameserver 127.0.0.1" to resolv.conf
Comment 7 Marius Tomaschewski 2009-12-04 13:10:55 UTC
OK,
thanks -- it is a glibc bug - see resolv.conf(5) manual page:
"[...]
       nameserver Name server IP address
              Internet  address  (in  dot  notation) of a name server that the
              resolver  should  query.   Up  to  MAXNS   (currently   3,   see
              <resolv.h>)  name  servers  may  be listed, one per keyword.  If
              there are multiple servers, the resolver library queries them in
              the  order  listed.   If  no nameserver entries are present, the
              default is to use the name server on the  local  machine.   (The
              algorithm  used  is to try a name server, and if the query times
              out, try the next, until out of name servers, then repeat trying
              all  the  name  servers  until  a  maximum number of retries are
              made.)
[...]"

See also https://bugzilla.novell.com/show_bug.cgi?id=549447#c5, it looks like
I forgot, that the problem is back :-/

Reassigning to the glibc maintainer.
Comment 8 Marius Tomaschewski 2009-12-16 08:04:55 UTC
AFAIS this is a dup of bug 473308.

*** This bug has been marked as a duplicate of bug 473308 ***