domain does not resolve

[rldev]

Hello Folks,
I am having a strange problem in DA. I recently had a domain transferred over to my DA server. It works fine by ip, but does not work via dns. The domain is va-democrats.com . I can not ping it locally on the server or anywhere outside the network. The name record is present and looks fine. The user just transfered this domain over. I am stumped.

 

[rldev]

The problem is that DA is not properly setting up new zone files. It creates the zone file file in /var/named instead of /var/named/chroot/var/named/ and then a symlink. It also does not give the proper permissions to the zone file. Hence it does not work unless I manually make the corrections. I can not be certain this happened when I upgraded to 1.263.

I also opened a ticket with DA about this.

 

[Seth]

I also have this issue on one of our DA setups. Did you get a fix from support?

 

[nobaloney]

Gentlemen please post your OS distribution to help debug this.

Jeff

 

[Seth]

Fedora 4

 

[DirectAdmin Support]

Hello,

DA never sets files to go into /var/named/chroot/var/named... (unless you tell it to).

If "named" get's updated, the rpm update will move everything from /var/named/* to /var/named/chroot/var/named/* and then link everything back to /var/named/*.

Same goes for the /etc/named.conf. It's moved to /var/named/chroot/etc/named.conf... but by the named update script.

If named gets updated and this happens, then you have to edit /etc/sysconfig/named and remove the:
ROOTDIR=/var/named/chroot
option so that named is not chrooted (then restart named). Everything should work ok even with the files moved over becaue of the links.


** If you actually do want to run named in a chroot environment, you'd have to change several things.

1) /usr/local/directadmin/conf/directadmin.conf. Change

namedconfig=/etc/named.conf
nameddir=/var/named

to

namedconfig=/var/named/chroot/etc/named.conf
nameddir=/var/named/chroot/var/named

2) You'd need to change the template around a bit.
/usr/local/directadmin/data/templates/zone.conf
Move it to the ./templates/custom/zone.conf directory first, then edit the custom file to read:

zone "|DOMAIN|" { type master; file "[b]/var/named[/b]/|DOMAIN|.db"; };

Basically, just to remove the token so that the full chroot path isn't added.

That should be about it.. remember to restart directadmin after changing your named.conf.



John

 

[Seth]

Thanks again John