Debian vs SuSE
Andy Shellam (Mailing Lists)
andy.shellam-lists at mailnetwork.co.uk
Wed Sep 12 18:13:15 UTC 2007
Hi Bill,
I've done what you've done today many a time (realised what I've done
wrong during the day on the drive home and kicked myself that is!)
As Kevin said, you're not bound to where you put your files. The
"standard" I've heard advised is configuration files in /etc, run-time
files in /var, and program files in /usr.
Personally I've never stuck to that; mainly from a maintenance
point-of-view - for a single application you have files in at least 3
places, so what I do, is install applications in /usr/local/<app_name>
and have the sub-directories etc and var in there. Obviously you have
the occasional applications that have to be shared (e.g. MySQL
libraries), to which end I link the library from
/usr/local/<app_name/lib/<library> to /lib/<library> (or use ldconfig if
the system supports it.)
For Bind, I have:
Config files:
/usr/local/bind/etc/named.conf
/usr/local/bind/etc/zones/<zone files>
Run-time files:
/usr/local/bind/var
/usr/local/bind/var/logs
Program files:
/usr/local/bind/bin
/usr/local/bind/sbin
This has the added security benefit that I can chroot Bind into
/usr/local/bind, and it has everything it needs!
Just my 2p.
Andy.
Bill.Light at kp.org wrote:
> Argghhh
> Thanks Kevin and Mark
>
> I thought about what I was putting in that .local file on the drive home,
> and kicked myself (pretty hard to do in traffic)... Anyway, it dawned on
> me that I was trying to make what was in SuSE box /var/lib/named in the
> Debian /etc/bind when it should have been what was in the SuSE
> /etc/named.conf file
>
> ...Sigh... Is there a recommended convention for which directory to place
> the db.domain & the db.ip.address into? Leave all in /etc/bind ?
>
> Bill
>
> ================================================================================================
>
>
>
>
>
> You're "include"ing zone data directly into your nameserver
> configuration. Don't do that. I think what you meant to do is include
> zone *definitions* into named.conf, e.g.
>
> zone "foo.bar" {
> type master;
> file "foo.bar";
> };
>
> Review the contents of the files on your SuSE box and you'll probably
> discover where you went wrong.
>
> Note that each flavor of Unix or Linux has *conventions* about where to
> put zone files, the structure of the named.conf, etc. but unless you're
> using a special OS-provided tool to manage your BIND setup, you're not
> really bound by those conventions and can put the files and directories
> wherever you want (within reason, of course, special-purpose directories
> or filesystems like /proc, /sys or /dev would be off-limits).
>
>
> - Kevin
>
> Bill.Light at kp.org wrote:
>
>> In /etc/bind/named.conf.local, I added the following line after the line
>>
>
>
>> // include "/etc/bind/zones.rfc1918";
>> include "/etc/bind/zone.light-family.com";
>>
>> I then used the SuSE convention I was shown of db.light-family.com and
>> copied to zone.light-family.com (also in /etc/bind/ directory) which
>> looks like:
>>
>> $TTL 86400
>> light-family.com. IN SOA dns1 (
>> webmaster ; Who to notify at
>> "light-family.com"
>> 2003060101 ; Serial
>> 7200 ; Refresh after 2 hours
>> 3600 ; Retry after 1 hour
>> 604800 ; Expire after 1 week
>> 7200 ) ; Negative Cache TTL of 2 hours
>> ;
>> ; Name servers
>> ;
>> IN NS dns1.light-family.com.
>> IN NS ns1.4servers.com.
>> IN NS ns2.4servers.com.
>> ;
>> ; Mail servers
>> ;
>> IN MX 10 mail.light-family.com. ;
>>
>
>
>> Primary
>> ;mail IN A 66.124.156.123
>> ;
>> ; Host addresses
>> ;
>> localhost IN A 127.0.0.1
>> dns1 IN A 66.124.156.123
>> mail IN A 66.124.156.123
>> ;
>> ; Aliases
>> ;
>> www IN CNAME dns1.light-family.com.
>> ;
>> ; SPF Record setup - see: http:///spf.pobox.com/
>> ;
>> light-family.com. IN TXT "v=spf1 a
>>
> mx:mail.light-family.com
>
>> mx:mail.light-family.com ip4:66.124.156.123 include:light-family.com,
>> include:sbcglobal.net ~all"
>>
>> I thought I was being failry vanilla, but I'm still getting lost as to
>> where files are in Debian vs SuSE. I am a total Debian noob.
>>
>> SuSE Bind is 9.2.4 (as I recall it is an old 9.0 or 9.1 SuSE distro)
>> and the Bind on debian is 9.3.4
>>
>> Bill
>>
>>
>>
> ==============================================================================
>
>>
>>
>> Karl Auer <kauer at biplane.com.au>
>> Sent by: bind-users-bounce at isc.org
>> 09/11/07 03:52 PM
>>
>> To
>> comp-protocols-dns-bind at isc.org
>> cc
>>
>> Subject
>> Re: Debian vs SuSE
>>
>>
>>
>>
>>
>>
>> On Tue, 2007-09-11 at 15:04 -0700, Bill.Light at kp.org wrote:
>>
>>
>>> I am moving a working BIND from a SuSE box to a Debian (Etch) box. I've
>>>
>
>
>>
>>> tried scp, copy/paste and touching a new file, typing from scratch ....
>>>
>
>
>>> all with the same result.
>>> When I rndc reload or start, I start off with a string of errors
>>> unknown option '$TTL'
>>> unknown option 'Who'
>>> unknown option 'Serial'
>>>
>>> I've tried starting with a comment (semi-colon) and it eliminates all
>>> those errors, and then gives syntax error near ';'
>>>
>>>
>> It sounds a bit as if you are not loading the file you think you are
>> loading. "Unknown option" doesn't usually come from a zone file, but
>> from a config file - but $TTL is in a zone file, not a config file.
>>
>> Are the BIND versions the same? How about posting the actual fragment
>> that gives the error?
>>
>> Regards, K.
>>
>
>
>
>
>
> !DSPAM:37,46e822f87682090717691!
>
>
>
>
More information about the bind-users
mailing list