This is where I am lost, every domain on the server works until I tried to set up jaylandings.com a few weeks ago. If the DNS is working on every other domain, Bind works for every other domain, why all of the sudden, its not working on just one domain. The install on the current box was done less than 6 months ago and it has been working until now. Is this a DA problem or a server problem? All of the domains are on the same server and the only problem is with the one domain. Is this something I need to send to DA support or is it something that can be fixed. It looks more like a problem with DA. The software is supposed to make adding, deleting, and moving domains easy. If the software can not remain stable enough to handle it, do I need to get rid of it and go back to the old fashioned way of handling the hosting? I never had problems before I changed to centos, is it centos or the version of DA for centos that is causing the problems?
All domains work except the newest.
- Thread starter Britt
- Start date
zEitEr
Super Moderator
The particular zone might be misconfigured. It has nothing with DA itself and CentOS.
Did you delete this:
?
Is it mistyped or that's what you have in zone? This should be fixed:
to
Add in named.conf
somewhere before
Run
and restart named. Then reads logs.
Did you delete this:
?
Is it mistyped or that's what you have in zone? This should be fixed:
to
Add in named.conf
Code:
logging {
channel all {
file "/var/log/named/all.log";
severity info;
print-category yes;
print-severity yes;
};
channel debug {
file "/var/log/named/debug.log";
severity info;
print-category yes;
print-severity yes;
};
channel xfer {
file "/var/log/named/xfer.log";
severity info;
print-category yes;
print-severity yes;
};
category xfer-in { xfer; };
category xfer-out { xfer; };
category config { all; };
category default { debug; };
};somewhere before
Code:
options {Run
Code:
mkdir /var/log/named
chmod 700 /var/log/named
chown named:named /var/log/namedand restart named. Then reads logs.
I was just about to point that out too. Unbalanced quotes will prevent the zone from loading. Since recursion is enabled, it will result in a loop and eventually a SERVFAIL.
The info I pasted must have rolled to another line, this is what is in the file:
jaylandings.com. 14400 IN TXT "v=spf1 a mx ip4:70.88.27.217 ~all"
I re-added this line, for some reason, DA is not putting it in on its own:
217.27.88.70.in-addr.arpa. 14400 IN PTR jaylandings.com.
I followed the info in the previous post, after the changes, its still not showing, but there only one reference in the log to the domain:
general: error: zone jaylandings.com/IN: loading master file /var/named/jaylandings.com.db: permission denied
This is the updated jaylandings.com.db file:
$TTL 14400
@ IN SOA ns1.hostingus.com. hostmaster.jaylandings.com. (
2011050500
14400
3600
1209600
86400 )
jaylandings.com. 14400 IN NS ns1.hostingus.com.
jaylandings.com. 14400 IN NS ns2.hostingus.com.
ftp 14400 IN A 70.88.27.217
jaylandings.com. 14400 IN A 70.88.27.217
localhost 14400 IN A 127.0.0.1
mail 14400 IN A 70.88.27.217
pop 14400 IN A 70.88.27.217
smtp 14400 IN A 70.88.27.217
www 14400 IN A 70.88.27.217
jaylandings.com. 14400 IN MX 10 mail
217.27.88.70.in-addr.arpa. 14400 IN PTR jaylandings.com.
jaylandings.com. 14400 IN TXT "v=spf1 a mx ip4:70.88.27.217 ~all"
localhost 14400 IN AAAA ::1
Still need to remove that PTR record. That's out of zone data. It gets ignored.
Have you compared file permissions to the jaylandings and other files that are loading? You may not have access to the file it sounds like.
I am able to replicate that error on my name server by starting named from a non root user, where permissions for the zone file disallow read access for the user, but the user has read write access to the /var/run/named directory. Having r/w access to the /var/run/named directory means named will start and yu get no pid error, but the zone wont load and give a permission denied error. When that zone doesn't load, you get that recursive lookup loop and then a SERVFAIL.
So that's a guess.
Have you compared file permissions to the jaylandings and other files that are loading? You may not have access to the file it sounds like.
I am able to replicate that error on my name server by starting named from a non root user, where permissions for the zone file disallow read access for the user, but the user has read write access to the /var/run/named directory. Having r/w access to the /var/run/named directory means named will start and yu get no pid error, but the zone wont load and give a permission denied error. When that zone doesn't load, you get that recursive lookup loop and then a SERVFAIL.
Code:
@ns1: pwd
/var/run
@ns1: ls -l | grep named
drwxrwxrwx 2 bind bind 512 May 5 22:46 named
@ns1: ls -l /etc/namedb/master/db.example.com
---------- 1 root wheel 565 May 5 22:29 /etc/namedb/master/db.example.com
@ns1: tail /var/log/messages|grep permission
May 5 22:44:45 ns1 named[23030]: zone example.com/IN: loading from master file master/db.example.com failed: permission deniedSo that's a guess.
Its fixed, Thanks!!!!!
http://www.intodns.com/jaylandings.com
It was the file ownership for /var/named/jaylandings.com.db, it was owned by root:root. Once I changed the owner, it came up with no issues.
Which brings up another question, how would DA be able to assign ownership to root for the .db file? It was deleted, redone, deleted, and redone via DA, the only time I hit it using root was to copy it for these posts.