AdGuard Home's DNS-over-TLS port 853 is not working · AdguardTeam/AdGuardHome#4963

(3 comments) (0 reactions) (0 assignees)Go (34,000 stars) (2,333 forks)batch import

help wantedwaiting for data

説明

Prerequisites

I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
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

x86

Installation

Snapcraft

Setup

On one machine

AdGuard Home version

v0.107.13

Description

I am using RHEL-8.6.0 system in aws ec2, I have configured ssl certificate, ec2 security group has squared port 853. Port 853 is not working, I check that port 853 is listening, no firewall is enabled, but port 853 is always in filtered state. I use nmap to scan 127.0.0.1 and find that port 853 is in open state, but when I use nmap to scan public ip, I find that it is in filtered state. Is this a problem caused by incompatibility with RHEL-8.6.0? Sorry, I forgot to mention

コントリビューターガイド

技術スタック: go
領域: backend
Issue 種別: bug
難度: 3
推定時間: 1-2 days
活動状況: stale
明確さ: needs investigation
前提条件: GoDNS over TLSAdGuardHome codebaseLinux network troubleshooting
初心者向け度: 30
調査方針: Investigate the TLS listener configuration in AdGuardHome's source code, particularly the port binding for DNS over TLS. Check if there is a known issue with RHEL or specific kernel settings. Look at the code responsible for starting the TLS listener, likely in the `internal/dns` package. Also review any existing discussions on GitHub about port 853 issues with similar setups.