PDA

View Full Version : Newly created domain not working



gcypher
06-28-2005, 05:29 AM
Hi
i am having this trouble for over a week, i looked all over the place but in the end i ended up more confused then i already was!

the problem is i have a DA server up and running on FC3.
At the moment 18 domains are running ok !! but any new domain i make at my registrar and assign my nameserver to it it will not function not in a million years, i tried the tool on dnsstuff.com
and resulted i have lame nameservers ... (but not on all my domain) just the ones who arent working such as:
apuestayganaras.com
lugenet.com

i hoped you guys can help me out here .. bcause i already gave up !

Gr
M.Franco

nobaloney
06-28-2005, 08:18 PM
Please give us some sample domains to work with.

Jeff

gcypher
06-29-2005, 06:23 AM
hello guys these are some sample for you to work with
apuestayganaras.com
apuestayganaras.net
lugenet.com

those are new added domains (since 1 week orso) they wont work at all and give errors,

fast-xs.net is the domain who provides the dns for the domains listed above. (which should be ok domain)

Gr

gcypher
06-29-2005, 03:43 PM
ok my problem is solved i have been another 12 hrs busy discovering where the hell this came from.

This is what happend:
Normally after creating a new domain on directadmin it will modify /etc/named.conf but also will create a zone file in
/var/named/[zone_file], which will end up being a symbolic link to the real zone file under
/var/named/chroot/var/named/

so in this case what happend is that after adding a new domain into DA it will put a link in /var/named but no zone file into /var/named/chroot/var/named/

how could this happen .. there was no modification made neither on dns nor the server. just from one moment till the other this problem has been a pain in the ass!!

i am sorry if my english is poor but i hope this helps ..
can it be my provider (of dedicated server) needed some money and did this to me or how ???


Gr
M,Franco

Titam
06-29-2005, 08:56 PM
I have the same problem, sometimes, for no reason. I'm running on FC3 too. I just delete and re-create, delete and recreate, and 1 times, that will work, for no reason too

gcypher
06-30-2005, 03:14 AM
but the weird thing is .. that something has been changed because i never tuuched the bind setup orso .. so what could have happended ???


i still believe my hosting isp needed some money and tried to bitch me up

nobaloney
07-01-2005, 04:55 PM
It would seem to me that a dedicated server company would want to keep your business, so it would be in their interest to do it right.

I haven't been using any OS distributions with chrooted bind, but this is about to change, so I don't know how DA does it.

I'll bring your post to their attention.

Jeff

DirectAdmin Support
07-01-2005, 06:31 PM
Hello,

When our install script installs bind, it will then check for a /etc/sysconfig/named file. If it exists, it check for a shell variable called ROOTDIR (I believe). If that variable exists, the install script will put a # character in front of it, resulting in #ROTDIR=/var/named/chroot/var/named, so that named starts it's not rooted. What might be happening, is if bind is updated or reinstalled, the /etc/sysconfig/named file is being reset to have the ROOTDIR variable set, thus messing up named.

So check your /etc/sysconfig/named file, and comment out any ROOTDIR variables by adding a # in front of it, then restart named.

John

gcypher
07-01-2005, 07:00 PM
Great this all sorts it all out for me !
now i can straighten this thing up! so bind will work correctly from directadmin (adding subdomains or anything) ..

thanks for all the effort !!

nobaloney
07-03-2005, 05:27 PM
John,

Nothing wrong with running BIND chrooted.

The following is NOT a change I'm going to make on our servers, but something you might consider for the future:

How about checking when installing DA, and if bind is set to run chrooted, create a link at /etc/named.conf to the location of the chrooted file.

Wouldn't this work with DA and still allow us the (perhaps overrated, perhaps not) security of a chrooted BIND?

Thanks for the consideration.

Jeff

nhack
07-07-2005, 09:55 AM
Hola, creo que tenemos el mismo problema, yo he cambiado mi dominio www.ghansa.com por www.nicared.com y ahora no me funcionan y no se que tengo que hacer.

Les agradeceria si me respondieran.

jmstacey
07-07-2005, 12:56 PM
Esté por favor enterado que utilicé un traductor para esto tan allí puedo ser errores. Respondí a su otro poste. Soy confuso en cuanto a su problema. En su otro hilo de rosca usted dice que usted cambió el nameserver, pero este hilo de rosca está mirando crear de nuevos dominios, no cambiando los nameservers.

gcypher
07-07-2005, 03:47 PM
ola amigo si nos puede decir ke OS usas y se la as actualizado alguna vez


si puede ser ponla en ingles para ke otra gente nos entiende

saludos !!

gcypher
08-09-2005, 06:40 AM
hi guys

so if i am right then every time we update fedora BIND we will need to edit its configs and comment some lines out ???



Regards