AdguardTeam / AdguardTeam/AdGuardHome

Using AdGuard Home along with dnsmasq for local hosts name mapping

Aperta
#3,063 6 commenti 0 reazioni 0 assegnatari Vedi su GitHub
compatibility documentation help wanted
Lingua principale
TypeScript
Stelle
36.9k
Fork
2.5k
Metriche di merge delle PR
Nessuna PR unita negli ultimi 30g

Descrizione

Hi,

I just installed in my raspberry AdGuard home and so far I'm very satisfied. I just noticed a weird behavior comparing with my previous setup which was using dnsmasq as DNS caching and DHCP server.

I was using expand-hosts option to resolve some local clients using unqualified names instead of their IP. For example, I was able to ping a host using just a simple name (i.e. test) instead of its IP.

When I installed AdGuard I changed my setup of dnsmasq to do only IP-->hostname mapping to my local network hosts and setup accordingly the AdGuard (using the dnsmasq IP as upstream).

While I'm able to ping everything as before (using just a name) from my windows PC I have to add the "." suffix in order to find the host. For example

`ping test. `
instead of
`ping test`

I didn't have to do the same with dnsmasq and I'm wondering why.

Any idea?

Thanks in advance!

Guida per i contributori

Apri la guida per i contributori

Direzione di ricerca

No files, tests, or entry points are mentioned. Reproduce the AdGuard Home, dnsmasq, and Windows setup described in the report, then inspect the DNS behavior for unqualified and fully qualified local hostnames. Done means explaining the difference and identifying whether a configuration change or product fix is needed.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Valutazione

Stack tecnologico
raspberry-pi
Ambito
networking
Tipo di issue
Bug
Difficoltà
4/5
Tempo stimato
3-5 giorni
Stato di attività
Ferma
Chiarezza
Da chiarire
Idoneità per principianti
20/100

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.