Trying to wrap my head around views.

[kollross]

I thought I had a good understanding of views but apparently not.

Situation:

I have a zone called asdf.com. This zone is the default view "public". I have some of other sub zones.

foo.asdf.com (view public)
internal.asdf.com (view private)
bar.foo.asdf.com (view public)
dev.internal.asdf.com (view private).

Looking at the Zones view of asdf.com, it shows foo.asdf.com and bar.foo.asdf.com as child domains for asdf.com. Looking at internal.asdf.com it shows dev.internal.asdf.com as a child of internal.asdf.com (ok that makes sense I guess).

However is I assign a DNS name to an IP of (blah.internal.asdf.com) it will only create DNS record as blah.internal under the asdf.com zone, not blah under the internal.asdf.com zone). Changing internal.asdf.com to the public view solves this problem.

I'm sure there is a rational there, but it also seems to limit being able to create records in anything but the default zone.

[peteeckel]

Hi @kollross, thanks for the detailed description.

You can view Views as namespaces: The zones in the different views are unrelated to each other. So zone x.y.z will only show up as a child zone of zone y.z if both are in the same view.

I would guess that you only assigned the 'public' view to the prefix containing the IP address. If 'private' isn't assigned to it, there will be no address record for internal.asdf.com. If you assign both views, you will get two address records: blah.internal in asdf.com and blah in internal.asdf.com. That's because the zones are unrelated - if they are in the same view you only get the latter, because internal.asdf.com is the longer match.