Which version of ajjahn-dns are you using?

from puppet-dns.

Also, please include your Profile::Nameserver class, so we can see how you're invoking dns::server::options.

from puppet-dns.

version 2.1.0

class profile::nameserver(
Hash $options,
Hash $zones,
Hash $a_records,
Hash $cname_records,
) {
class { '::dns::server': }

Build records

create_resources('dns::server::options', $options)
create_resources('dns::zone', $zones)
create_resources('dns::record::a', $a_records)
create_resources('dns::record::cname', $cname_records)
}

from puppet-dns.

inside nameserver.yaml
profile::nameserver::options:
/etc/bind/named.conf.options: <-- this was set to /etc/named > I correct this to Debian path but this is not a long term solution, how can I get it to choose based on OSfamily?

Its not the module , it was how I am calling dns::server::options

from puppet-dns.

You can't change it based on OSfamily entirely within Hiera - you need puppet logic.

What you can do is move the options "up" a level and feed it in properly in the profile:

profile::nameserver::options:
    forwarders:
        - 8.8.8.8
        - 8.8.4.4

class profile::nameserver(
    Hash $options,
    Hash $zones,
    Hash $a_records,
    Hash $cname_records,
) {
    class { '::dns::server': }
    # Build records
    include dns::server::params
    create_resources('dns::server::options', {
            "${dns::server::params::cfg_dir}/named.conf.options" => $options
        })
    create_resources('dns::zone', $zones)
    create_resources('dns::record::a', $a_records)
    create_resources('dns::record::cname', $cname_records)
}

from puppet-dns.