[Samba] How to switch from internal DNS to Bind

[James]

On 12/31/2015 11:01 AM, Reindl Harald wrote:
>
>
> Am 31.12.2015 um 16:51 schrieb James:
>> I forgot, I do not want to update the distro at the moment. My
>> production is currently on 12.04. Want to keep things symmetrical. I'm
>> going to compile and build bind again.
>>
>> mount | grep /run
>> tmpfs on /run type tmpfs (rw,noexec,nosuid,size=10%,mode=0755)
>> none on /run/lock type tmpfs (rw,noexec,nosuid,nodev,size=5242880)
>> none on /run/shm type tmpfs (rw,nosuid,nodev)
>
> so it's like on every recent distribution not persistent
> https://www.google.at/#q=ubuntu+12.04+/var/run
>
> http://askubuntu.com/questions/303120/how-folders-created-in-var-run-on-each-reboot 
>
>
>
>
That second link proved helpful. Thank you.

The errors I posted were prior to using a init script. Creating one and 
using the following eliminated the errors.

cat /etc/init/bind9.conf
# bind9 - bind9 job file
description "bind9 Domain Name Server For Samba4"

start on runlevel [2345]
stop on runlevel [!2345]

pre-start script
     mkdir -p -m0777 /run/named
     chown root:named /run/named
end script

exec /usr/sbin/named -u named

Do the permissions look about right for /run? I now get these errors.


Dec 31 12:01:59 VMDC1 named[939]: configuring command channel from 
'/etc/bind/rndc.key'
Dec 31 12:01:59 VMDC1 named[939]: couldn't add command channel 
127.0.0.1#953: file not found
Dec 31 12:01:59 VMDC1 named[939]: configuring command channel from 
'/etc/bind/rndc.key'
Dec 31 12:01:59 VMDC1 named[939]: couldn't add command channel ::1#953: 
file not found
Dec 31 12:01:59 VMDC1 named[939]: the working directory is not writable

If I make /etc/bind writable via. the init script. I still get these 
messages. Maybe it's referring to another folder?


-- 
-James