1

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.

Kiran Kotturi
  • 211
  • 4
Tushar
  • 133
  • 1
  • 7
  • 1
    Is: "Learn how wildcards work" a valid answer for you? Because you expect things to work that are explicitly not working by standards. – TomTom Jan 23 '23 at 09:55
  • @TomTom Not sure. If one only knew how it worked, there wouldn't be this question. – Tushar Jan 24 '23 at 08:34
  • 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. – TomTom Jan 24 '23 at 09:30

1 Answers1

4

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.

Romeo Ninov
  • 5,263
  • 4
  • 20
  • 26