Comment 5 for bug 1714088

I was going to submit a new bug report but this this seems directly related to my issue.

How to reproduce my specific issue:
User has privileges in Project1 and Project2 projects
1. User creates a shared network "SharedNet" in Project1 with dns_domain "dev.example.com"
2. User creates a zone in Project1 for "dev.example.com"
3. User creates an instance in Project1 attached to "SharedNet". Neutron creates PTR zone/record in the "service" project. Neutron then looks for and finds the associated "dev.example.com" Zone in Project1 and creates an A record there appropriately. (All good so far)
4. User creates an instance in Project2 attached to "SharedNet". Neutron creates the PTR record in the "service" project. Neutron then looks for the associated "dev.example.com" Zone in Project2 but cannot find it and so A record creation fails.

Sharing Neutron networks between projects is a very common use case. As such, Zones should have a similar functionality or Neutron needs to look across projects for the matching domain.

Thanks!