Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add support for ndots to unbound resolver #37

Open
1 task done
lgyurci opened this issue May 17, 2024 · 1 comment
Open
1 task done

Add support for ndots to unbound resolver #37

lgyurci opened this issue May 17, 2024 · 1 comment

Comments

@lgyurci
Copy link

lgyurci commented May 17, 2024

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:

search anything.something.example.com something.example.com example.com
nameserver 10.0.0.1
options ndots:4

And an asterisk config snippet like:

[reg1]
type=registration
transport=transport-udp
client_uri=sip:[email protected]
server_uri=sip:[email protected]

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

  • Yes, I have read the Asterisk Issue Guidelines
@seanbright
Copy link

libunbound ignores those settings. We would have to implement this behavior ourselves.

@jcolp jcolp transferred this issue from asterisk/asterisk May 21, 2024
@jcolp jcolp changed the title [bug]: Asterisk ignores ndots option in resolv.conf Add support for ndots to unbound resolver May 21, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants