Tivo domain name resolution

[AlphaWolf]

Is it just me or does /etc/resolv.conf never get populated?

Here's my attempt at fixing that by adding this to the init scripts:


#Force populate the nameserver list based on MFS (why doesn't tivoapp do this?)
rm /var/etc/resolv.conf
echo "search localdomain" >> /etc/resolv.conf
export NAMESERVERS=`mfs_dumpobj -r /State/Network | grep -i dnsservers | cut -d= -f2`
for server in $NAMESERVERS
do
echo "Adding nameserver $server"
echo "nameserver $server" >> /etc/resolv.conf
done


It looks like by default the init scripts will play with this in the debug board mode, but I am not certain what they are doing exactly. You'd figure that tivoapp would populate this after you enter your DNS values in the network configuration screen (or via netconfig.tcl.) But I've never seen anything happen to it. Has anybody ever seen this get populated? Or perhaps tivoapp does its own name resolution and therefore doesn't really care how the underlying linux environment is configured in this respect?

[Vasman]

/etc/resolv.conf is populated on my Directivo 6.2. It is picking up the local domain name (search) and three DNS servers (nameserver) from my DHCP server.

Hope this helps.

[Periwinkle]

Is it just me or does /etc/resolv.conf never get populated?


On my machine /etc/resolv.conf is a link to /var/etc/resolv.conf. (Since /etc is on a read-only partition, this redirection is clearly required.)

/var/etc/resolv.conf is getting updated -- I think by dhclient.

If you disabled dhcp, you probably also disabled the update mechanism for resolv.conf.

[AlphaWolf]

I've got the problem sorted out. Since I bring up telnet early in the init stage, it causes tivoapp to not touch the networking settings at all. It is fixable by running hotplug in the post init stages.