diff --git a/heat/engine/resources/openstack/keystone/role.py b/heat/engine/resources/openstack/keystone/role.py
index 51d1416c74..620427d32d 100644
--- a/heat/engine/resources/openstack/keystone/role.py
+++ b/heat/engine/resources/openstack/keystone/role.py
@@ -51,9 +51,8 @@ class KeystoneRole(resource.Resource):
         DOMAIN: properties.Schema(
             properties.Schema.STRING,
             _('Name or id of keystone domain.'),
-            default='default',
             constraints=[constraints.CustomConstraint('keystone.domain')],
-            support_status=support.SupportStatus(version='10.0.0')
+            support_status=support.SupportStatus(version='16.0.0')
         )
     }
 
diff --git a/releasenotes/notes/remove-default-domain-from-templates-b5965242bfb78145.yaml b/releasenotes/notes/remove-default-domain-from-templates-b5965242bfb78145.yaml
new file mode 100644
index 0000000000..ca46f199f0
--- /dev/null
+++ b/releasenotes/notes/remove-default-domain-from-templates-b5965242bfb78145.yaml
@@ -0,0 +1,13 @@
+---
+prelude: >
+    There was a mismatch between the way heat create role behaved with the
+    templates or with the openstack CLI on what relates to the default domain
+    if the domain is not specified on both cases the CLI will not assign on
+    to the created new role but the heat templates will assign the "default"
+    domain
+critical:
+  - |
+    Templates that creates roles but does not specify the domain will not get
+    a "default" domain from now on. To have a domain added to your new role
+    it needs to be assigned in the template.
+