Building PTR Records Fails With Same Resource Defined In Seperate Zones

[rustyautopsy]

If you try to use whats below puppet fails with...

Error: Duplicate declaration: Dns::Record::Ptr[40] is already declared

As you can see the entry I am trying to add is for separate subnets.

PTR:

dns::record::ptr {
'40':
zone => '1.0.10.IN-ADDR.ARPA',
data => ["eg1.example.com"];
}

PTR:

dns::record::ptr {
'40':
zone => '2.0.10.IN-ADDR.ARPA',
data => ["eg2.example.com"];
}

Thanks in advance.

[ajjahn]

This is because you're using the shorthand where the name of the resource is used as the host. You can specify a unique name and then set the host parameter directly like this:

PTR:

dns::record::ptr { '40-zone-1':
host => '40',
zone => '1.0.10.IN-ADDR.ARPA',
data => ["eg1.example.com"];
}

PTR:

dns::record::ptr { '40-zone-2':
host => '40',
zone => '2.0.10.IN-ADDR.ARPA',
data => ["eg2.example.com"];
}

Let me know if it still doesn't work.

[rustyautopsy]

Hey Adam,

Thanks for helping out. All I had to do was updated my version of the
module, and what you suggested worked great.

Cheers.

On Thu, Dec 6, 2012 at 3:29 PM, Adam Jahn notifications@github.com wrote:

This is because you're using the shorthand where the name of the resource
is used as the host. You can specify a unique name and then set the host
parameter directly like this:
PTR:

dns::record::ptr { '40-zone-1':
host => '40',
zone => '1.0.10.IN-ADDR.ARPA',
data => ["eg1.example.com"];
}
PTR:

dns::record::ptr { '40-zone-2':
host => '40',
zone => '2.0.10.IN-ADDR.ARPA',
data => ["eg2.example.com"];
}

Let me know if it still doesn't work.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/12#issuecomment-11111271.

Travis Dolan
Network Services Administrator
Direct: 604.214.8562 I Fax: 604.214.8556

Check out Lasso’s Blog at http:// http://blog.lassodatasystems.com/
www.lassodatasystems.com/blog/
to learn about cool technologies and more for selling real estate.