Plex.direct DNS servers unreachable via ipv6

Plex Media Server Remote Access
1

The DNS servers for plex.direct appear to be unreachable via IPv6.

$ dig +noall +answer plex.direct. NS
plex.direct.		268	IN	NS	ns-plexdirect.plex.tv.
plex.direct.		268	IN	NS	ns1-plexdirect.plex.bz.
plex.direct.		268	IN	NS	ns2-plexdirect.plex.bz.
plex.direct.		268	IN	NS	ns1-plexdirect.plex.tv.


$ dig +noall +answer ns-plexdirect.plex.tv. AAAA
ns-plexdirect.plex.tv.	60	IN	AAAA	2a05:d018:8af:2306::155e
ns-plexdirect.plex.tv.	60	IN	AAAA	2a05:d018:8af:2307::26c5
$ dig +noall +answer ns1-plexdirect.plex.tv. AAAA
ns1-plexdirect.plex.tv.	60	IN	AAAA	2600:1f18:5538:480b::3195
ns1-plexdirect.plex.tv.	60	IN	AAAA	2600:1f18:5538:480a::9263
$ dig +noall +answer ns1-plexdirect.plex.bz. AAAA
ns1-plexdirect.plex.bz.	60	IN	AAAA	2600:1f18:5538:480b::3195
ns1-plexdirect.plex.bz.	60	IN	AAAA	2600:1f18:5538:480a::9263
$ dig +noall +answer ns2-plexdirect.plex.bz. AAAA
ns2-plexdirect.plex.bz.	60	IN	AAAA	2a05:d018:8af:2306::155e
ns2-plexdirect.plex.bz.	60	IN	AAAA	2a05:d018:8af:2307::26c5



$ dig -6 plex.direct. SOA @ns-plexdirect.plex.tv.
;; communications error to 2a05:d018:8af:2306::155e#53: timed out
;; communications error to 2a05:d018:8af:2306::155e#53: timed out
;; communications error to 2a05:d018:8af:2306::155e#53: timed out
;; communications error to 2a05:d018:8af:2307::26c5#53: timed out

; <<>> DiG 9.18.39-0ubuntu0.24.04.3-Ubuntu <<>> -6 plex.direct. SOA @ns-plexdirect.plex.tv.
;; global options: +cmd
;; no servers could be reached

$ dig -6 plex.direct. SOA @ns1-plexdirect.plex.tv.
;; communications error to 2600:1f18:5538:480b::3195#53: timed out
;; communications error to 2600:1f18:5538:480b::3195#53: timed out
;; communications error to 2600:1f18:5538:480b::3195#53: timed out
;; communications error to 2600:1f18:5538:480a::9263#53: timed out

; <<>> DiG 9.18.39-0ubuntu0.24.04.3-Ubuntu <<>> -6 plex.direct. SOA @ns1-plexdirect.plex.tv.
;; global options: +cmd
;; no servers could be reached

Currently, resolution via IPv4 seems to work fine.

$ dig -4 plex.direct. SOA @ns-plexdirect.plex.tv.

; <<>> DiG 9.18.39-0ubuntu0.24.04.3-Ubuntu <<>> -4 plex.direct. SOA @ns-plexdirect.plex.tv.
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43125
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;plex.direct.			IN	SOA

;; AUTHORITY SECTION:
plex.direct.		300	IN	SOA	ns-plexdirect.plex.tv. dns-admin.plex.tv. 0 172800 7200 1209600 3600

;; Query time: 154 msec
;; SERVER: 18.202.136.15#53(ns-plexdirect.plex.tv.) (UDP)
;; WHEN: Wed Apr 08 16:32:05 PDT 2026
;; MSG SIZE  rcvd: 114
2

There is/was a known issue with plex.direct DNS today.

3

There is/was a known issue with plex.direct DNS today.

Yes, I encountered that, too. After that issue was reported resolved (at status.plex.tv), the IPv6 connectivity issue persisted.

As of now, the authoritative nameservers for plex.direct still do not appear to be responding via IPv6.