John,
I had a similar issue with my system at work.
What I did was to edit /etc/default/dhcpagent
and uncomment # CLIENT_ID= and add:
CLIENT_ID= [hostname expected on your work network]
My issue isn't with the DHCP server. In fact, if I get my setup from the
DHCP server, DNS works. It's just that the DNS it gives me is really bad
[1].
My issue is that if I take the DHCP server out of the equation and try
to setup my routes and netmasks and hosts manually, the resolver flatly
refuses to resolve.
I should have said that in this latter case -- the manually configured
case -- that this will work:
dig @an.appropriate.ip.of.a.DNS.server www.adam.com.au
DSL
[1] I may be able commandeer control of the DHCP server itself however
that would involve workplace politics :P
_______________________________________________
opensolaris-discuss mailing list
[email protected]
