setting up help DA

wazburn · Dec 2, 2011

SeLLeRoNe said:
Try

Code:

chown named:named /var/named/gorihosting.com.db

then try restart named.

Regards

same error result

Code:

[root@server ~]# tail /var/log/directadmin/error.log
loading "gorihosting.com" from "/var/named/gorihosting.com.db.temp" class "IN"
zone gorihosting.com/IN: NS 'ns1.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: NS 'ns2.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: not loaded due to errors.

2011:12:02-04:42:20: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-04:42:20: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.
2011:12:02-06:03:53: ConfigFile::writeFile(/usr/local/directadmin/data/users/admin/ftp.passwd) : Timestamp from when it was read is different, overwriting anyway
2011:12:02-06:03:53: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-06:03:53: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.

in Directadmin panel , this might a lil help
admin » DNS Administration » Entry for gorihosting.com

Code:

ftp	A	208.94.244.194	
gorihosting.com.	A	208.94.244.194	
localhost	A	127.0.0.1	
mail	A	208.94.244.194	
ns1.gorihosting.com.	A	208.94.244.195	
ns2.gorihosting.com.	A	208.94.244.196	
pop	A	208.94.244.194	
smtp	A	208.94.244.194	
www	A	208.94.244.194	
gorihosting.com.	NS	ns1.gorihosting.com.	
gorihosting.com.	NS	ns2.gorihosting.com.	
mail	MX	10	
gorihosting.com.	TXT	"v=spf1 a mx ip4:208.94.244.194 ~all"	
localhost	AAAA	::1

SeLLeRoNe · Dec 2, 2011

Try remove from DA Panel the DNS for this zone and re-add (always from DA Panel) (not the reset as you did before).

Regards

wazburn · Dec 2, 2011

SeLLeRoNe said:
Try remove from DA Panel the DNS for this zone and re-add (always from DA Panel) (not the reset as you did before).

Regards

admin » DNS Administration » Entry for gorihosting.com

removed

ns1.gorihosting.com. A 208.94.244.195
ns2.gorihosting.com. A 208.94.244.196

and readded it again,
restart named
restart directadmin

tried also restarting using DA panel's restart option. still no dice.

tail /var/log/directadmin/error.log

Code:

 tail /var/log/directadmin/error.log
loading "gorihosting.com" from "/var/named/gorihosting.com.db.temp" class "IN"
zone gorihosting.com/IN: NS 'ns1.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: NS 'ns2.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: not loaded due to errors.

2011:12:02-04:42:20: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-04:42:20: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.
2011:12:02-06:03:53: ConfigFile::writeFile(/usr/local/directadmin/data/users/admin/ftp.passwd) : Timestamp from when it was read is different, overwriting anyway
2011:12:02-06:03:53: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-06:03:53: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.

In DA's DNS entries I guess it shows the correct content but why it the error log reports as it doesn't know it??

SeLLeRoNe · Dec 2, 2011

No, i mean remove all the zone.

Regards

wazburn · Dec 2, 2011

SeLLeRoNe said:
No, i mean remove all the zone.

Regards

from DA
admin » gorihosting.com » DNS Settings
I tried deleting all but this give me:

Code:

Cannot Delete those NS records

Details

Deleting them will leave you with 0. You must have more than 0 NS records or named may not start.
Add the new NS records first.

I tried to leave "FTP" and delete all still give me same result. other way around?

scsi · Dec 2, 2011

You dont have to delete it you just have to repair it.

Type:

/usr/sbin/rndc reload

Then:

tail -25 /var/log/messages

Then you will see what the zone error is so you can fix it.

Then you can manually edit /var/named/gorihosting.com.db and fix the error.

wazburn · Dec 2, 2011

scsi said:
You dont have to delete it you just have to repair it.

Type:

/usr/sbin/rndc reload

Then:

tail -25 /var/log/messages

Then you will see what the zone error is so you can fix it.

Then you can manually edit /var/named/gorihosting.com.db and fix the error.

Thanks for jumping in, these are the results im lost to repair .db here:

Code:

[root@server home]# tail -25 /var/log/messages
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'dlv.                                   isc.org/DNSKEY/IN': 2001:4f8:0:2::20#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'dlv.                                   isc.org/DNSKEY/IN': 2001:500:60::29#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'dlv.                                   isc.org/DNSKEY/IN': 2001:500:71::29#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'ns2.                                   isc.ultradns.net/AAAA/IN': 2001:503:231d::2:30#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'ns.i                                   sc.afilias-nst.info/A/IN': 2001:500:6::79#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'pdns                                   4.ultradns.org/A/IN': 2001:500:e::1#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'pdns                                   5.ultradns.info/AAAA/IN': 2001:500:1a::1#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'pdns                                   6.ultradns.co.uk/AAAA/IN': 2001:500:2f::f#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'pdns                                   5.ultradns.info/AAAA/IN': 2001:500:19::1#53
Dec  2 12:10:23 server named[23767]: error (network unreachable) resolving 'pdns                                   6.ultradns.co.uk/A/IN': 2001:502:4612::1#53
Dec  2 12:14:28 server proftpd[5434]: 208.94.244.194 (::ffff:151.16.96.241[::fff                                   f:151.16.96.241]) - FTP session opened.
Dec  2 12:14:29 server proftpd[5434]: 208.94.244.194 (::ffff:151.16.96.241[::fff                                   f:151.16.96.241]) - FTP session closed.
Dec  2 12:52:37 server named[23767]: received control channel command 'reload'
Dec  2 12:52:37 server named[23767]: loading configuration from '/etc/named.conf                                   '
Dec  2 12:52:37 server named[23767]: reading built-in trusted keys from file '/e                                   tc/named.iscdlv.key'
Dec  2 12:52:37 server named[23767]: using default UDP/IPv4 port range: [1024, 6                                   5535]
Dec  2 12:52:37 server named[23767]: using default UDP/IPv6 port range: [1024, 6                                   5535]
Dec  2 12:52:37 server named[23767]: using built-in trusted-keys for view _defau                                   lt
Dec  2 12:52:37 server named[23767]: using built-in trusted-keys for view _meta
Dec  2 12:52:37 server named[23767]: set up managed-keys.bind meta-zone
Dec  2 12:52:37 server named[23767]: the working directory is not writable
Dec  2 12:52:37 server named[23767]: zone managed-keys.bind/IN/_meta: (other) re                                   moved
Dec  2 12:52:37 server named[23767]: reloading configuration succeeded
Dec  2 12:52:37 server named[23767]: zone managed-keys.bind/IN/_meta: loaded ser                                   ial 355
Dec  2 12:52:37 server named[23767]: reloading zones succeeded

scsi · Dec 2, 2011

That looks to be fine now.

I dont see any errors.

SeLLeRoNe · Dec 2, 2011

i see an error on resolve, so maybe is in

Code:

/etc/resolv.conf

one error

and one here:

Code:

Dec  2 12:52:37 server named[23767]: the working directory is not writable

For this should work

Code:

chmod 750 /var/named

SeLLeRoNe · Dec 2, 2011

ok scsi have for sure more experience then me, so, it should be fine.

scsi: does named have to be listening on external ip aswell? On the netstat he posted before seemed that named was listening just on localhost.

telnet on port 53 is now working so you should be ok now...

wazburn · Dec 2, 2011

scsi said:
That looks to be fine now.

I dont see any errors.

SeLLeRoNe said:
ok scsi have for sure more experience then me, so, it should be fine.

scsi: does named have to be listening on external ip aswell? On the netstat he posted before seemed that named was listening just on localhost.

telnet on port 53 is now working so you should be ok now...

Thanks guys, just my concern now why directadmin error log still shows this?

Code:

[root@server /]# tail /var/log/directadmin/error.log
zone gorihosting.com/IN: NS 'ns1.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: NS 'ns2.gorihosting.com' has no address records (A or AAAA)
zone gorihosting.com/IN: not loaded due to errors.

2011:12:02-04:42:20: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-04:42:20: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.
2011:12:02-06:03:53: ConfigFile::writeFile(/usr/local/directadmin/data/users/admin/ftp.passwd) : Timestamp from when it was read is different, overwriting anyway
2011:12:02-06:03:53: Added record ns1.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns1.gorihosting.com.
2011:12:02-06:03:53: Added record ns2.gorihosting.com. A 208.94.244.194 to satisfy gorihosting.com. NS ns2.gorihosting.com.
2011:12:02-11:13:05: Socket write error: fd is connected to a pipe or socket whose reading end is closed.  When this  happens the writing process will also receive a SIG_PIPE signal.  (Thus, the write return value is seen only if  the program catches, blocks or ignores this signal.)

scsi · Dec 2, 2011

My guess is the log entries are old and not of the current time. You must of fixed the problem now.

You could just do:

echo > /var/log/directadmin/error.log

Then see if the errors come back at any time in the log.

Your nameservers are working fine and resolving fine.

scsi · Dec 2, 2011

SeLLeRoNe said:
ok scsi have for sure more experience then me, so, it should be fine.

scsi: does named have to be listening on external ip aswell? On the netstat he posted before seemed that named was listening just on localhost.

telnet on port 53 is now working so you should be ok now...

He must of fixed the netstat thing before I checked it because it was resolving fine.

scsi · Dec 2, 2011

Dec 2 12:52:37 server named[23767]: the working directory is not writable

This error can be ignored...its a typical error on freebsd servers. I dont know what OS you are running, but I have the problem on all my freebsd nameservers. It has to do the the way the source code of named is in /usr/src

wazburn · Dec 2, 2011

scsi said:
My guess is the log entries are old and not of the current time. You must of fixed the problem now.

You could just do:

echo > /var/log/directadmin/error.log

Then see if the errors come back at any time in the log.

Your nameservers are working fine and resolving fine.

after echo and checked log, shows clear now.

scsi said:
This error can be ignored...its a typical error on freebsd servers. I dont know what OS you are running, but I have the problem on all my freebsd nameservers. It has to do the the way the source code of named is in /usr/src

I used centos 6, forgot to mention.

Guys after almost a week of trial finally!,, THank you so much!

setting up help DA

wazburn

Verified User

SeLLeRoNe

Super Moderator

wazburn

Verified User

SeLLeRoNe

Super Moderator

wazburn

Verified User

scsi

Verified User

wazburn

Verified User

scsi

Verified User

SeLLeRoNe

Super Moderator

SeLLeRoNe

Super Moderator

wazburn

Verified User

scsi

Verified User

scsi

Verified User

scsi

Verified User

wazburn

Verified User