Answer the question
In order to leave comments, you need to log in
How to properly configure binding wildcard in IIS 10?
IIS 10 introduced the ability to use wildcard in binding. Now I set it up like this:
test.com 80
*.test.com 80
If you just leave *.test.com. Then, when accessing test.com, IIS gives 404. In nginx, for example, the construction of the *.test.com type is understood for all domain 3 lvl + root 2 lvl.
How can I solve this problem in one line?
Answer the question
In order to leave comments, you need to log in
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question