103 reputation
2
bio website
location
age
visits member for 1 year, 11 months
seen Mar 25 at 9:06

Feb
9
asked Bind and redirection of clients
Feb
5
comment Debian Wheezy, bind and generic config with views
Nope, no extra includes anywhere. And all is working good. Take a look at the output of named-checkconf -p, if you would like — pastebin.com/2pzzciS2
Feb
5
comment Debian Wheezy, bind and generic config with views
Thinking about it more, I decided to include the zones within the unhittable views (default_view and global_view) into my custom views in the named.conf.local. I didn't managed to do this gracefully using include directive (named-checkconf reports <...> all zones must be in views error, even if I include zones in a view; probably should bugreport this), so I ended up just copypasting all the zones to all of my three views, which are actually used (in the original question I simplified things and mentioned only one). The resulting named.conf.local is pastebin.com/VF3Y7xL5
Feb
4
comment Debian Wheezy, bind and generic config with views
Thank you for your explanation, Hakan. In my case, however the caveats which you pointed me to are not really relevant, because only root and local users are allowed to use DNS-server and only local_view view and its myho.st zone will be hit ever. So, if I follow your logic properly, I can even delete all other views and their underlying zones in their entirety and this will not affect the name resolution at all.
Feb
4
comment Debian Wheezy, bind and generic config with views
Well, that did the trick, didn't knew that views/zones declaration order matters. Thanks a lot!
Feb
4
awarded  Scholar
Feb
4
accepted Debian Wheezy, bind and generic config with views
Feb
4
asked Debian Wheezy, bind and generic config with views
Feb
4
awarded  Supporter