Search results

Oeps, my mistake. I've overwritten all the files but forget that I renamed the binary to just directslave. I will do a new test and report back.

I hope so... For some reason the special version @fln gave me does not stay either unfortunately. Somehow it gets automatically updated to the normale 1.690 version on both servers, while autoupdate in directadmin.conf file is off.

Fix is not correct, just tested it and it's not working with deletion.

@roman_m Unfortunately it is not fixed. I just tested with Directadmin 1.690 and could create a user with a testdomain. Then I tested adding A and TXT record, which went fine. Tested removing A record and change of TXT record. Also went fine. As a last test I tested the removal of the user...

Thank you very much. I wrote you a mail about the web interface. Also yesterday I discovered an issue where I had change DS to another directory and restarted (both DS and named) but it still used the /etc/namedb/secondary directory. Only after I added a trailing / after the new directory and...

That's great! Thank you very much Roman!

Yep he contacted me too looking for access to a server and a DS server. I'm afraid I can't give that because servers is not mine. But since we discovered the issue we might be able to help him anyway.

Well I don't have nGinx, only Apache and that one has mod_evasive, but once I used the above it gone quiet on the servers so filtering via user-agent this way does help. And not only in my case. I handed out that Chrome block below 100 solution and worked for many others. Luckily we haven't...

You're welcome. Well... I haven't seen bad bots before this year not stating their user agent. They probably are not bots but probably rather a bot net which uses these older Chrome versions. Those Chrome attacks came from tens of thousends of different unique ip's even more than 100K as some...

Yep, I had another more recent thread about it here (click). But I also discovered, especially on phpBB forums there was a wide spread attack of bots which did not identify as such, but used older Chrome versions, older than v100. So I added these to my bad bot list and blocked all of the...

Thank you for checking the difference for us. I just had time to check special DA 1.690 build version you suggested and I can confirm that with that special version, everything in Directslave is working as designed again. Creating domain, adding records and deleting domain is working again...

You can remove that line, it's obsolete. Seemed on my Directslave after removing that line, at least creating and deleting after this went fine in 1.689 (not 1.690) Updating (even with the multi-server task.queue command) did not change anything in either version. So the same issue we are also...

@DrWizzle Did you posted (and removed the post) that you experienced the same issues with DS and 1.690? If yes it's important to mention it.

Yep and on Alma 8 which I'm using on the DS server.

Ah personal plus license then. If it's a new installation then you're entitled to ticket support. Otherwise I hope somebody of devs here will fix it for you.

It's decreated as from Bind 9.16 but was still working. It was fully removed from 9.18. Anyway I can confirm it's a 1.690 issue as also with the other server on 1.689 it works flawlessly with creating and deleting. But on changing records it does not. So might still be something else.

So are you co-admin or do you mean you have a lifetime/legacy license? Because Debian 13 is not supported with legacy licenses.

@reonhoub2 do you have the dnssec-enable yes; option in any of your /etc/named.conf files? Edit: Also check if you change records. On 1.689 creating and deleting works fine but changing records doesn't work.

My previous post is due to the editting a bit unclear. The non creation of .db files on the DS slave was my fault and is fixed. Tested with 1.690, problem occurs, line and .db is added but on removal no erros on the DS servers. Tested with 1.689 looks like everything is working as designed after...

@exlhost have dnssec-validation yes; in my Directadmin, but I just checked and looks I do stil have dnssec-enable yes; in named.conf of the Directslave server. That did not give issues before. I now removed that line from the DS server and restarted named. Now it only has dnssec-validation auto...