Search results

No the server would keep working, at least the services like websites and mail etc.. You might loose access to the panel when you don't pay, but that is easily restored after paying again. What I mean with the pause option is the following. At this moment you have a lifetime license. If you...

Name me 1 reason why. Because I can name you a couple of reasons why it's not. Starting with teaching people the wrong way, lot don't even know how to set up a hostname correctly and then come complaint that they have mail issues, which we almost had not in the early days. Otherwise I wouldn't...

So no change at all. As this is also possible at this moment already since da uses an SSL based on the ip. That's why it's called the (for example) 65.21.61.62-da.direct as hostname. So this way you can already directly visit your server via SSL by the hostname. So this is already implemented...

That would most likely be from the filter.conf from Spamassassin. Normally that is like line 4 of the filter.conf, but maybe additions were made. The filter.conf can be found in the /etc/virtual/domain-tld/ directory. Normally created by Spamassassin configuration settings in the user account...

No not at all. These are just idea's posted here.

I agree with your thoughts. This is something we also have spoken about in the first older thread where idea's were given. Just 1 question. If it's not about the money (for most it is), then why not convert your license and then for 180/year you have a full modern license? Or is that giving you...

My bad, sorry! I was too enthousiastic and so thus fast. I overwritten everything and forgotten that I renamed the longer binary name to just directslave, so the older version was started again.:rolleyes: The 3.5.1 is working perfectly. Thanks a million @roman_m for fixing it!! (y) (y)

Sorry, I will report back soon, seems 3.4.3 was still running. Edit: Confirmed, 3.5.1. is working as a sunshine, perfectly!!

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...