# Documenting variable suboption types in a module

**URL:** <https://forum.ansible.com/t/documenting-variable-suboption-types-in-a-module/32346>\
**Category:** Ansible Developer\
**Created:** [February 27, 2020, 7:24pm UTC](https://forum.ansible.com/t/documenting-variable-suboption-types-in-a-module/32346 "2020-02-27T19:24:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![John\_Nelson1](https://avatars.discourse-cdn.com/v4/letter/j/c68b51/32.png) [@John\_Nelson1](https://forum.ansible.com/u/John_Nelson1)\
**Post date:** [February 27, 2020, 7:24pm UTC](https://forum.ansible.com/t/documenting-variable-suboption-types-in-a-module/32346/1 "2020-02-27T19:24:40Z")

</div>

While working on a PR for the [win\_dns\_record](https://docs.ansible.com/ansible/latest/modules/win_dns_record_module.html) module, I ran into a documentation issue that I thought best to ask about, in case anyone can offer any suggestions or otherwise correct my thinking. As background, I’m trying to extend the existing module to support additional DNS record types. Of concern is that the new record types take _values_ that are more nuanced than those currently supported.

---

<div class="post-metadata">

**Author:** ![cassell](https://avatars.discourse-cdn.com/v4/letter/c/ecae2f/32.png) [@cassell](https://forum.ansible.com/u/cassell)\
**Post date:** [February 27, 2020, 11:37pm UTC](https://forum.ansible.com/t/documenting-variable-suboption-types-in-a-module/32346/2 "2020-02-27T23:37:08Z")

</div>

I think the general recommendation would be to create one module per record type if it gets complex. Share common code using module\_utils.

V/r,  
James Cassell