quot;su –l root" in salt?
Thank you for any insight,
Dan
*From: *Dan Dietterich
*Date: *Wednesday, April 19, 2017 at 9:24 AM
*To: *Martin Bašti , "freeipa-users@redhat.com"
*Subject: *Re: [Freeipa-users] DNSSEC warning when DNSSEC should be
disabled
*From: *Martin Bašti
*Date
r any insight,
Dan
From: Dan Dietterich
Date: Wednesday, April 19, 2017 at 9:24 AM
To: Martin Bašti , "freeipa-users@redhat.com"
Subject: Re: [Freeipa-users] DNSSEC warning when DNSSEC should be disabled
From: Martin Bašti
Date: Wednesday, April 19, 2017 at 9:23 AM
To: Dan Dietterich ,
Date: *Wednesday, April 19, 2017 at 3:59 AM
*To: *Dan Dietterich , "freeipa-users@redhat.com"
*Subject: *Re: [Freeipa-users] DNSSEC warning when DNSSEC should be
disabled
On 13.04.2017 22:50, Dan Dietterich wrote:
I am seeing inconsistent results configuring a DNS forward zone
e: [Freeipa-users] DNSSEC warning when DNSSEC should be disabled
On 13.04.2017 22:50, Dan Dietterich wrote:
I am seeing inconsistent results configuring a DNS forward zone.
At a bash prompt, as root, after kinit admin, I do:
ipa dnsforwardzone-add domain.internal --forwarder= ww.xx.yy.zz
--
On 13.04.2017 22:50, Dan Dietterich wrote:
I am seeing inconsistent results configuring a DNS forward zone.
At a bash prompt, as root, after kinit admin, I do:
ipa dnsforwardzone-add domain.internal --forwarder= ww.xx.yy.zz
--forward-policy=only
That works fine and does not warn about DN
I am seeing inconsistent results configuring a DNS forward zone.
At a bash prompt, as root, after kinit admin, I do:
ipa dnsforwardzone-add domain.internal --forwarder= ww.xx.yy.zz
--forward-policy=only
That works fine and does not warn about DNSSEC.
In a Java webapp running as root under a Je
