Ignore /etc/resolv.conf; it's not really used by the system. Look at System
Preferences / Network / / Advanced / DNS, instead.
Regards,
Chris Buxton
BlueCat Networks
On Dec 10, 2010, at 9:02 AM, Banana Flex wrote:
> hello list,
>
> Our setup:
>
> - a MAN network with thousand of Mac computer
hello list,
Our setup:
- a MAN network with thousand of Mac computers running Mac OS X 10.4, 10.5 and
10.6
- two linux servers running dhcp-3.1.3ESV and bind-9.5.0P2, redundant as a
cooperation, this is the main DHCP/DNS servers for the MAN
- a multitude of servers running Mac OS X Server (10.4
> Date: Fri, 10 Dec 2010 10:17:57 -0600
> From: Martin McCormick
> Sender: bind-users-bounces+oberman=es@lists.isc.org
>
> On my test box, I am not seeing any errors so I think we are
> signing the test zone. The dnssec part of named.conf options
> looks like:
>
> dnssec-enable yes;
> dnssec
On 12/10/2010 11:17 AM, Martin McCormick wrote:
> Is there, somewhere, a linear description of this
> process that starts out like:
>
> 1. Do this.
>
> and leading up to
>
> x. Congratulations! you have dnssec working.
>
> None of these steps in the puzzle have been hard, so far, but
>
On my test box, I am not seeing any errors so I think we are
signing the test zone. The dnssec part of named.conf options
looks like:
dnssec-enable yes;
dnssec-validation yes;
dnssec-lookaside auto;
managed-keys-directory "/etc/namedb/working";
In the actual zone, I have:
zone
Hello,
thanx to all that helped me. Problem solved.
The main reason was this posted by phil
1. Ensure there is a prinicpal in your kerberos realm "DNS/
hostname.domain.com", matching the hostname of your DNS server
This is why I always got a wrong principal name.
Have a nice weekend,
cheers,
6 matches
Mail list logo
