Will doJust not sure it was that or not but I will make sure to do so
if I can 100% say for sure.
Thanks!
On Thu, Oct 1, 2015 at 2:42 PM, Jan-Piet Mens wrote:
> > Ironically the Ansible python module that I was using was your's! :)
>
> Please report bugs on the Github issue-tracker for the
> Ironically the Ansible python module that I was using was your's! :)
Please report bugs on the Github issue-tracker for the module, if and
when you find them.
-JP
___
Pdns-users mailing list
Pdns-users@mailman.powerdns.com
http://mailman.powe
Hi All,
I' ve just joined this forum because I'm trying someone that can help me to
use my DNS server cache resolver. It is part of a my project developed this
summer.
Is a Debian server that run PowerDNS and is protected by a Cisco ASA
Firewall.
As al DNS cache resolver in the world (ie. 8.8.8.8
Thanks Ken,
It appears that the mystery has been solved. Apparently when I used Ansible
to create the zones the issue presents itself..SOA? But when manually
entering the zones using NSEDIT all seems to start working immediately.
Very strange.
And thanks Jan-Piet as well. Ironically the Ansible py
On Thu, Oct 01, 2015 at 08:40:03AM -0400, Larry Smith wrote:
> I should also note...All static entries other than AD related (SRV) work
> and all DHCP (ISC-DHCP) DDNS related entries are created and work; other
> than AD DDNS related entries which should be created automatically within
> each zone.
I should also note...All static entries other than AD related (SRV) work
and all DHCP (ISC-DHCP) DDNS related entries are created and work; other
than AD DDNS related entries which should be created automatically within
each zone.
Zones pre-created are below.
example.org
_msdcs.example.org
_sites.
I was actually looking for anyone who has experienced issues with AD
integration. DDNS works and has worked but for some reason I cannot get AD
working either automatically (i.e. auto registered via the client) or by
manually adding records from netlogon.dns (i.e. NSEDIT, Ansible using PDNS
API or
