SERVFAIL for plex.direct addresses using AirVPN DNS Servers

[RVECJSCXEUZCWVBR 0]

Hi,

When using AirVPN DNS Servers I'm unable to resolve the DNS names of requests like the below
192-168-1-1.77777777777777777777777777777777.plex.direct
Resulting in SERVFAIL

I'm not 100% sure on how plex handles this process, but these requests should always result in the begining IP address. You can change around the IP to anything and it'll return it

Have tested with the below servers
Piscium
Comae
Celaeno
Cujam
Via Tunnelblick Mac, and openVPN via pfsense

I'd appreciate if some others could try to see if this is unique to me. Equally if this has come up before let me know as I couldn't find anything.

Much appreciated,

[OpenSourcerer 1363]

Cannot reproduce on Chamaeleon (US):

dig +short @10.4.0.1 192-168-1-1.77777777777777777777777777777777.plex.direct.
192.168.1.1

I get an interesting result for the parent zone, though:

$ dig +short @10.4.0.1 plex.direct.
0.0.0.0

.

[RVECJSCXEUZCWVBR 0]

Well that's odd. Chamaeleon works for me, and testing some other US servers I get the below
Cursa - Works
Yildun - Doesn't
Vulpecula - Doesn't

And some random world wide servers-
Benetnasch - Doesn't
Camelopardalis - Doesn't
Kitel - Doens't
Alruba - Doesn't

And I get the same for Cursa & Chamaeleon. 0.0.0.0 for plex.direct.

[Air4141841 23]

what DNS server are you using?  you didn't specify in your post
10.4.0.1.  is what is listed here. https://airvpn.org/specs/
 

[RVECJSCXEUZCWVBR 0]

Yes; using 10.4.0.1 or the gateway IP, both give the same results for the servers I've tried.

[ss11 15]

For me using AirVPN's UK servers 192-168-1-1.77777777777777777777777777777777.plex.direct  resolves to 192.168.1.1 - I guess this is correct and expected given you said it should always resolve to the first IP in the subnet?

Given each AirVPN server is also a DNS server, plesk.direct *could* probably blacklist if too many requests come from certain IP addresses, thus resulting in SERVFAIL?