Okay, let me be very clear:
"There is only one configuration file for named. It is named.conf. Everything else derives from that. There is no named.conf.local, except insofar as one might be included by an include statement in named.conf."
So look inside your linux named.conf to see what's there, and if you like it, copy that over. Every other sub-configuration file, every zone file, every tsig configuration file, every key definition file, every ACL file, every other file is either included from or defined through named.conf. There is no particular standard for how this is done, and those of us who've been managing BIND since the 1980's each have our own preferred way to make the configuration manageable.
If you want a configuration subfile that does not exist, you can include it. Sticking
include "named.swbartley.conf"
into your named.conf file will cause BIND to include that file into the configuration. You can make the configuration look like whatever you please, that's part of what makes it "configuration."