DNS problem with Tidal

[nikigo]

@nikigo

Let's stay focused on what you have now

Sorry, later on I realized I still have the "Could not resolve host: ab-pr-ak.audio.tidal.com" error, as well.

Quick update of what I realized. I removed resolvconf and entered this

Code:

sudo ln -sf /run/resolvconf/resolv.conf /etc/resolv.conf
sudo sh -c 'echo "nameserver 8.8.8.8" >> /etc/resolv.conf'

I was able to play a track from Tidal and I was able to ping. However a reboot overwrites the resolv.conf and then nameserver is back to the router ip and it's not working anymore. It resolves other addresses but not tidal. It works only if the router ip is removed as a nameserver. Other computers and android devices ping the tidal address so I guess the router dns is fine. Something with my network settings on raspbian is broken. Noob here so I would need more help in what other info you need, so you can help me.

Here is what ports are listened while I was able to play a tidal

Code:

pi@moode:~ $ pi@moode:~ $ sudo netstat -tulpn|grep upmpdcli
tcp        0      0 192.168.100.20:49152    0.0.0.0:*               LISTEN      756/upmpdcli
tcp        0      0 192.168.100.20:49153    0.0.0.0:*               LISTEN      786/upmpdcli
udp        0      0 127.0.0.1:35065         0.0.0.0:*                           756/upmpdcli
udp        0      0 127.0.0.1:52541         0.0.0.0:*                           786/upmpdcli
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           786/upmpdcli
udp        0      0 0.0.0.0:1900            0.0.0.0:*                           756/upmpdcli