Manish, The problem is that I don't have a bullet proof test yet to determine if the networking parameters provided prior to zone creation will enable netidcfg to be able to talk to the specified name server. The problem is that if you don't get a working network config, netidcfg will require manual intervention via zlogin -C to accept the DNS configuration. I think what I will have to do is within zonemgr create the zone without specifying DNS params during zone creation and then create a properly configured nsswitch.conf and resolv.conf in the zone.
For now to work around this problem you can just copy the nsswitch.conf and resolv.conf files from the global zone into the non-global zones with the -C parameter. If anyone else has a better suggestion or other items that I should include in this new DNS setup methodology please share your thoughts. Thanks in advance, Brad On Mon, 2007-02-05 at 10:23 -0800, Manish Agrawal wrote: > I am trying to use the -D -d options in zonemgr to configure DNS during zone > creation. My command is: > > zonemgr -a add -n $zonename -z "/export/home/zones" \ > -P "$rootpassword" -R "/root|/usr/bin/bash" \ > -I "$ipaddress|elxl0|25|$zonename" \ > -s "basic|lock" -S ssh \ > -D "ismlab.usf.edu" -d "131.247.16.129 131.247.16.130 > 131.247.100.1" \ > -C /etc/ssh/sshd_config & > > The variables in the script above are: > $zonename:torresd > $ipaddress:131.247.16.173 > $rootpassword:4220Ism > > I am getting the following error: > Error: The default route doesn't match the subnet of the zone IP address. > This may cause the zone to hang on reboot if the zone cannot connect to the > DNS server. To resolve this you may need to login to the console with > "zlogin -C torresd" and complete the DNS configuration in the console. > > I then have to configure DNS manually in the zone. Relevant information is > provided below: > > -bash-3.00# cat /etc/defaultrouter > 131.247.16.254 > > -bash-3.00# netstat -r > > Routing Table: IPv4 > Destination Gateway Flags Ref Use Interface > -------------------- -------------------- ----- ----- ------ --------- > 131.247.16.128 unknown U 1 1239 elxl0 > BASE-ADDRESS.MCAST.NET unknown U 1 0 elxl0 > default vlan272.edu-msfc.net.usf.edu UG 1 6904 elxl0 > localhost localhost UH 71049585 lo0 > > Routing Table: IPv6 > Destination/Mask Gateway Flags Ref Use If > --------------------------- --------------------------- ----- --- ------ ----- > fe80::/10 fe80::2c0:4fff:fe60:d4b9 U 1 0 elxl0 > ff00::/8 fe80::2c0:4fff:fe60:d4b9 U 1 0 elxl0 > default fe80::2c0:4fff:fe60:d4b9 U 1 0 elxl0 > localhost localhost UH 10 359 lo0 > > The network configuration in the global zone is fine: > -bash-3.00# traceroute www.sun.com > traceroute to www.sun.com (72.5.124.61), 30 hops max, 40 byte packets > 1 vlan272.edu-msfc.net.usf.edu (131.247.16.254) 0.783 ms 0.631 ms 0.509 > ms > 2 wan-msfc.net.usf.edu (131.247.254.40) 0.625 ms 0.633 ms 0.734 ms > 3 g2-1.core01.tpa01.atlas.cogentco.com (38.101.48.173) 1.025 ms 1.063 ms > 1.018 ms > > -bash-3.00# ping www.gm.com > www.gm.com is alive > > The entire output during zone creation is: > -bash-3.00# learnscripts.sh 4220trial.info > :torresd: > :131.247.16.173: > :4220IsmSp0793: > Error: The default route doesn't match the subnet of the zone IP address. > This may cause the zone to hang on reboot if the zone cannot connect to the > DNS server. To resolve this you may need to login to the console with > "zlogin -C torresd" and complete the DNS configuration in the console. > Preparing to install zone <torresd>. > Creating list of files to copy from the global zone. > Copying <15282> files to the zone. > Initializing zone product registry. > Determining zone package initialization order. > Preparing to initialize <955> packages on the zone. > Initialized <955> packages on zone. > Zone <torresd> is initialized. > Installation of these packages generated warnings: <SUNWwgetu CSWcyrusimapd> > The file </export/home/zones/torresd/root/var/sadm/system/logs/install_log> > contains a log of the zone installation. > Creating the sysidcfg file for automated zone configuration. > Booting zone for the first time. > Waiting for first boot tasks to complete. > > First boot tasks do not complete even though the zone is up and running: > > -bash-3.00# zonemgr -a list > ID NAME STATUS PATH > 0 global running / > 29 torresd running /export/home/zones/torresd > > After logging into the zone (zlogin -C torresd) and initializing DNS > information, the above script completes, with the following output: > > Updating netmask information. > Updating /etc/inet/hosts of the global zone with the torresd IP information. > Zone torresd is ready. > Setting the root user's home directory to /root > Setting the root user's shell to /usr/bin/bash > Error: Invalid hardening argument for basic method. > Use -h flag to see proper usage or -l flag to see the license. > ./learnscripts.sh: line 27: -C: command not found > > I don't believe there is any problem in the defaultroute, because adding the > zone information in the script above (domain name, DNS servers) works: > > Hostname: torresd > > torresd console login: root > Password: > Feb 5 13:24:50 torresd login: ROOT LOGIN /dev/console > Sun Microsystems Inc. SunOS 5.10 Generic January 2005 > -bash-3.00# ping www.gm.com > www.gm.com is alive > -bash-3.00# ifconfig -a > lo0:1: flags=2001000849<UP,LOOPBACK,RUNNING,MULTICAST,IPv4,VIRTUAL> mtu 8232 > index 1 > inet 127.0.0.1 netmask ff000000 > elxl0:1: flags=1000843<UP,BROADCAST,RUNNING,MULTICAST,IPv4> mtu 1500 index 2 > inet 131.247.16.173 netmask ffffff80 broadcast 131.247.16.255 > > Help would be appreciated so that I can create one zone per student with > operational dns configuration. I can provide any additional information > required. > > Thanks > Manish > > > This message posted from opensolaris.org > _______________________________________________ > zones-discuss mailing list > zones-discuss@opensolaris.org _______________________________________________ zones-discuss mailing list zones-discuss@opensolaris.org
