[Pdns-users] PDNS and Isilon Smartconnect Delegation

[Ian Easter]

Morning Bert

Thank you for your help last week with my Isilon issue.  As well as thank
you to ph1.

Isilon round robin issue ended up being related to network configuration
for the guest machines.  Once I cleared that up, the PDNS Recursor Forward
Zone configuration worked without a hitch.

For closure, and anyone else that happens across this thread that is
migrating from BIND, I figured I would follow up to maybe be a source of
assistance.

Your SmartConnect Zone(Domain) name will be added in the PDNS Recursor
configuration file and point to your SmartConnect service IP.

As an example:
* forward-zones=isilon-mgmt.teve.inc=10.1.1.100,
isilon-nfs.teve.inc=192.168.100.100*

*Thank you,*
*Ian Easter*




On Thu, Dec 13, 2018 at 2:42 PM bert hubert <bert.hubert at powerdns.com>
wrote:

> On Thu, Dec 13, 2018 at 02:17:23PM -0500, Ian Easter wrote:
> > Recently switched from BIND9.7.3 to PowerDNS and working through some
> > adjustments.
> >
> > We previously followed the guidelines for DNS based on the documentation:
> >
> https://www.emc.com/collateral/hardware/white-papers/h8316-wp-smartconnect.pdf
> > and everything worked without issue.
>
> Hi Ian,
>
> We happen to have a quorum of people with Isilon expertise present on our
> IRC channel right now. Could you drop by?
> https://www.powerdns.com/opensource.html
> has a link to a web client.
>
> Thanks!
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.powerdns.com/pipermail/pdns-users/attachments/20181217/0e8d33ad/attachment.html>