Unfortunately I can't get it to work.
When I add
tkey-gssapi-credential "DNS/";
tkey-domain "...";
to my named.conf file, named doesn't want to start anymore. I get the
following message in /var/log/messages:
Dec 26 13:55:33 dns named[8546]: configuring TKEY: not implemented
Dec 26 13
On Wed, 24 Dec 2008 22:31:19 -0500, Robert Spangler wrote:
> On Wednesday 24 December 2008 20:13, Scott Haneda wrote:
>
>> Trying to help a client, they stumped me today.
>
> OK, I get the sam answers form all the NS servers.
>
>> dig crm.share-ideas.com
>>
>> ; <<>> DiG 9.4.2-P2 <<>> crm.sh
At Fri, 26 Dec 2008 14:28:13 +0100, Nico De Ranter wrote:
>
> Dec 26 13:55:33 dns named[8546]: configuring TKEY: not implemented
The error suggests that you don't really have GSSAPI enabled
(dst_gssapi_acquirecred() returns that error when called with GSSAPI
support disabled). Check your build l
Dmitry Rybin wrote:
Linux Addict wrote:
Folks, I have BIND 9 running. For some reason, the external resolution
is not working. I can telnet to root servers on port 53. Recursion is
on. What are the other requiremnts for the server to reesolve the
external records. Please help!!
TCP?
This is *exactly* why there is a rule in RFC 1034 prohibiting
the use of CNAME with anything else. This is also why named
enforces the rule. The operators of share-ideas.com are
in violation of this rule and their nameserver does not
enforce this rule.
I'm testing BIND 9.6 with dynamically updated zones.
I'm trying to figure out if I can maintain the zone entirely via
dynamic update, even including key rollover tasks.
Or is key rollover better performed outside the nameserver process,
eg. by freezing the zone, moving in new key files into th
6 matches
Mail list logo
