Name resolution issues causing inability to claim server - Arch Linux

Plex Media Server Desktops & Laptops
21

Yes, I would not have posted the solution I did if I did not show I could break and fix Plex with it.

When there is no nameserver in /etc/resolv.conf (resolv.conf mode: foreign, the state in which I made my initial post) or no /etc/resolv.conf file or symlink at all, which gives resolv.conf mode: missing, the behavior is as below: ping, curl, and wget resolve domain names; dig, nslookup, and Plex v1.23.2.4656-85f0adf5b fail to resolve plex.tv.

$ sudo unlink /etc/resolv.conf

$ cat /etc/resolv.conf
# Resolver configuration file.
# See resolv.conf(5) for details.
# nameserver 1.1.1.1 8.8.8.8 9.9.9.10

$ ls -la /etc/resolv.conf
-rw-r--r-- 1 root root 103 Jun 13 23:57 /etc/resolv.conf

$ sudo systemctl restart systemd-resolved

$ sudo resolvectl status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: foreign
         DNS Servers: 1.1.1.1
Fallback DNS Servers: 9.9.9.10 8.8.8.8 1.0.0.1 8.8.4.4 2001:4860:4860::8888 2606:4700:4700::1111 2606:4700:4700::1001

Link 2 (eno1)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (br0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

$ curl plex.tv
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

# plex.tv doesn't answer pings so I went with www.plex.tv
$ ping -c 5 www.plex.tv
PING www.plex.tv (104.18.13.47) 56(84) bytes of data.
64 bytes from 104.18.13.47 (104.18.13.47): icmp_seq=1 ttl=59 time=7.21 ms
64 bytes from 104.18.13.47 (104.18.13.47): icmp_seq=2 ttl=59 time=7.62 ms
64 bytes from 104.18.13.47 (104.18.13.47): icmp_seq=3 ttl=59 time=7.21 ms
64 bytes from 104.18.13.47 (104.18.13.47): icmp_seq=4 ttl=59 time=7.50 ms
64 bytes from 104.18.13.47 (104.18.13.47): icmp_seq=5 ttl=59 time=6.45 ms

--- www.plex.tv ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4005ms
rtt min/avg/max/mdev = 6.451/7.198/7.620/0.406 ms

$ wget plex.tv
--2021-06-14 00:01:08--  http://plex.tv/
Resolving plex.tv (plex.tv)... 99.81.153.144, 108.128.10.254, 99.81.164.127
Connecting to plex.tv (plex.tv)|99.81.153.144|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://plex.tv/ [following]
--2021-06-14 00:01:08--  https://plex.tv/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Connecting to plex.tv (plex.tv)|99.81.153.144|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://www.plex.tv/ [following]
--2021-06-14 00:01:08--  https://www.plex.tv/
Resolving www.plex.tv (www.plex.tv)... 104.18.12.47, 104.18.13.47, 2606:4700::6812:c2f, ...
Connecting to www.plex.tv (www.plex.tv)|104.18.12.47|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html.2’

index.html.2                                                    [ <=>                                                                                                                                       ] 234.08K  --.-KB/s    in 0.02s

2021-06-14 00:01:08 (10.7 MB/s) - ‘index.html.2’ saved [239697]

$ dig plex.tv

; <<>> DiG 9.16.16 <<>> plex.tv
;; global options: +cmd
;; connection timed out; no servers could be reached

$ nslookup plex.tv
;; connection timed out; no servers could be reached

$ sudo systemctl stop plexmediaserver

$ sudo rm /var/log/plex/Plex\ Media\ Server.log

$ sudo systemctl start plexmediaserver

$ cat /var/log/plex/Plex\ Media\ Server.log | grep -e WARN -e ERROR
Jun 14, 2021 00:03:04.576 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:04.576 [0x7fa8630eab38] WARN - [MediaProviderManager] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:04.576 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error parsing content.
Jun 14, 2021 00:03:04.576 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error parsing XML: Error parsing file.
Jun 14, 2021 00:03:04.580 [0x7fa862e17b38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:04.580 [0x7fa862e17b38] WARN - HTTP error requesting GET https://plex.tv/api/v2/server/access_tokens?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:05.829 [0x7fa86295fb38] ERROR - getaddrinfo(192-168-1-69.abcdefghijklmnopqrstuvwxyz012345.plex.direct) failed: -3
Jun 14, 2021 00:03:05.829 [0x7fa862b44b38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:05.829 [0x7fa862b44b38] WARN - HTTP error requesting GET https://plex.tv/api/v2/user?includeSubscriptions=1&includeProviders=1 (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:05.829 [0x7fa862b8ab38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:05.829 [0x7fa862b8ab38] WARN - HTTP error requesting GET http://plex.tv/pms/:/ip (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:05.830 [0x7fa862b8ab38] ERROR - PublicAddressManager: Unable to get public IP adddress from myPlex (httpCode=-6):
Jun 14, 2021 00:03:09.582 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:09.582 [0x7fa8630eab38] WARN - [MediaProviderManager] HTTP error requesting GET https://plex.tv/media/providers?X-Plex-Token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:09.582 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error parsing content.
Jun 14, 2021 00:03:09.582 [0x7fa8630eab38] ERROR - [MediaProviderManager] Error parsing XML: Error parsing file.
Jun 14, 2021 00:03:09.590 [0x7fa862e17b38] ERROR - Error issuing curl_easy_perform(handle): 6
Jun 14, 2021 00:03:09.590 [0x7fa862e17b38] WARN - HTTP error requesting GET https://plex.tv/api/v2/server/users?auth_token=xxxxxxxxxxxxxxxxxxxx (6, Couldn't resolve host name) (Could not resolve host: plex.tv)
Jun 14, 2021 00:03:10.838 [0x7fa862b8ab38] ERROR - Error issuing curl_easy_perform(handle): 6

The behavior after putting a DNS server IP into /etc/resolv.conf (resolv.conf mode: uplink if it is a symlink like in the example below, resolv.conf mode: foreign if it is just a file, but still fixes DNS issues): ping, curl, and wget are the same; dig, nslookup, and Plex v1.23.2.4656-85f0adf5b now have DNS resolution.

$ sudo ln -snf /run/systemd/resolve/resolv.conf /etc/resolv.conf

$ cat /etc/resolv.conf
# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 1.1.1.1
search .

$ ls -la /etc/resolv.conf
lrwxrwxrwx 1 root root 32 Jun 14 00:10 /etc/resolv.conf -> /run/systemd/resolve/resolv.conf

$ sudo systemctl restart systemd-resolved

$ sudo resolvectl status
Global
           Protocols: +LLMNR +mDNS -DNSOverTLS DNSSEC=no/unsupported
    resolv.conf mode: uplink
         DNS Servers: 1.1.1.1
Fallback DNS Servers: 9.9.9.10 8.8.8.8 1.0.0.1 8.8.4.4 2001:4860:4860::8888 2606:4700:4700::1111 2606:4700:4700::1001

Link 2 (eno1)
Current Scopes: LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

Link 3 (br0)
Current Scopes: LLMNR/IPv4 LLMNR/IPv6
     Protocols: -DefaultRoute +LLMNR -mDNS -DNSOverTLS DNSSEC=no/unsupported

$ curl plex.tv
<html>
<head><title>301 Moved Permanently</title></head>
<body bgcolor="white">
<center><h1>301 Moved Permanently</h1></center>
<hr><center>nginx</center>
</body>
</html>

$ ping -c 5 www.plex.tv
PING www.plex.tv (104.18.12.47) 56(84) bytes of data.
64 bytes from 104.18.12.47 (104.18.12.47): icmp_seq=1 ttl=59 time=6.14 ms
64 bytes from 104.18.12.47 (104.18.12.47): icmp_seq=2 ttl=59 time=6.73 ms
64 bytes from 104.18.12.47 (104.18.12.47): icmp_seq=3 ttl=59 time=5.60 ms
64 bytes from 104.18.12.47 (104.18.12.47): icmp_seq=4 ttl=59 time=5.94 ms
64 bytes from 104.18.12.47 (104.18.12.47): icmp_seq=5 ttl=59 time=5.68 ms

--- www.plex.tv ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4006ms
rtt min/avg/max/mdev = 5.603/6.021/6.733/0.404 ms

$ wget plex.tv
--2021-06-14 00:17:48--  http://plex.tv/
Resolving plex.tv (plex.tv)... 99.81.164.127, 108.128.10.254, 99.81.153.144
Connecting to plex.tv (plex.tv)|99.81.164.127|:80... connected.
HTTP request sent, awaiting response... 301 Moved Permanently
Location: https://plex.tv/ [following]
--2021-06-14 00:17:48--  https://plex.tv/
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Connecting to plex.tv (plex.tv)|99.81.164.127|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://www.plex.tv/ [following]
--2021-06-14 00:17:49--  https://www.plex.tv/
Resolving www.plex.tv (www.plex.tv)... 104.18.13.47, 104.18.12.47, 2606:4700::6812:d2f, ...
Connecting to www.plex.tv (www.plex.tv)|104.18.13.47|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: unspecified [text/html]
Saving to: ‘index.html.3’

index.html.3                                                    [ <=>                                                                                                                                       ] 234.08K  --.-KB/s    in 0.03s

2021-06-14 00:17:49 (7.58 MB/s) - ‘index.html.3’ saved [239697]

$ dig plex.tv

; <<>> DiG 9.16.16 <<>> plex.tv
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 38438
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                38      IN      A       99.81.153.144
plex.tv.                38      IN      A       99.81.164.127
plex.tv.                38      IN      A       108.128.10.254

;; Query time: 10 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 14 00:18:04 EDT 2021
;; MSG SIZE  rcvd: 84

$ nslookup plex.tv
Server:         1.1.1.1
Address:        1.1.1.1#53

Non-authoritative answer:
Name:   plex.tv
Address: 108.128.10.254
Name:   plex.tv
Address: 99.81.153.144
Name:   plex.tv
Address: 99.81.164.127

$ sudo systemctl stop plexmediaserver

$ sudo rm /var/log/plex/Plex\ Media\ Server.log

$ sudo systemctl start plexmediaserver

$ cat /var/log/plex/Plex\ Media\ Server.log | grep -e WARN -e ERROR
Jun 14, 2021 00:19:00.364 [0x7f40e7f4bb38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Jun 14, 2021 00:19:00.364 [0x7f40e7f4bb38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Jun 14, 2021 00:19:00.364 [0x7f40e7f4bb38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: universalSearch
Jun 14, 2021 00:19:00.368 [0x7f40e8073b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability
Jun 14, 2021 00:19:00.368 [0x7f40e8073b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: availability-platforms
Jun 14, 2021 00:19:00.368 [0x7f40e8073b38] WARN - [MediaProviderManager] Unrecognized MediaProvider feature: universalSearch
Jun 14, 2021 00:19:01.034 [0x7f40e75b5b38] ERROR - Unable to find client profile for device; platform=Xbox, platformVersion=10.0.19041.7772, device=Xbox, model=Xbox One
Jun 14, 2021 00:19:01.034 [0x7f40e75b5b38] WARN - [Analytics] Attempting to send unrecognized metric (playback:server:itemstart). Skipping.
Jun 14, 2021 00:19:01.787 [0x7f40e8202b38] WARN - MyPlex: attempted a reachability check but we're not yet mapped.
Jun 14, 2021 00:19:01.817 [0x7f40e781cb38] WARN - Sync: Couldn't get sync lists without subscription.
1 Like
22

nslookup is different from many other tools; it parses /etc/resolv.conf itself rather than using (whichever) libc. So that one is easy to understand.

—-

Out of curiosity, does your firewall allow communication from localhost to 127.0.0.53 or 127.0.0.1, udp:53?

Is something equivalent to iptables -I INPUT -s localhost -d 127.0.0.53 -j ACCEPT present?

Can you do nslookup www.plex.tv 127.0.0.53?

23

When I filed this issue, I had iptables disabled so I could rule that out. I have since enabled it. I’m so bad at iptables, but the relevant lines in /etc/sysconfig/iptables are:

# Allow loopback interface (lo0) and drop all traffic to 127/8 that doesn't use lo0
-A INPUT -i lo -j ACCEPT
-A OUTPUT -o lo -j ACCEPT
-A INPUT -d 127.0.0.0/8 -j REJECT
-A OUTPUT -d 127.0.0.0/8 -j REJECT

# DNS resolution is UDP on port 53
-A INPUT -p udp --sport 53 -j ACCEPT
-A OUTPUT -p udp --dport 53 -j ACCEPT

and nslookup gives this both when /etc/resolv.conf is empty and when /etc/resolv.conf is a symlink to a populated /run/systemd/resolve/resolv.conf (restarting systemd-resolved in between changes of /etc/resolv.conf)

$ nslookup www.plex.tv 127.0.0.53
Server:         127.0.0.53
Address:        127.0.0.53#53

Non-authoritative answer:
Name:   www.plex.tv
Address: 104.18.12.47
Name:   www.plex.tv
Address: 104.18.13.47
Name:   www.plex.tv
Address: 2606:4700::6812:d2f
Name:   www.plex.tv
Address: 2606:4700::6812:c2f
1 Like
24

Any difference with 127.0.0.1?

26

Yes, timeout whether iptables is running or stopped.

$ nslookup www.plex.tv 127.0.0.1
;; connection timed out; no servers could be reached
1 Like
27

Ok: I looked at the code. musl’s fallback is to 127.0.0.1.

It looks at /etc/resolv.conf for nameservers and falls back to 127.0.0.1.

If there’s no response from 127.0.0.1 then resolution will fail.

How did your system get into a state where there was no valid /etc/resolv.conf, do you know?

28

The file was there but it only had a little commented header. As far as I know, that is just the default on Arch Linux, it’s a very DIY distribution. For example, you don’t have networking if you don’t set up your ethernet device yourself with iproute2. I am writing a guide on how to go from Arch Linux installation to running a Windows VM, because it took me so long to iron out the details of it.

29

Oh! Well then! :slight_smile: If it’s a DIY thing, set up /etc/resolv.conf appropriately.

https://www.freedesktop.org/software/systemd/man/systemd-resolved.service.html#/etc/resolv.conf

Some apps parse the file themselves, some via a traditional library, some use systemd-provided libraries.

Arch seems weird. It uses “modern” stuff like systemd but is also DIY. Many of the DIY distros are very retro and anti-systemd.

30

You’re absolutely right, it’s in my installation notes for the future. It’s just that no program has ever had DNS issues even with /etc/resolv.conf being empty, including Plex <v1.23.

1 Like
31

Anyone running into DNS lookup issues with 1.23 or later, please post the following information from the system where the error occurs:

  • Contents of /etc/resolv.conf
  • Output of dig plex.tv A plex.tv AAAA +nofail

Thanks.

1 Like
32

Plex Media Server: v1.23.2.4656-85f0adf5b
Operating System: Arch Linux 2021.06

$ dig plex.tv A plex.tv AAAA +nofail when /etc/resolv.conf is an empty or nonexistent file:

; <<>> DiG 9.16.16 <<>> plex.tv A plex.tv AAAA +nofail
;; global options: +cmd
;; connection timed out; no servers could be reached

/etc/resolv.conf when it is a symlink to /run/systemd/resolve/resolv.conf

# This is /run/systemd/resolve/resolv.conf managed by man:systemd-resolved(8).
# Do not edit.
#
# This file might be symlinked as /etc/resolv.conf. If you're looking at
# /etc/resolv.conf and seeing this text, you have followed the symlink.
#
# This is a dynamic resolv.conf file for connecting local clients directly to
# all known uplink DNS servers. This file lists all configured search domains.
#
# Third party programs should typically not access this file directly, but only
# through the symlink at /etc/resolv.conf. To manage man:resolv.conf(5) in a
# different way, replace this symlink by a static file or a different symlink.
#
# See man:systemd-resolved.service(8) for details about the supported modes of
# operation for /etc/resolv.conf.

nameserver 1.1.1.1
search .

$ dig plex.tv A plex.tv AAAA +nofail when /etc/resolv.conf is a symlink to /run/systemd/resolve/resolv.conf

; <<>> DiG 9.16.16 <<>> plex.tv A plex.tv AAAA +nofail
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24613
;; flags: qr rd ra; QUERY: 1, ANSWER: 3, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;plex.tv.                       IN      A

;; ANSWER SECTION:
plex.tv.                14      IN      A       99.81.153.144
plex.tv.                14      IN      A       108.128.10.254
plex.tv.                14      IN      A       99.81.164.127

;; Query time: 10 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 14 01:35:37 EDT 2021
;; MSG SIZE  rcvd: 84

;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 24798
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 1232
;; QUESTION SECTION:
;plex.tv.                       IN      AAAA

;; AUTHORITY SECTION:
plex.tv.                2903    IN      SOA     jeremy.ns.cloudflare.com. dns.cloudflare.com. 2037520463 10000 2400 604800 3600

;; Query time: 6 msec
;; SERVER: 1.1.1.1#53(1.1.1.1)
;; WHEN: Mon Jun 14 01:35:37 EDT 2021
;; MSG SIZE  rcvd: 100
33

I don’t understand how this condition can possibly work at all. An empty/missing resolv.conf is a valid configuration, but it requires a working resolver on 127.0.0.1, which you don’t appear to have. Could you run strace ping -c 1 www.plex.tv and post the output?

I only need information on configurations where glibc-based applications work, but PMS doesn’t.

1 Like
34

@mikewouldknow can you also share the contents of your /etc/nsswitch.conf?

I think this is why ping and other glibc-linked utilities work with an empty /etc/resolv.conf.

nss-resolve(8) — Arch manual pages

Musl doesn’t implement NSS nor support glibc-specific systemd extensions.

35

Contents of /etc/nsswitch.conf

# Name Service Switch configuration file.
# See nsswitch.conf(5) for details.

passwd: files systemd
group: files [SUCCESS=merge] systemd
shadow: files

publickey: files

hosts: files mymachines myhostname resolve [!UNAVAIL=return] dns
networks: files

protocols: files
services: files
ethers: files
rpc: files

netgroup: files

strace ping -c 1 www.plex.tv output attached with and without /etc/resolv.conf symlink established, restarting systemd-resolved in between changes.

Arch_Linux_strace_ping_-c_1_www.plex.tv_No_resolv.conf.txt (47.6 KB)
Arch_Linux_strace_ping_-c_1_www.plex.tv_resolv.conf.txt (47.8 KB)

1 Like
36

Apart from finding /etc/resolv.conf or not (which differs as expected) those should be pretty identical.

Resolution is being performed by the resolve (systemd) module successfully, so classic Unix dns isn’t used.

This explains why a missing /etc/resolv.conf works. Apps linked to glibc are never getting to the classic dns module at all. Systemd’s resolve glibc NSS module is configured before it and responds first.

—-

I’m curious if other people with the same issue also have an invalid /etc/resolv.conf. While I’m pretty sure it’s not in the LSB, it’s very surprising to me that a distro would ship that way.

Even macOS maintains a valid version of that file!

1 Like
37

Ah, this could definitely explain it!

This configuration is pretty unfortunate, since relying solely on NSS for DNS resolution means that statically-linked apps or ones that ship their own libc (such as PMS) won’t work; it’s pretty much always a good idea to have either a valid resolv.conf, or have a stub resolver listening on 127.0.0.1.

I’m very curious how this configuration ends up happening in the first place; systemd-resolvd exposes a stub resolver at 127.0.0.53, and one would naïvely expect resolv.conf to point at that on a system that uses it.

Anyway, for now, to work around this issue, I’m going to hardcode 127.0.0.53 as an additional fallback address, and add support for an env variable (FALLBACK_NAMESERVER) that’ll also be tried if set. You can build my branch if you’d like; otherwise, you can try this build, which can be dropped into the PMS lib directory. If all seems to be well, we’ll push this out in an upcoming PMS release to work around the bad configuration for people who somehow end up in that situation accidentally.

Thanks much to everyone for your cooperation.

2 Likes
38

Amen.

That’s both gross and clever.

You could do OVERRIDE_NAMESERVER instead of FALLBACK_NAMESERVER and just use it unconditionally when present.

39

This topic was automatically closed 90 days after the last reply. New replies are no longer allowed.