Technical

• Download the latest version of bind from http://www.isc.org/downloads
• Create a folder on your desktop called bind and extract the downloaded zip to it.
• Open the newly created bind folder and right click on BINDInstall.exe and select "Run as administrator"
• In the Bind 9 Installer window enter:
  • Target Directory: c:\named
  • Service Account Name: named
  • Service Account Password: Enter a secure password to use for the service to use
  • Confirm Service Account Password:  Enter the password again
  • Ensure that Automatic Startup is selected
  • Ensure that Keep Config files after uninstall is selected.
• Click Install.
• When the installer reports "BIND Installation completed successfully", click OK.
• Click Exit to close the installer.

• Create a c:\named\zones folder
• Download named.conf and db.yourdomain.com.txtand save them to:
  • c:\named\etc\named.conf
  • c:\named\zones\db.yourdomain.com.txt
• Open a command prompt and run:

  cd c:\named\bin
  rndc-confgen -a
  rndc-confgen > ..\etc\rndc.conf

• Close the command prompt
• Open c:\named\etc\rndc.conf in notepad
• Cut to the clipboard the section belowthe line that says:

  # Use with the following in named.conf, adjusting the allow list as needed:

• Save & close rndc.conf
• Open c:\named\etc\named.conf in notepad
• Paste the contents of the clipboard into the bottom of this file
• Remove the hashes (#) from the beginning of the pasted lines.
• Remove the line that says "End of named.conf"
• Save & close named.conf

• Open c:\named\etc\named.conf in notepad.
• In the zone definition for yourdomain.com, modify the zone and file lines to reflect the domain you are configuring.
• Save and close named.conf
• Rename c:\named\zones\db.yourdomain.com.txt to reflect your previous change in named.conf
• Open this zone file in notepad.
• Substitute all references to yourdomain.com for the domain you are configuring.
• Substitute namesever-hostname for the hostname of your nameserver.
• Edit the last line so that the A record reflects the IP address of your server.
• Edit the serial line to reflect today's date. The format for this line is YYYYMMDDRR where:

  YYYY = The year (e.g. 2005)

  MM = The month (e.g. 02)

  DD = The day (e.g. 22)

  RR = Today's revision of this file (e.g. 01)

• Save and close the zone file.

• Start -> right click on "Computer" and select "Manage" -> Services and Applications -> Services
• Locate the "ISC Bind" service, right click on it and select start.
• If it fails to start, errors can be found in the Event Viewer.

• Create a text file called "reload bind.bat" on the desktop, with the following content

  @echo off
  c:\named\bin\rndc reload
  pause

Installing Solaris via JumpStart from a Linux server.

Thanks to Jon Still, Tim Gibbons, Scott Mann and Chris Cosby for helping me improve this document.

mkdir -p /home/jumpstart/install
mkdir /home/jumpstart/config

ln -s /bin/tar /bin/bar

ln -s /bin/sed /usr/bin/sed
ln -s /usr/bin/gdb /usr/bin/adb

echo "#!/bin/bash" > /bin/mach
echo "uname -p" >> /bin/mach
chmod +x /bin/mach  

Mount Solaris CD 1 / the Solaris DVD, and use the setup_install_server script. Then run the setup_install_server script.

mount /mnt/cdrom
cd /mnt/cdrom/Solaris_8/Tools
./setup_install_server /home/jumpstart/install
cd /
umount /mnt/cdrom

Replace the cd with cd 2 (if you don't have a cd 2, dont worry about it - skip to the next section). Even in Solaris 8 you can get away with just using cd1 if youre not going for one of the bigger installs. The add_to_install_server is written in ksh, so this is what you need pdksh for. It's odd that these scripts are completley different, and it seems this one uses cpio to copy the data. Weird eh? Anyway, most of it works ok apart from the disk space checking thing, so set and export $NOSPACECHK before you run it. I'm sure you can cope with checking how much space you have free.

mount /mnt/cdrom
cd /mnt/cdrom/Solaris_8/Tools
NOSPACECHK="yes"; export NOSPACECHK
./add_to_install_server /home/jumpstart/install

Set up the NFS server

If you've not already done so, install rarpd, bootparamd and tftpd. I'm assuming you're using the kernel nfsd here.

Set up the NFS export. Put the follwing in /etc/exports, but use appropriate values for your site. The config export is optional, depending on wether you want to use non-interactive jumpstart or not.

/home/jumpstart/install		192.168.1.0/24(ro,no_root_squash,async,no_subtree_check)
/home/jumpstart/config		192.168.1.0/24(ro,no_root_squash,async,no_subtree_check)

For newer versions of the linux nfsd, nfsv4 may well be enabled by default. It's probably easier to disable it - add " --no-nfs-version 4" to the nfsd parameters, however your Linux distribution chooses to do that.

Set up the server for the client

This is where it gets a little fiddly, for each install client you need an entry in /etc/hosts, /etc/ethers and /etc/bootparams and a symlink to the appropriate kernel in /tftpboot

/etc/hosts

This one is easy, you need the hostname and its IP address. Put it in /etc/hosts in the following format:

192.168.1.4	jumpstartclient

Also, ensure that your server's hostname is *not* listed against 127.0.0.1. If it is, remove it from that line and give it its own line, so your hosts file looks like this (where jumpstartserver is your server).

127.0.0.1		localhost.localdomain localhost
192.168.1.1		jumpstartserver
192.168.1.4		jumpstartclient

/etc/ethers

This is so that rarpd can respond to the client's request for an IP address. It does this by resolving it's MAC address to a hostname, and uses /etc/hosts to turn that in to an IP. In /etc/ethers:

8:0:20:7a:a3:f2	jumpstartclient

/etc/bootparams

This is the config so the client knows where to access the install image and configurations. In /etc/bootparams, where jumpstartserver is my jumpstart server:

jumpstartclient  root=jumpstartserver:/home/jumpstart/install/Solaris_8/Tools/Boot \
	        install=jumpstartserver:/home/jumpstart/install  \
       		boottype=jumpstartserver:in \

		sysid_config=jumpstartserver:/home/jumpstart/install/Solaris_8/Tools/Boot/etc \
       		install_config=jumpstartserver:/home/jumpstart/config \
       		rootopts=jumpstartserver:rsize=8192,wsize=8192

/tftpboot

This is the really fiddly bit. Either you calculate the client's IP address in hex format, or you use tcpdump to determine what it's requesting.

This is becase the client will request an inetboot file from the tftp server. It will be named in the format HEXIPADDR.ARCH or just HEXIPADDR (some machines do not request the .ARCH part of the filename). In my case, it is C0A80104.SUN4U. So if, like me you don't fancy calculating this name, start the bootparamd and the rarpd (you may need to start the rarpd with -e as some versions will not respond to rarp queries if there is not a corresponding image in /tftpboot to serve.

According to Jon,

perl -e 'printf "%02x"x4 ."\n",192,168,1,4;'|tr a-z A-Z

will give you the hex address (where the IP is 192.168.1.4).

Similarly, you can do it in shell like this:

printf %02x 192 168 1 4|tr [:lower:] [:upper:]

Once your services are started, get tcpdump on the go (this is best done on a quiet or switched network, and boot net - install your client. tcpdump should produce a line like this:

08:59:24.640821 jumpstartclient.40337 > jumpstartserver.beau.net.tftp:  23 RRQ "C0A80104.SUN4U"

Alternativley, running bootparamd with -d and -s flags should write the filename being requested to the syslog

Once you have this filename, you can copy the appropriate inetboot image from your /home/jumpstart/install hierachy. The example below is appropriate for a sun4m architecture machine, modify it for other systems

cp /home/jumpstart/install/Solaris_8/Tools/Boot/usr/platform/sun4m/lib/fs/nfs/inetboot /tftpboot/inetboot.sun4u

cd /tftpboot
ln -s inetboot.sun4u C0A80104.SUN4U

ln -s inetboot.sun4u C0A80104

Enable your tftpd and you should be ready to go!

Jumpstart the client

Stop-A the client and get it to the openboot prompt. From there type either:

boot net - install 

(for a non-interactive install)

or

boot net - text

(for an interactive install)

IMPORTANT. One problem I have had with this is that when it boots, after it configured the network interface (a message like "Configured interface le0" is displayed), the client just sits there. Sending the client a ping should wake it up and it will continue fine. Weird eh?