Then asterisk will only try to resolve nothing.everything.local, and for example, not nothing.everything.local.example.com, like the underlying operating system would. While the workaround for this is easy, this causes confusion, especially in kubernetes environments. This way, the registrartion will be shown as rejected, while asterisk just couldn't resolve the domain properly, while everything else in the system could.
Relevant log output
No response
Asterisk Issue Guidelines
[X] Yes, I have read the Asterisk Issue Guidelines
Severity
Trivial
Versions
20.5.0
Components/Modules
Tested in pjsip, but probably an issue everywhere else
Operating Environment
Fedora 38
Frequency of Occurrence
Constant
Issue Description
As the title says. Suppose you have a resolv.conf:
And an asterisk config snippet like:
Then asterisk will only try to resolve nothing.everything.local, and for example, not nothing.everything.local.example.com, like the underlying operating system would. While the workaround for this is easy, this causes confusion, especially in kubernetes environments. This way, the registrartion will be shown as rejected, while asterisk just couldn't resolve the domain properly, while everything else in the system could.
Relevant log output
No response
Asterisk Issue Guidelines