Juanita Heieck writes: > opensolaris console login: Dec 16 00:27:23 opensolaris mDNSResponder: > Unable to > parse DNS server list. Unicast DNS-SD unavailable
That sounds like a problem with svc:/network/dns/multicast:default. By searching in sunsolve, appears to be CR 6741196, and is caused by a lack of /etc/resolv.conf during an initial boot. I don't believe that it'll have any effect on your system, unless you're using the mDNS-based service discovery (Bonjour). Most importantly, it has nothing to do with "normal" DNS used for resolution of host names. > Dec 16 00:27:34 opensolaris in.routed[534]: route 0.0.0.0/8 --> 0.0.0.0 > nexthop > is not directly connected. I don't think that's a problem. That's most likely due to the reworking of the DHCP client implementation done by CR 4354207. The client now brings up the address with a zero address, and that confuses in.routed. It rights itself once the interface is established. (Feel free to file a bug, but I don't believe it actually will cause you any operational problems.) Neither of these messages describes a problem that seems related to the issue you're having. -- James Carlson, Solaris Networking <james.d.carlson at sun.com> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677
