medibuntu

[Matthew Flaschen]

Pastor JW wrote:
>> Are you sure all the machines all have the same DNS settings (do you
>> know how they're getting assigned DNS servers?)?  Can you post
>> /etc/resolv.conf from a machine on the LAN that works and one that doesn't?
> 
> ### BEGIN INFO
> #
> # Modified_by:  NetworkManager
> # Process:      /usr/bin/NetworkManager
> # Process_id:   5459
> #
> ### END INFO
> 
> search domain.actdsltmp
> 
> 
> nameserver 192.168.0.1
> nameserver 216.229.160.10
> 
> and from the one which does:
> 
> #Dynamic resolve.conf(5) file for glibc resolver(3) generated by resolvconf(8)
> #	DO NOT EDIT THIS FILE BY HAND -- yOUR CHANGES WILL BE OVERWRITTEN
> nameserver 192.168.2.1
> search Belkin

Okay, as you can see the DNS settings are not the same.  The DNS server
on 192.168.2.1 appears to be resolving medibuntu.org correctly.  My
guess is that 192.168.0.1 doesn't work, and the non-working machine is
using 216.229.160.10 which is not resolving medibuntu.org correctly.

A possible solution would be manually setting the DNS on the non-working
machine to 192.168.2.1, presuming that that all the machines are really
on the same subnet.  I think a good way to do this is by disabling
NetworkManager (usually a good choice in general), installing the
resolvconf package using your regular package manager, then adding:

nameserver 192.168.2.1

to the end of:

/etc/resolvconf/resolv.conf.d/head

Make sure you put a line break after.

Then do,

sudo /etc/init.d/networking restart

This doesn't completely address why they have different DNS to begin
with, though.  Let me know how it goes.

Matt Flaschen