InfoBlox backend docs out of date

[Kiall Mac Innes]

InfoBlox backend docs out of date, they need to be updated for pools.yaml.

[selvakumar (selvakumar-nms)]

can anybody help us in giving the backend dns configuration in pools.yaml for infoblox?

Your help is appreciated.

[Erich Birngruber (ebirn)]

Hi,

I'm currently in the process of setting up Designate with an infoblox backend on the test system. This is what my pool.yaml file looks like at the moment.
I'm not using multi-tenancy yet, but it works for DNSaaS and automatic record creation/deletion on instance start/delete.

---
- name: default
  description: InfoBlox Pool
  attributes: {}

  # List out the NS records for zones hosted within this pool
  # these will be put into each zone that is created in infoblox
  ns_records:
    - hostname: "infoblox-test.example.com."
      priority: 1

  # List out the nameservers for this pool. These are the actual dns
  # servers addresses. We use these to verify (query for) changes have propagated to all nameservers.
  nameservers:
    - host: "infoblox-test.example.com"
      port: 53

  targets:
    - type: infoblox
      description: InfoBlox Cluster API

      # designate mdns is the master, it must run on port 53 for infoblox to query it
      masters:
        - host: "controller.openstack.example.com"
          port: 53

      options:
        # api is only used to
        wapi_url: "https://infoblox-test.example.com/wapi/v2.0/"
        username: "infoblox_username"
        password: "infoblox_secret_password"
        sslverify: False
        # multi_tenant: ""
        # dns_view: ""
        # net_view: ""
        # this must be predefined on infoblox, containing the infoblox server(s) as grid secondaries,
        # all the mdns as external primaries
        ns_group: "openstack-designate-group"
        # infoblox DNS host to send NOTIFY to,
        # to sync up records from mdns on controller node,
        host: "infoblox-test.example.com"
        port: 53