On 2016-03-23 11:31 AM, syaginf wrote:
Are you suggesting to run recursor on 53
PDNS on port 8699
and have nodes talk to recursor directly?
What would forward-zones= will look to make recursor ask pdns about .hpc
addresses?
This is how most people would do it; yes.
forward-zones=hpc.=127.0
Seems like it works if we do it this way.
Recursor on port 53
PDNS on custom port 8669
add
forward-zones=isilon.hpc=192.168.3.0,hpc=127.0.0.1:8669
Good to know that I was doing this all backwards.
--
View this message in context:
http://powerdns.13854.n7.nabble.com/Powerdns-Problem-with-Deleg
Ok. So maybe we are doing things a wrong way.
Currently we have pdns running on port 53.
we have recursor running on port 8699
in pdns.conf we have
allow-recursor=127.0.0.0/8,192.168.3.0/24
recursor=127.0.0.1:8699
So nodes send requests to main pdns auth server and if it's not part of hpc
it is
On Wed, Mar 23, 2016 at 08:03:04AM -0700, syaginf wrote:
> What is interesting with
> forward-zones=isilon.hpc=192.168.3.0 set
> if I do dig and point to recursor dns and port - I get the A record I need.
> But when I ask PDNS server i don't get A record.
> So it seems like I need to do something
On Wed, Mar 23, 2016 at 07:50:37AM -0700, syaginf wrote:
> I have tried following options as this point
> forward-zones=isilon.hpc=192.168.3.0
> forward-zones=+isilon.hpc=192.168.3.0
> forward-zones-recurse=192.168.3.0
>
> None of them provide me with result that I need.
> I still don't get A rec
On 2016-03-23 9:03 AM, syaginf wrote:
What is interesting with
forward-zones=isilon.hpc=192.168.3.0 set
if I do dig and point to recursor dns and port - I get the A record I need.
But when I ask PDNS server i don't get A record.
So it seems like I need to do something that would make PDNS ask rec
What is interesting with
forward-zones=isilon.hpc=192.168.3.0 set
if I do dig and point to recursor dns and port - I get the A record I need.
But when I ask PDNS server i don't get A record.
So it seems like I need to do something that would make PDNS ask recursor
about this and it's not happening
I have tried following options as this point
forward-zones=isilon.hpc=192.168.3.0
forward-zones=+isilon.hpc=192.168.3.0
forward-zones-recurse=192.168.3.0
None of them provide me with result that I need.
I still don't get A record answer.
On Wed, Mar 23, 2016 at 07:12:28AM -0700, syaginf wrote:
>
I had tried that before posting here, but the result is the same.
when putting
forward-zones=isilon.hpc=192.168.3.0
I still don't get answer for A record.
--
View this message in context:
http://powerdns.13854.n7.nabble.com/Powerdns-Problem-with-Delegation-to-Isilon-tp12204p12211.html
Sent f
On Wed, Mar 23, 2016 at 06:30:47AM -0700, syaginf wrote:
> This is the part I don't understand I guess.
> what would be the forward zone that I am serving?
> if it's not isilon.hpc and not isilon-dns.hpc? What exactly am I serving and
> how do I put it in?
> forward-zone=???=???
>
> Because what i
Ok. This is clearly a part I don't understand then.
So i need to put something in
forward-zones=
But what do it put there?
it's not isilon.hpc and not isilon-dns.hpc
So what is it?
forward-zone==???
What i need to happen is NFS queary isilon.hpc and get ip address and use it
to do mount.
I am
This is the part I don't understand I guess.
what would be the forward zone that I am serving?
if it's not isilon.hpc and not isilon-dns.hpc? What exactly am I serving and
how do I put it in?
forward-zone=???=???
Because what is happening is nfs would query isilon.hpc and it need to
resolve that t
On Wed, Mar 23, 2016 at 06:12:53AM -0700, syaginf wrote:
> I have pdns-recursor configured.
> It works for outside addresses , but I can't seem to make it respond for
> this type of requests.
>
> Indeed what happens on bind side is isilon would return one of the addresses
> from dynamic pool.
> So
I have pdns-recursor configured.
It works for outside addresses , but I can't seem to make it respond for
this type of requests.
Indeed what happens on bind side is isilon would return one of the addresses
from dynamic pool.
So if I keep repeating requests I will keep getting different addresses m
On Wed, Mar 23, 2016 at 05:44:56AM -0700, syaginf wrote:
> Greetings.
> We are in the process of migrating from Bind to Powerdns on one of our
> compute cluster.
> Issue we are having is related to DNS Delegation for Isilon (Related to
> Isilon Smart Connect feature.)
>
> Server is Master for .hpc
Greetings.
We are in the process of migrating from Bind to Powerdns on one of our
compute cluster.
Issue we are having is related to DNS Delegation for Isilon (Related to
Isilon Smart Connect feature.)
Server is Master for .hpc
we need to delegate for isilon.hpc
In order to achive that we have
16 matches
Mail list logo
