Hi Mary, you are right. People have been suffering from this issue since nwam phase 0 was integrated. Please see following bug for details:
125 /etc/nsswitch.conf (and /etc/resolv.conf) aren't always updated for DNS http://defect.opensolaris.org/bz/show_bug.cgi?id=125 Hopefully, the user experience is going to change soon, since nwam 0.5 will be available in build 100: 2683 Phase 0.5 of nwam Integration. http://defect.opensolaris.org/bz/show_bug.cgi?id=2683 If you are interested, please see following pages for details: http://www.opensolaris.org/os/project/nwam/picea/ Also, this is the reasons, we are not going to take advantage of nwam in AI image for now. Thank you, Jan mary ding wrote: > Dave and Jan: > > BTW, this is what I had noticed too when I try to setup the first AI > server with opensolaris 99. Even after install, nwam is enabled but I > still cannot get dns service to come up because /etc/resolv.conf is > not populated. I had to switch from nwam to network:physical, run > sysunconfig and then answer the questions and setup dns with the right > data. Then it works. > > > > jan damborsky wrote: >> Dave Miner wrote: >>> jan damborsky wrote: >>>> Hi Dave, >>>> >>>> >>>> Dave Miner wrote: >>>>> jan damborsky wrote: >>>>>> Hi, >>>>>> >>>>>> when testing latest AI images, I have realized >>>>>> that we currently don't have any naming services >>>>>> functional in AI image. >>>>>> >>>>>> As far as user perspective is concerned, at least >>>>>> one visible impact is that AI installer can't >>>>>> successfully process AI manifest, if the >>>>>> address of IPS repository is not passed in >>>>>> the form of raw IP. >>>>>> >>>>>> Based on this, it seems that we should have >>>>>> some naming service running in AI image. I was >>>>>> thinking about DNS, but not sure if this is >>>>>> the approach we want to follow. >>>>>> >>>>>> Please let me know what you think. >>>>>> Comments and suggestions are highly appreciated. >>>>>> >>>>> You should have mdns, nsswitch.conf just needs to be set to use >>>>> it. I'd expect that DNS should be automatically configured during >>>>> boot if a server list is provided by DHCP. >>>> It seems we have DNS enabled, but it is in 'offline' state, because >>>> /etc/resolv.conf is not being populated even if DHCP server provides >>>> information about DNS servers ('dhcpinfo DNSserv' returns correct >>>> values). >>>> Looking at the code, /lib/svc/method/net-svc populates >>>> /etc/resolv.conf >>>> in case 'nwam' is not enabled. >>>> I have realized that 'nwam' instance of svc:/network/physical >>>> service currently >>>> takes care of network configuration in AI, 'default' is disabled. >>>> I think that we could switch to 'default' instead of 'nwam', since >>>> we won't be taking advantage of nwam features and it seems 'default' >>>> should take care of configuring DNS. >>>> Do you think it might be the good approach to follow ? >>>> >>> Yes, AI and NWAM really aren't compatible at this stage, I would >>> expect. >> >> ok. I will switch from 'nwam' to 'default' and will >> investigate from that point. I have filed following bug >> for tracking this: >> 4021 Naming services are not available in AI environment >> >> Thanks a lot for your help, >> Jan >> >> _______________________________________________ >> caiman-discuss mailing list >> caiman-discuss at opensolaris.org >> http://mail.opensolaris.org/mailman/listinfo/caiman-discuss >
