New users can't see sites after Bind update

B

blanezx3

Verified User
Joined
Sep 14, 2006
Messages
16
Location
Virginia
OS - FC4
kernel - 2.6.16*

I used yum to update the following packages:

[user @ packages]# ls bind*
bind-9.3.1-20.FC4.i386.rpm
bind-utils-9.3.1-20.FC4.i386.rpm
bind-chroot-9.3.1-20.FC4.i386.rpm
bind-libs-9.3.1-20.FC4.i386.rpm

Now when I create a user they cannot access their site. There is nothing in /var/named/chroot/var/named for them. There IS an entry in /var/named, but they are still unable to see http://theirurl.com.

Anyone here know why the users can't access their sites? I've done a workaround which was listed on the DNS forum, but it only worked that one time. If anyone could help it would be greatly appreciated.
 
Btw, There is nothing in the apache error logs. There is an index.html file which was created by DA. I've gone so far as to delete/re-add users and the same thing happens.

:confused:
 
Yep. All of the old sites are working fine.
This is only happening when I add new users.

[blane@*** ~]$ ps aux | grep named
named 5033 0.0 0.3 37456 3764 ? S Sep14 0:01 /usr/sbin/named -
blane 11453 0.0 0.0 3764 676 pts/1 S 02:17 0:00 grep named



[root@*** ~]# /etc/init.d/named restart
Stopping named: [ OK ]
Starting named: [ OK ]
[root@*** ~]#


Any other ideas? This one has me confused..:confused:

Could it be that the httpd.conf in for those new users isn't correct? I've compared them with older accounts which work fine and they look to be the same format/syntax. Getting 404 errors when trying to access the new sites. I've already chmod a+x and 777 ~/public_html on a "test" account and it didn't make a difference...
 
Hi,

Had same problem with upgrading named on CentOS 4.4.

Just copy the named.conf.rpmsave to your named.conf (/etc) and you will be fine.

Franky
 
If the above doesn't work do the following:

create a new file called dns_write_post.sh in /usr/local/directadmin/scripts/custom

write the following content into the file and save:

cd /var/named/
mv /var/named/$DOMAIN.db /var/named/chroot/var/named/$DOMAIN.db
ln -s /var/named/chroot/var/named/$DOMAIN.db $DOMAIN.db
Click to expand...

Now next time DA adds a domain, it will be moved to the new directory and a symlinks for DA will be created. :)

when done, do chmod +x dns_write_post.sh to make the file executable.

note: when deleting a domein it does NOT delete the domain file in the new directory ( chroot. ) you have to do this manually. if anyone has a better workaround please let us know.
 
Last edited:
pls stop the "i can fix that for low fee" guys.
if someone likes to pay they would go to some certified guys and have it fixed . . cmon guys we're a community forum and not a money making bussiness .. keep it real pls.

Just copy your old named.conf back to the right place, what happends is that bind may or may not run chrooted .. this usually happends after updating bind.

Greetings
 
To stop BIND from running chroot, edit the /etc/sysconfig/named file.

comment out any lines beginning with:

ROOTDIR=

and save and restart BIND.

Then all will be good and BIND won't run chrooted anymore.

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