Answers: <p>From what I can see</p>
  <ul>
  <li>os-floating-ip-dns - Floating IP DNS support. This seems to be limited to integrating floating IP DNS with external DNS services. Not a DNS inside Openstack.</li>
  <li>dns or dns_domain_ports : Allows you to add a FQDN to a port in Openstack. Then, if it's an internal network, the dnsmasq instance (that acts as DHCP and DNS) will be able to resolve the zone and the associated hostname.</li>
  </ul>
  <p><code>dns_domain_ports</code> seems to be the new plugin name for Queens and up. <a href="https://review.opendev.org/c/openstack/charm-neutron-api/+/635667/2/hooks/neutron_api_context.py" rel="nofollow noreferrer">Change in config</a></p>
  <p>There doesn't seem to be any configuration for <code>dns-integration</code>. It's either <code>dns</code> or <code>dns_domain_ports</code></p>
  
Answers: CC BY-SA 4.0
Answers: 2022-02-27T22:53:57.377Z
Answers: While this is great information, where did you find it? Teach a man to fish, etc.
Answers: Evan Carroll
Answers: CC BY-SA 4.0
Answers: 2022-02-27T23:27:46.210Z
Answers: No great magic there - like I mentioned in the post : https://review.opendev.org/c/openstack/charm-neutron-api/+/635667/2/hooks/neutron_api_context.py
  
  And some trial and error in my own Openstack lab. Unfortunately, the Openstack doc is pretty barebones for some uses cases.
Answers: LaurentDumont
Answers: CC BY-SA 4.0
Answers: 2022-02-27T08:49:33.077Z
Answers: 2022-02-27T08:49:33.077Z
Answers: LaurentDumont
Body: <p><a href="https://devops.stackexchange.com/q/15507/18965">There is <em>something</em> (still not exactly sure because of the documentation) that allows DNS internal resolution in OpenStack through an extension</a>. I'm wondering if any of these do that deed (from the output of <code>extension list</code>)</p>
  <ul>
  <li><code>os-floating-ip-dns</code> - Floating IP DNS support.</li>
  <li><code>dns-integration</code> - Provides integration with DNS.</li>
  <li><code>dns-domain-ports</code> - Allows the DNS domain to be specified for a network port.</li>
  </ul>
  <p>These are all very interesting to me. Is there anyway to find more information about what these do than the 4 or 5 vague words their described with with <code>extension list</code>?</p>
  
Tags: <openstack>
Title: How can I get more information about an OpenStack extension?
UserDisplayName: Evan Carroll
ThreadText: # How can I get more information about an OpenStack extension?
  
  (Asked by: username_0 on 2022-02-23)
  
  [There is *something* (still not exactly sure because of the documentation) that allows DNS internal resolution in OpenStack through an extension](https://devops.stackexchange.com/q/15507/18965). I'm wondering if any of these do that deed (from the output of `extension list`)
  
  * `os-floating-ip-dns` - Floating IP DNS support.
  * `dns-integration` - Provides integration with DNS.
  * `dns-domain-ports` - Allows the DNS domain to be specified for a network port.
  
  These are all very interesting to me. Is there anyway to find more information about what these do than the 4 or 5 vague words their described with with `extension list`?
  
  **Tags:** openstack
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2022-02-27. Score: 1
  
  From what I can see
  
  * os-floating-ip-dns - Floating IP DNS support. This seems to be limited to integrating floating IP DNS with external DNS services. Not a DNS inside Openstack.
  * dns or dns\_domain\_ports : Allows you to add a FQDN to a port in Openstack. Then, if it's an internal network, the dnsmasq instance (that acts as DHCP and DNS) will be able to resolve the zone and the associated hostname.
  
  `dns_domain_ports` seems to be the new plugin name for Queens and up. [Change in config](https://review.opendev.org/c/openstack/charm-neutron-api/+/635667/2/hooks/neutron_api_context.py)
  
  There doesn't seem to be any configuration for `dns-integration`. It's either `dns` or `dns_domain_ports`
  
  > **Comments:**
  > **username_0**: While this is great information, where did you find it? Teach a man to fish, etc.  
  > **username_1**: No great magic there - like I mentioned in the post : https://review.opendev.org/c/openstack/charm-neutron-api/+/635667/2/hooks/neutron_api_context.py  And some trial and error in my own Openstack lab. Unfortunately, the Openstack doc is pretty barebones for some uses cases.  
  
  ---
  
  