Error writing remote dns zone

M

MtK

Verified User
Joined
Aug 2, 2007
Messages
405
Hey,
I'm getting an error on the errortask.log:
Code: 
Error writing remote dns zone

how can I tell which zone is it, or at least which cluster?
(from the multi-server, all connection tests return OK)


MtK
 
Hello,

Let me know which OS version you're using and I'll compile you a set of pre-release binaries that actually shows the domain being tried.
I've also added more output if the details are blank (like they are above)... meaning it's probably a socket issue, based on how it's coded and results given.

Try the "Test Connection" button with the remote server's checkbox checked, on the Multi-Server Setup page, to confirm it's working.

John
 
DirectAdmin Support said:
Let me know which OS version you're using and I'll compile you a set of pre-release binaries that actually shows the domain being tried.
I've also added more output if the details are blank (like they are above)... meaning it's probably a socket issue, based on how it's coded and results given.
Click to expand...
Code: 
<$> cat /etc/redhat-release
CentOS release 6.2 (Final)

DirectAdmin Support said:
Try the "Test Connection" button with the remote server's checkbox checked, on the Multi-Server Setup page, to confirm it's working.
Click to expand...
MtK said:
(from the multi-server, all connection tests return OK)
Click to expand...
 
DirectAdmin Support said:
Hello,

DA 1.44.0 was released, it will have the new code.

John
Click to expand...
Thanks - Updated!

now the error says:
Code: 
Cluster: Error writing remote dns zone (DOMAIN.COM): (null) (retry=0)
Cluster socket:
but all domains are listed in the error log, so it doesn't really explain the problem.

would it be possible to add the remote server causing the issue?
 
I'm having the same errors in the DirectAdmin logs.
Code: 
"Cluster: Error writing remote dns zone"
"Cluster: socket"

But the zones get transferred to the slave server alright, as I can test them with DIG and see them in the DirectSlave action-log on the slaveserver.

Any advise on a solution to solve the error is welcomed.
 
John, there's no DA present on the slave server as it's just a (2nd) DNS/Nameserver to the Master server.

The few domains that are being listed in the errors have been either removed or added to the Master recently.
So only recent zone changes seem to cause the errors in the Master's DA-errorlog.
 
Hmm.. DA seems to think there is a remote box.

What do you see here?
Admin Level -> Multi Server Setup

If the list is empty, then just make sure that the clustering it shut off completely, to rule out any other issues.

John
 
At the MultiServer setup there's the one entry of the 2nd nameserver.
This has been working nicely for over a year now since forummember RichardG installed DirectSlave for me on the remote DNS-nameserver.

I think something has been altered or broken on the remote server a few months ago when I installed some updates.
Some time later I noticed the DirectSlave-service wasn't running and I think just after when I restarted it, the errors/notices started showing up on the DA-server.

In the meantime I've also started using DA under SSL so that could have something to do with it perhaps.

Usually, with my limited server-knowledge, I would like to dig in a bit and see if I can fix it myself, but I'm not sure if one issue has an impact on the other here.
 
DirectAdmin doesn't officially support DirectSlave. I'd suggest writing the authors or posting to their thread.

Jeff
 
You must log in or register to reply here.
Back
Top