https://bugzilla.novell.com/show_bug.cgi?id=388266
User mt@novell.com added comment
https://bugzilla.novell.com/show_bug.cgi?id=388266#c39
--- Comment #39 from Marius Tomaschewski
Ok, so what this means is that suse system configured by yast and static IP does not support:
* DHCP - I doubt your ISP allows DNS queries from a random wifi hotspot you'd like to use your laptop. * Dialup - Same reason as above. * VPN - Many corporate environments (including novell) use their own internal DNS servers that are not public and the host names won't resolve without them.
No. It is a very common mistake people make, thinking that they order of the nameservers in resolv.conf solves this problem. On linux (at least), there is _no_ way to direct local network queries to a local nameserver VPN queries to another one and ISP queries to ISP nameserver just by adding the nameservers to resolv.conf only. Also when you define 3 nameservers (vpn, local, isp) in /etc/resolv.conf, only one (first) at time is used by the resolver, except the request times out where then the resolver trys the next one. There is no "NXDOMAIN" fallback or something like this. See also "man resolv.conf": "[...] If there are multiple servers, the resolver library queries them in the order listed. [...] (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.) [...] If no nameserver entries are present, the default is to use the name server on the local machine. [...]" Solution for this, is to not to define any nameserver (or only a local one) in /etc/resolv.conf, but to install a local nameserver (bind or dnsmasq) and define forward zones there - bind example: options { forward first; # ask isp first, then try root ns include "/etc/named.d/forwarders.conf"; ### forwarders.conf content is like: # forwarders { isp.isp.isp.isp; }; }; zone "lan.example.com" in { type forward; forward only; # ask only lan ns forwarders { lan.lan.lan.lan; }; }; #zone "<lan-network>.in-addr.arpa" in { ... }; # lan reverse zone "vpn.example.com" in { type forward; forward only; # ask only vpn ns forwarders { vpn.vpn.vpn.vpn; }; }; #zone "<vpn-network>.in-addr.arpa" in { ... }; # vpn reverse On 11.0 there is the MODIFY_NAMED_CONF_DYNAMICALLY on 11.1 the NETCONFIG_DNS_FORWARDER="bind" that should help to update the ISP nameserver to configure a scenario like this. -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.