Summary: yast dns vs. dns-server is poorly designed
Product: openSUSE 11.2
Priority: P5 - None
Found By: ---
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:18.104.22.168)
Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
From Bug 558333:
Marius Tomaschewski 2009-11-27 22:56:20 UTC
It sounds like you would like to use bind as forwarder
for your system, right?
There is a policy + 3 variables:
=> defines a rule who is allowed to provide settings
(servers and search list).
=> defines the dns domain search list
=> defines the (external) recursive dns servers / forwarder
=> "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
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,
This design is a mess. It confuses bind forwarders vs. the resolver. When you
install bind, it makes 127.0.0.1 a bind forwarder. This is wrong!
Start over with the design, consider the difference between bind forwarders vs.
the resolver, and simplify this sorry mess.
Steps to Reproduce:
Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are on the CC list for the bug.