Ah...You actually *may* have hit a bug. What version of powerdns and
what backend? There's an issue on github, number 49, fixed in commit
number 549 according to the bug where PDNS was behaving similar to
this...if you dig for things *under* that subdomain eg
test.labisilon.lab.domain.com you get
Michael,
the PowerDNS server IS the main recursor resolver and the IP of the PowerDNS
server is actually in /etc/resolv.conf for all of the platform servers. We no
longer have any BIND servers in our infrastructure.
Here are the dig outputs:
$ dig @pdns01 NS labisilon.lab.domain.com
; <<>> D
No you definitely do not want to add an A record for
labisilon.lab.domain.com to the powerdns server, that would cause it
to always serve the A record. From the response information I take it
the powerdns server isn't your recursive resolver (IE it's not whats
in the /etc/resolv.conf or equivalent
Peter,
Thank You we did manage to get it to work via auth = 1. I have one
other question in regards to the DS and DNSKEY records from a registry
perspective ICANN requires registrars to provide a mechanism allowing a
domain owner to secure a zone. The registrar has to submit the DS and
DNSKE
Hello Eric,
On Dec 13, 2013, at 17:42 , Eric Haskins wrote:
> I am in the middle of migration testing for 330K Domains and 1.8
> Million records from a MyDNS with a Bind Mysql backend to PowerDNS with
> PDNSSEC with gmysql backend, We have had no issue migrating zones and
> records a
Hello Everyone,
I am in the middle of migration testing for 330K Domains and 1.8
Million records from a MyDNS with a Bind Mysql backend to PowerDNS with
PDNSSEC with gmysql backend, We have had no issue migrating zones and
records after creating the scripts. Our issue lies in serving the
Sorry - replace “pslisilon.lab.securustech.net” with “pslisilon.lab.domain.com”
(trying to keep things simple)
--
Drew Decker
Sent with Airmail
On December 13, 2013 at 10:23:02 AM, Drew Decker (drewrocksh...@gmail.com)
wrote:
pslisilon.lab.securustech.net__
Same output -
dig @psl-pdns01 A pslisilon.lab.securustech.net
; <<>> DiG 9.8.3-P1 <<>> @pdns01 A labisilon.lab.domain.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24930
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDI
So there is no A record for labisilon.lab.example.com in the pdns01 name
server? (What's the dig output when you request the A record for the
delegated domain?)
Michael,
You are correct - my typo - it is labisilon (not simply isilon).
When I do “dig @pdns01 NS labisilon.lab.example.com" I get the
No it's shared - so to speak. It's part of the lab.example.com domain. That's
the "common" domain. I'm trying to delegate labisilon.lab.example.com to the
isilon smartconnect feature.
Sent from my iPhone
> On Dec 13, 2013, at 7:48 AM, "k...@rice.edu" wrote:
>
>> On Thu, Dec 12, 2013 at 06:17
On Thu, Dec 12, 2013 at 06:17:50PM -0600, Drew Decker wrote:
> Does anyone else know of a way to do this, or could give me some
> recommendations on how we could do this in or current configuration? We
> just need to be able to create a delegation in PowerDNS to use a
> different Nameserver on t
11 matches
Mail list logo
