AdguardTeam / AdguardTeam/AdGuardHome

DNS Rewrites issue

Offen
#5,457 43 Kommentare 3 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen
waiting for data
Vorherrschende Sprache
TypeScript
Sterne
36.9k
Forks
2.5k
PR-Merge-Kennzahlen
Keine gemergten PRs in 30 T.

Beschreibung

### Prerequisites

- [X] I have checked the [Wiki](https://github.com/AdguardTeam/AdGuardHome/wiki) and [Discussions](https://github.com/AdguardTeam/AdGuardHome/discussions) 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

### Operating system type

Linux, Other (please mention the version in the description)

### CPU architecture

AMD64

### Installation

Other (please mention in the description)

### Setup

On one machine

### AdGuard Home version

0.107.23

### Description

Hello,

I have migrated from pihole to adguard at my home.

I have purchased domain that in example I will call: domain.com

That domain using cloudflare dns and in cloudflare I pointed it to my public, static IP address that I have from my ISP
In Cloudflare for my domain - proxied records not enabled.

In Adguard (that I have using only for dns in my home network) i have configured domain.com to point to local IP address: 172.17.72.246.

I do that in /etc/hosts on my adguard server.

The idea is if I open domain.com at home to be resolved from 172.17.72.246.

Sometimes (again I telling sometimes) some devices connected to my home network (laptop, phones, tablets etc) got an error to open domain.com because it resolving from my public IP address, NOT from 172.17.72.246 that I have configured in /etc/hosts.

Any idea why that heppening?

Beitragsleitfaden

Beitragsleitfaden öffnen

Bewertung

Dieses Issue wurde noch nicht bewertet.

Neue Issues direkt in Ihr Postfach

Eine kurze Übersicht über anfängerfreundliche GitHub-Issues.