AdguardTeam/AdGuardHome

Using AdGuard Home along with dnsmasq for local hosts name mapping

Open

#3,063 opened on May 3, 2021

View on GitHub
 (6 comments) (0 reactions) (0 assignees)Go (2,333 forks)batch import
compatibilitydocumentationhelp wanted

Repository metrics

Stars
 (34,000 stars)
PR merge metrics
 (No merged PRs in 30d)

Description

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!

Contributor guide

Research direction
Investigate DNS search domain configuration and how AdGuard Home handles unqualified names compared to dnsmasq.
Tech stack
go
Domain
backend
Issue type
Research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-3 hours
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
DNS basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
75