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

Addon DNS #268

Closed
Danny89530 opened this issue Jul 26, 2023 · 15 comments · Fixed by #275
Closed

Addon DNS #268

Danny89530 opened this issue Jul 26, 2023 · 15 comments · Fixed by #275

Comments

@Danny89530
Copy link
Contributor

Hi @TECH7Fox,
I am trying to configure the Asterisk addon in order to set up the trunk for Telecom Italia's VoIP service.

Everything seems to be working, as long as I manually modify the resolv.conf file inside the addon's shell, inserting Telecom's DNS.

On my HomeAssistant instance, I already have the AdGuard addon installed for some time. However, it seems to be completely ignored, as I still see the addon pointing to the server's IP instead of the container's IP.

What am I doing wrong?

Thank you in advance.

@felipecrs
Copy link
Collaborator

felipecrs commented Jul 26, 2023

AFAIK AdGuard add-on isn't taken into account as DNS server for other add-ons.

One thing you can try to do is to set the DNS in the Asterisk config files:

https://wiki.asterisk.org/wiki/display/AST/Asterisk+20+Configuration_res_resolver_unbound

; /config/asterisk/custom/resolver_unbound.conf

[general]
nameserver = 127.0.0.1
resolv =

Theoretically it should make Asterisk use your AdGuard home as DNS server.

@Danny89530
Copy link
Contributor Author

Hi @felipecrs,

Thank you for your response. Based on the various tests I have conducted, it seems that the module allowing the use of that specific configuration has not been compiled into the Docker image of the addon.

In reality, my hope was that it could be implemented in the future so that we can manually insert a custom DNS configuration.

@felipecrs
Copy link
Collaborator

Hm... that could be the case. PRs are welcome if you happen to figure it out.

@Danny89530
Copy link
Contributor Author

I have just submitted the PR #270
I have tested it now without any issues, and I hope you can integrate it soon!

@felipecrs
Copy link
Collaborator

Thank you! It will be released tomorrow :)

@felipecrs
Copy link
Collaborator

@Danny89530 I'm receiving this issue in my logs after #270 released as 4.1.0:

ERROR[512]: loader.c:2524 load_modules: Error loading module 'res_resolver_unbound.so': libunbound.so.8: cannot open shared object file: No such file or directory

Is there a chance you can take a look?

@Danny89530
Copy link
Contributor Author

Hi @felipecrs, I just performed the upgrade, and I just noticed that the "libunbound-dev" library is not installed on the container. I'm checking it right now...

@felipecrs
Copy link
Collaborator

Debian was also upgraded from 11 to 12, maybe it has something to do with it as well.

@Danny89530
Copy link
Contributor Author

I have just tried to compile the Dockerfile separately, not considering the addon. Everything is compiled and installed as it should. Now I am compiling the addon, but I can't figure out why it would skip the installation of the library.

@Danny89530
Copy link
Contributor Author

I'm having trouble understanding what the problem might be.
I just tried running the installation of the library separately using the apt command, but it doesn't seem to be installed according to dpkg. Do you have any ideas?

immagine

@felipecrs
Copy link
Collaborator

Can you change to libunbound8 just to try?

I will take a closer look tomorrow otherwise.

@Danny89530
Copy link
Contributor Author

Unfortunately, nothing has changed.
Even installing libunbound8 directly, it doesn't show up on dpkg during startup.
I am quite puzzled..

@felipecrs
Copy link
Collaborator

Oh, I know what's wrong. You added the dependency on the "build" docker layer. You should in fact add it to the "base" docker layer. Check the apt-get install command before the one you made changes to.

@felipecrs
Copy link
Collaborator

The build layer is intermediary and it's only used to build asterisk from source.

That's why you don't see the dependency after the build.

@felipecrs
Copy link
Collaborator

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

Successfully merging a pull request may close this issue.

2 participants