My Leopard Server DNS had been working fine... hosting 7 domains with
numerous hosts each, in some cases. Haven't made any changes in at
least
over a week. The TTL's were set to 3 hours.
Now there are cases where a user can get to one site but can't resolve
another. Another user can't get to the first, but can get to the
second.
Can't make heads or tails out of it.
I used dnsstuff.com and it was able to successfully test the site.
The two major domains in question are dsop.com and pennsyrr.com, if
anyone
cars to troubleshoot.
I've also noted, all along, that Leopard Server doesn't seem to
provide
SOA records. Can anyone comment on this?
I have not seen that at all yet - the SOA issue. What I /have/ seen is
that if you're not careful,
it puts the SOA as "example.com" and even if you remove any reference
to "example.com" in the GUI, it will *LEAVE* that entry in the zone
files,
and then throw an error about it in the log when you (try to) start up
DNS.
Don't trust the GUI is my advice, check the resultant files /private/
var/named/zones/db.*.zone.apple
The GUI for DNS in 10.5 server is one step forward, two steps back.
Nice effort, but buggy to the point of botching the config from the
get-go.
_______________________________________________
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
