On Mar 10, 2008, at 12:01 PM, David Stodolsky wrote:
I said, "needs a DNS, and a good one, *already running*". If you
read my earlier posts, and followed the links, you would see that
this is a widespread problem. The documentation is not clear on
this point, that the DNS can't be fixed after the install, except
the Expert Install.
Except the above is patently false.
You do need DNS, yes, but DNS can be offered -- in part -- from the
server you're running. However since DNS has /always/ required two
name servers for any zone (not an Apple requirement but an RFC /
InterNIC requirement) you will always have another DNS server.
Since this DNS is resolving only a 10.* network, upon which it is the
only server, that requirement is irrelevant. And supplying a local
(10.2 or 10.3) DNS led to no visible improvement with my Standard
Install.
And yes, you can fix this after the install, it's just not as
magically easy.
Since DNS config. is the first item on the agenda, it is easier to do
an Erase and Install, in practice. Seeing as the error messages tend
to be opaque, even determining what is wrong would likely take longer
than starting over. So, you have a theoretical point, but in practice
it doesn't apply.
Yesterday, I tried again to start an Advanced Configuration, with
point and click instructions in front of me. A single error meant I
had to do an Erase and Install. But this was only after the Server
Admin DNS tool "fixed" the error, and "host" and "changeip" on the
command line confirmed all was well. Can you say, "Human interface
from Hell"?
dss
David Stodolsky email@hidden Skype: davidstodolsky
