Score:1

IIS: Multi level subdomain with wildcard not resolving

se flag

Let's say I have a website - example.com. If I create a binding in IIS, with *.example.com then abc.example.com works.

However, abc.in.example.com doesn't work. It gives me 404 status code.

Any suggestions.

cn flag
Is: "Learn how wildcards work" a valid answer for you? Because you expect things to work that are explicitly not working by standards.
Tushar avatar
se flag
@TomTom Not sure. If one only knew how it worked, there wouldn't be this question.
cn flag
Yeah, but rtfm is not really optional. It is clear in any documentation i ever read that wildcards are ONE LEVEL ONLY and do not extend downwards.
Score:4
in flag

This is how wildcard certificates work. *.example.com work only for hosts like: host1.example.com, host2.example.com, etc.

If you want to have it work for abc.in.example.com you need to use certificate for *.in.example.com

The same is situation with binding to wildcard hosts.

Tushar avatar
se flag
Thanks @RomeoNinov for your answer. That worked for me.
Romeo Ninov avatar
in flag
@Tushar, if you are happy with my answer feel free to accept it (tick on the left side of the answer) :)
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.