On Sat, Feb 07, 2009 at 05:31:24PM +, Richard Kettlewell wrote:
> Thomas Hood wrote:
>>> iface eth0 inet static
>>> address 172.17.207.12
>>> gateway 172.17.207.1
>>> netmask 255.255.255.0
>>
>>
>> I'll assume that interface eth0 is configured using the "ifup" command.
>>
>> Add this line to
Thomas Hood wrote:
iface eth0 inet static
address 172.17.207.12
gateway 172.17.207.1
netmask 255.255.255.0
I'll assume that interface eth0 is configured using the "ifup" command.
Add this line to the "iface eth0" stanza in /etc/network/interfaces
dns-nameservers 172.17.207.1 172.17.207
Thomas Hood wrote:
Through which network interface can those nameservers be reached? How
is that network interface configured?
eth0 and as below.
$ ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:16:3e:06:f3:14
inet addr:172.17.207.12 Bcast:172.17.207.255 Mask:255.255.255.0
Thomas Hood wrote:
We need to figure out why resolvconf is not functioning correctly on
your system.
Resolvconf writes the resolver configuration file on the basis of
information provided to it. If nothing provides it with nameserver
addresses then it writes an empty resolv.conf file.
What nam
Package: resolvconf
Version: 1.43
Severity: critical
This is from my unstable VM. I did not explicitly install resolvconf,
perhaps apt followed a 'recommends' or something. Essentially all
network operations after this stop working (hence 'Severity: critical')
as resolv.conf had been replace
5 matches
Mail list logo
