Unbound crashes if I add a wildcard record

[Jyling]

I add *.domain.com, and Unbound goes tits up.
I remove this record, and it starts up.
Anything can be done about this?

[meyergru]

Works fine for me. Added *.domain.com -> 1.2.3.4 as override. Unbound restarts fine and responds with 1.2.3.4 to an nslookup aaa.domain.com.

[Jyling]

Good to know, but this does not help me. The crash is 100% reproducible: add a wildcard - it crashes and fails to restart. Remove the wildcard - it restarts. This is not something that users should discuss among ourselves but rather something that dev team should become concerned about.

[meyergru]

I did not discuss it, I merely gave another data point saying: Nope, not happening here. If you want to catch the developer's attention, you better create a bug report on Github with a repeatable configuration or steps to reproduce the bug. This is a user's forum.

As I said, I cannot reproduce the bug the way you describe it, so probably it is something specific to your configuration. Unless you can point to something more exact, the problem will not be fixed. That is something you could have figured out if you thought about what I wrote.

And maybe you do not want to discuss it, but I will tell you anyway what your exact problem is:

You created a *.domain.com override on top of something pre-existing like aaa.domain.com. It is exactly with this configuration that Unbound crashes. Use only one or the other and it magically works. And no, I do not want to discuss that this may not be what you want to achieve (namely, a fallback for any unspecified name in the domain, while maintaining specific overrides). If it is so, file a bug. Now you now what to specify in a bug description and why it would be nice to have it fixed, not an unspecific, irreproducible complaint.

You are welcome.

[Jyling]

It is exactly with this configuration that Unbound crashes

The definition of the problem. A crash from user input that has not been rejected for being in valid is a disgrace for any developer.

By the way, you are sounding too defensive and aggressive, for a user. Have a horse in this race?

[meyergru]

Sure - especially for the Unbound developers. And since there still is no bug report for either OpnSense or Unbound, this disgrace will haunt them forever, although unbeknowst to them. I thought you did not want to discuss this between us users?

No, I am just pissed off because this will lead nowhere. BTW: You sound pissed because of a simple bug. These things happen, you know?

[Jyling]

I am just pissed off because this will lead nowhere.

And you believe that it allows you to lash out at strangers? Hmm.

This is not a trivial issue. This is huge. Unbound simply goes tits up, having been given a valid DNS entry. This is bizarre. This is disgrace. Oh, and by the way, it turns our that this issue EXISTS. Surprise, surprise!

https://github.com/opnsense/core/issues/8051

As to this likely going nowhere, your assessment is probably spot-on: no one gives.