DNS unresolved?

C

cmelcher

Verified User
Joined
Sep 16, 2005
Messages
27
I have a DNS problem.

I created a new account on direct admin for a .net domain last Friday.

The domain was purchased though GoDaddy, and the nameservers for my server were entered (ns1.webtechia.com and ns2.webtechia.com)


If I do a whois search on the domain, I can find the entry, and it does say ns1.webtechia.com and ns2.webtechia.com

However, if I try to ping the .net domain, it cannot resolve the name to the IP address. I've tried restarting named through the CP, but I had no luck.

Now, I realize it takes a bit for the DNS info to propagate across the network, but it's been about 5 days. Any idea why it's not resolving? Does directadmin handle .net domains differently?

Thanks for any help
 
You said that ns1.webtechia.com and ns2.webtechia.com was the correct DNS for your domain skarate.net ?

Well either NS1 or NS2 has a zonefile for skarate.net

You can just check by using host in unix/linux ex: host skarate.net ns1.webtechia.com answer:

$host rskarate.net NS1.WEBTECHIA.COM
Using domain server:
Name: NS1.WEBTECHIA.COM
Address: 204.11.33.49#53
Aliases:

Host rskarate.net not found: 2(SERVFAIL)

This usualy means that the DNS apointed for your domain has no zone file activated for it.
 
Well, I solved the problem and I thought I'd post it here for everyone's benefit.

The first time I checked the DNS files everything appeared to be as it should be.

Later when I was at home, I checked them again. This time, I used putty to log in. When I checked the files, I noticed that the rskarate.net.db file was a different color than the rest. I used file to inspect it and it appears the rskarate.net.db file was an ASCII file while the rest were symbolic links to the /var/named/chroot/var/named directory

I went in /var/named/chroot/var/named and copied on of the files from a different name into a file named rskarate.net.db (I, of course, edited that file to replace the old domain with the new one)

Then, I deleted the ASCII file at /var/named and replaced it with a symbolic link to the other.

After doing a host, everything appeared ok. I checked my browser and it appeared as it should.

Now, I'm not 100% sure how DirectAdmin is set up, but it looks like it was some sort of a permissions problem.

I'm just curious why DI made an ASCII file for that specific domain while it created a link for the others? Any ideas? I'm just curious so I don't have to do this for every .net domain I create.
 
Oh no, now DirectAdmin is doing this for all new domains created.

Every single domain it creates doesn't work. I have to manually log in as root and correct it.

Any idea what could have triggered this or how to fix it? It kinda defeats the purpose of the software if I have to fix every domain it creates.
 
Yes.

What's happened is that your OS has updated your DNS program to use a chrooted directory. DA doesn't directly support that.

The easiest way to fix it is to edit the /etc/sysconfig/named file.

The comment out any lines that begin with Rootdir=.

Then restart BIND.

On CentOS:
Code: 
# service named restart
Jeff
 
Then, the solution is to comment the ROOTDIR line?

Then the named will work as not chrooted, right?
 
You must log in or register to reply here.
Back
Top