[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [Testbed-admins] Errors booting admin mfs

pc1 can resolve (via ping) boss and boss.atcorp.emulab.priv
boss (via ping, host, or nslookup) can resolve pc1 and pc1.emulab.atcorp.priv
Interestingly, pc1 doesn't seem to be able to resolve itself, however. If I try "ping pc1.emulab.atcorp.priv" on pc1, it comes back with "Can't resolve pc1.emulab.atcorp.priv: unknown host." 

Shouldn't that work? Boss can certainly resolve itself.

On 6/3/2010 11:45 AM, Leigh Stoller wrote:

DHCP seems to be working fine. The right ip address got assigned to
the right mac address on pc1 and shows up in the dhcp log. (I
presume you wanted me to also look in /usr/local/etc/dhcpd.conf and
yes, the right mac address is there too.)

I can ping boss from pc1 and pc1 from boss and the ip addresses are
as expected.

It bothers me that the hostname on pc1 is "...foo.net". Is that to
be expected.


That is a side effect. We have to solve:


GetHostByName(UNKNOWN) failed
TMCC exited with status 256!


Okay, the next thing to look at is DNS, since that is how tmcc
determines who the boss actually is.

What is in pc1:/etc/resolv.conf? Can you resolve names on pc1?
Does boss.your.domain resolve?

Lbs