Update incident: Netflix domains whitelisted in AdGuard
This commit is contained in:
@@ -160,3 +160,30 @@ to-addresses=192.168.31.4 to-ports=53
|
|||||||
### Verification
|
### Verification
|
||||||
- AdGuard container querying 192.168.31.1 → SUCCESS
|
- AdGuard container querying 192.168.31.1 → SUCCESS
|
||||||
- MikroTik resolve command → SUCCESS
|
- MikroTik resolve command → SUCCESS
|
||||||
|
|
||||||
|
---
|
||||||
|
|
||||||
|
## Additional Issue: Netflix Blocked by AdGuard Filter (13:45)
|
||||||
|
|
||||||
|
### Symptom
|
||||||
|
- TV reports no internet even though DNS is working
|
||||||
|
- Netflix app fails to connect
|
||||||
|
|
||||||
|
### Root Cause
|
||||||
|
AdGuard DNS filter (FilterListID:1) was blocking Netflix operational domains:
|
||||||
|
- `ichnaea.netflix.com` - Netflix connectivity check
|
||||||
|
- `customerevents.netflix.com` - Netflix events
|
||||||
|
- `*.logs.netflix.com` - Netflix logging
|
||||||
|
|
||||||
|
Netflix requires these domains to function, even though they're flagged as tracking.
|
||||||
|
|
||||||
|
### Fix
|
||||||
|
Added whitelist rules to AdGuard:
|
||||||
|
```
|
||||||
|
@@||ichnaea.netflix.com^
|
||||||
|
@@||customerevents.netflix.com^
|
||||||
|
@@||logs.netflix.com^
|
||||||
|
```
|
||||||
|
|
||||||
|
### Verification
|
||||||
|
Restarted AdGuard, TV should now connect to Netflix.
|
||||||
|
|||||||
Reference in New Issue
Block a user