Can't create a subdomain

D

.decimaL

Verified User
Joined
Feb 20, 2011
Messages
7
I've googled around and can't seem to find an answer, I hope it's just not an obvious fix that I'm overlooking.

Everytime I try to create a subdomain for one of my domains, I get this error:

Error writing the db file: Error writing /var/named/domain.com.db : /var/named/domain.com.db is a link or hardlink. Will not run tokenizer on it.

Where domain.com is my domain.

Any help is appreciated.

Thanks.
 
Seems I can't edit my first post.

I just did another search on Google and found another user with the same problem as mine, a user recommended running 2 commands via ssh.

I did, this is the output:

[root@s1 ~]# ls -ld /var/named/
drwxr-x--- 5 root named 4096 Mar 27 17:33 /var/named/
[root@s1 ~]# ls -l /var/named/domain.com.db
lrwxrwxrwx 1 root named 41 Feb 20 12:20 /var/named/domain.com.db -> /var/named/chroot//var/named/domain.com.db
 
Check if all domains are symlink

Code: 
ls -l /var/named/

and post output of:

Code: 
ls -l /var/named/chroot//var/named/

Those files shouldnt be redirected anywhere.

If this is just the only one you should do the following.

Code: 
rm /var/named/domain.com.db
mv /var/named/chroot//var/named/ /var/named/domain.com.db
chown named:named /var/named/domain.com.db
/etc/init.d/named restart

DO THAT ONLY IF IT IS THE ONLY FILE LINKED.
If is not the only one linked so post the result of the first 2 command i sayd.

Regards
 
Thanks for all the replies.

I did do a search, but at the time nothing came up, I think I may have tried to much of an exact search, did a more loose search after I posted the topic and that's when I found the other topic.

I also did what was in this topic: http://help.directadmin.com/item.php?id=128
However, now named won't restart.
I tried /etc/init.d/named restart , but it just says [FAILED]

Can't seem to find any log of it anywhere as well, to pinpoint the exact problem.

Thanks and Regards.
 
Just as a followup, I was on the box to address this, and the final problem was an out-of-sync pid file. A simple nuke did the trick:
Code: 
killall -9 named
/etc/init.d/named start
The restart command had given this, which hinted to the out-of-sync pid file
Code: 
[root@s1 named]# /etc/init.d/named restart
Stopping named:                                            [FAILED]
named: already running
Everything else was done correctly (named was un-chrooted), but named just needed a kick to be restarted.

John
 
You must log in or register to reply here.
Back
Top