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.
>
>
>>
>>
>> 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.
I dunno. DNS outages generate some very specific errors in my experience.
Usually the server starts throwing errors like:
Mar 7 03:16:29 xserve01 servermgrd: servermgr_dns: no name available via
DNS for <IP address>
Mar 7 03:16:29 xserve01 servermgrd: servermgr_dns: no reverse DNS entry for
server, various services may not function properly
Along with tons of :
Mar 7 03:24:02 xserve01 mDNSResponder: mDNSPlatformSendUDP sendto failed to
send packet on InterfaceID 01814400 en0/4 to 224.0.0.251:5353 skt 9 error
-1 errno 65 (No route to host) 416862123
When I see those together, I know DNS is having a bad day. The true cause of
that can be varied, but the log entries are hardly "opaque". What they are
*not* is aimed at someone with no knowledge whatsoever.
>
> 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?
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"?
--
John C. Welch Writer/Analyst
Bynkii.com Mac and other opinions
email@hidden
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Macos-x-server mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/macos-x-server/email@hidden
This email sent to email@hidden
