AdguardTeam / AdguardTeam/AdGuardHome

iOS client identifier

Abierto
#8,222 2 comentarios 0 reacciones 0 asignados Ver en GitHub
waiting for data
Lenguaje dominante
TypeScript
Estrellas
36.9k
Forks
2.5k
Métricas de merge de PR
Sin PR fusionados en 30 d

Descripción

### 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)

Custom (please mention in the description)

### Installation

GitHub releases or script from README

### Setup

On one machine

### AdGuard Home version

v0.107.71

### Action

I use adguard home dns on multiple devices. Specifically I use tls for example on windows and android with the correct result and the client is before the hostname clientid.domain.com is properly shown in adguard home admin.
Now I want to add an iOS device, and I did the same.

### Expected result

I expect the iOS client to show with the subdomain as client id in adguard home.

### Actual result

The dns does reach my adguard domain and shows but without client id and just with ipofdevice/x.x.x.x.

### Additional information and/or screenshots

_No response_

Guía de contribución

Abrir la guía de contribución

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.