On 03/10/2008 13:34 PM, "David Stodolsky"
<email@hidden> wrote:
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.
Is there a specific problem here, with perhaps specific
informational items,
or just Apple didn't read your mind.
Silent failure of the Standard Install and later the VPN doesn't turn
on as was requested during the Install.
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.
I dunno. DNS outages generate some very specific errors in my
experience.
Sure:
Jan 10 10:33:05 WI named1020: /etc/dns/publicView.conf.apple:1:
undefined ACL 'example.com'
Doesn't matter, if you could spot this as being a DNS problem, as
opposed to a disk problem. Reinstalling was the only way out.
According to Support, Open Directory is populated with crap during a
Standard Install, if the DNS name is off. And even if that could be
fixed, it would still take a lot of time on the command line to fix
the DNS and make sure everything else was right.
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"?
Why would you have to change the IP address immediately after the
install?
changeip -checkhostname
What I want to know is why did "host" and this give an all clear and
then a lookup from a client showed a faulty nameserver entry. It was
still "ns" even though that had been replaced in Server Admin.
That's a fairly abnormal situation, and reeks of really bad preinstall
planning. That's one of the reasons Apple provides a worksheet, so
that you
can have various bits of information, like the correct IP address in
front
of you. Can you say "You're leaving out quite a few pertinent details
there"?
Note that I am just trying to duplicate a 10.2 configuration that has
been running fine for years.
Please reread qualifications in order to avoid foot-in-mouth disease;-)
dss
David Stodolsky email@hidden Skype: davidstodolsky
