https://www.saruman.biz/saruwiki/api.php?action=feedcontributions&feedformat=atom&user=194.165.0.0%2F16 2026-07-23T15:06:40Z User contributions MediaWiki 1.46.0 https://www.saruman.biz/saruwiki/index.php?title=Networking_section&diff=1848 2008-10-22T09:54:15Z

<p>194.165.42.61: 0</p> <hr /> <div>10Ln2s &lt;a href=&quot;http://qagxoudlwsrg.com/&quot;&gt;qagxoudlwsrg&lt;/a&gt;, [url=http://hkohogbnntqz.com/]hkohogbnntqz[/url], [link=http://ajmoxspubzba.com/]ajmoxspubzba[/link], http://izdncmzymuhe.com/<br /> <br /> ==DNS resolution under Debian==<br /> One headache you might encounter when configuring a Debian server is how to let every program know how to resolve DNS names. Before a program can connect to an external network resource (say, for example, a web server), it must have a means of converting DNS names (e.g. www.saruman.biz) into the corresponding IP addresses (e.g. 192.168.67.10). This process is called &quot;name resolution&quot;. The need for name resolution means that every program needs to know about the available means by which to do this name resolution.<br /> <br /> From the good old days comes the configuration file ''resolv.conf'', normally found in ''/etc''. It contains information about the nameservers to be used by the system, be they actual servers or lookup files. However, more and more programs have the need to dynamically modify the ''resolv.conf'' configuration file. This means that frequently they step on each other, and the ''resolv.conf'' file can become out-of-sync. The ''resolvconf'' program addresses this problem. It acts as an intermediary between programs that supply nameserver information (e.g. DHCP clients) and programs that use nameserver information (e.g. resolver).<br /> <br /> When ''resolvconf'' is properly installed, the file ''/etc/resolv.conf'' is replaced by a symbolic link to ''/etc/resolvconf/run/resolv.conf'', and any resolver thus uses the dynamically generated resolver configuration file at ''/etc/resolvconf/run/resolv.conf''.<br /> <br /> The ''resolvconf'' program is only necessary when a system has multiple programs that need to dynamically modify the nameserver information. In a simple system where the nameservers do not change often or are only changed by one program, the standard ''/etc/resolv.conf'' configuration file is adequate.</div>

194.165.42.61