AdguardTeam / AdguardTeam/AdGuardHome

Adguard doesn't resolve any address - FreeBSD/ports/raspberry pi/etc

Aperta
#6,500 43 commenti 0 reazioni 1 assegnatario Assegnata a @Mizzick Vedi su GitHub
compatibility needs investigation
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) and found no answer

- [X] I have searched other issues and found no duplicates

- [X] I want to report a bug and not [ask a question or ask for help](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a)

- [X] I have set up AdGuard Home correctly and [configured clients to use it](https://github.com/AdguardTeam/AdGuardHome/wiki/Clients). (Use the [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions/categories/q-a) for help with installing and configuring clients.)

### Platform (OS and CPU architecture)

FreeBSD, ARM64

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

v0.107.41/v0.107.42/v0.107.43/v0.107.44/v0.108.0-b.49/v0.108.0-b.51

### Action

In the past, I've used Adguard on a PI4B before without any issues (via Debian/Raspian). Now, as adguard provides FreeBSD versions I've installed FreeBSD 14 onto the SD card - which is currently v14.

That installation went fine and whether I install AG via the ports or by the guide provided by AG, it does NOT seem to work as intented to my clients. I have mutliple VLANS, which all was setup via rc.conf - that shouldn't make difference to my setup.

But no matter what, even after a reboot of the adguard device - NOTHING seems to be able to resolve DNS addresses. I thought it was some issue with sysctl, but I don't think it is. This is causing outages by the adguard device, but I can't work out why.

For a test on the PI itself, I installed unbound and configured it to forward queries (same as AG to the same forwarders) - and it worked completely fine. So the issue is completely with Adguard - even looking at the webpage it claims the request was "processed" when it actually wasn't.

If you need more info, please don't hesitate to ask.

### Expected result

I expect DNS results to be passed onto the client

### Actual result

Nothing passed onto the client, so therefore the device just hung

### Additional information and/or screenshots

_No response_

Edit: Updated versions which still have the issue

Guida per i contributori

Apri la guida per i contributori

Valutazione

Questa issue non è ancora stata valutata.

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.