Hi there, solution found. It's not a problem of domains and their dns, it's a problem with a Nginx-Setting: I've tried it on the old one of my two vps (old in terms of processor).
It's about this (taken from Nginx-documentation), configured in nginx.conf, see below.
After removing the # from the line (server_names_hash_max_size) it works with value left at 32. Perhaps you could integrate this in Webinoly in any way?
Thanks
Rüdiger
If a large number of server names are defined, or unusually long server names are defined, tuning the server_names_hash_max_size and server_names_hash_bucket_size directives at the http level may become necessary. The default value of the server_names_hash_bucket_size directive may be equal to 32, or 64, or another value, depending on CPU cache line size. If the default value is 32 and server name is defined as “too.long.server.name.example.org” then nginx will fail to start and display the error message:
could not build the server_names_hash,
you should increase server_names_hash_bucket_size: 32
In this case, the directive value should be increased to the next power of two:
http {
server_names_hash_bucket_size 64;
...
If a large number of server names are defined, another error message will appear:
could not build the server_names_hash,
you should increase either server_names_hash_max_size: 512
or server_names_hash_bucket_size: 32
In such a case, first try to set server_names_hash_max_size to a number close to the number of server names. Only if this does not help, or if nginx’s start time is unacceptably long, try to increaseserver_names_hash_bucket_size.
