Thank you for your donation!


Cloudsmith graciously provides open-source package management and distribution for our project.


Solved: TIDAL
#16
(09-05-2018, 08:19 AM)gza123 Wrote: I have no proxies nor subnets. Just simple configuration LAN-Router-WAN.
Router is giving external DNS (ISP's) servers to all LAN hosts via DHCP service.
Following your advise, I compared /etc/resolv.conf at both moOde and OSX seem to be identical:

moOde:

Code:
pi@moode:~ $ cat /etc/resolv.conf
# Generated by resolvconf
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

OSX:

Code:
MacBook-Pro:~ $ cat /etc/resolv.conf
#
# macOS Notice
#
# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.
#
# To view the DNS configuration used by this system, use:
#   scutil --dns
#
# SEE ALSO
#   dns-sd(1), scutil(8)
#
# This file is automatically generated.
#
domain gdansk-morena.vectranet.pl
nameserver 37.8.214.2
nameserver 31.11.202.254

Regards,

@gza123

I just tried to resolve the Tidal hostname with the nameservers listed in your resolv.conf by using the 'dig' command [1]. The process failed in both instances. Here's just the first failure:


Code:
pi@moode:~ $ dig @37.8.214.2 ab-pr-ak.audio.tidal.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> @37.8.214.2 ab-pr-ak.audio.tidal.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 36545
;; flags: qr rd ad; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1
;; WARNING: recursion requested but not available

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;ab-pr-ak.audio.tidal.com.    IN    A

;; Query time: 135 msec
;; SERVER: 37.8.214.2#53(37.8.214.2)
;; WHEN: Wed Sep 05 12:26:07 EDT 2018
;; MSG SIZE  rcvd: 53


In contrast, here's a successful result using the Google nameserver 8.8.8.8:

Code:
pi@moode:~ $ dig @8.8.8.8 ab-pr-ak.audio.tidal.com

; <<>> DiG 9.10.3-P4-Raspbian <<>> @8.8.8.8 ab-pr-ak.audio.tidal.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 50490
;; flags: qr rd ra; QUERY: 1, ANSWER: 5, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;ab-pr-ak.audio.tidal.com.    IN    A

;; ANSWER SECTION:
ab-pr-ak.audio.tidal.com. 74    IN    CNAME    ab-pr-ak.audio.tidal.akadns.net.
ab-pr-ak.audio.tidal.akadns.net. 29 IN    CNAME    eip4ab-pr-ak.audio.tidal.com.edgekey.net.
eip4ab-pr-ak.audio.tidal.com.edgekey.net. 17877    IN CNAME eip4ab-pr-ak.audio.tidal.com.eip.akadns.net.
eip4ab-pr-ak.audio.tidal.com.eip.akadns.net. 299 IN CNAME eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net.
eip-tata.eip4ab-pr-ak.audio.tidal.com.akahost.net. 8 IN    A 23.7.244.13

;; Query time: 201 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Wed Sep 05 12:24:38 EDT 2018
;; MSG SIZE  rcvd: 272


You can try the same test at your location using your own moOde player.

I don't have any experience with OSX. These comment lines from your /etc/resolv.conf file tell me I can't simply extrapolate from my past Linux/Unix experience:

Quote:# This file is not consulted for DNS hostname resolution, address
# resolution, or the DNS query routing mechanism used by most
# processes on this system.

It could mean that your OSX is actually using a different nameserver than those listed in its resolve.conf file.

Regards,
Kent

[1] dig is not part of a default raspbian installation. You can install it from the dnsutils package:

Code:
pi@moode:~ $ sudo apt-get install dnsutils
Reply


Messages In This Thread
TIDAL - by dekac - 08-21-2018, 11:13 AM
RE: TIDAL - by kit1cat - 08-21-2018, 11:46 AM
RE: TIDAL - by dekac - 08-21-2018, 01:28 PM
RE: TIDAL - by dekac - 08-21-2018, 01:30 PM
RE: TIDAL - by gza123 - 09-03-2018, 08:58 PM
RE: TIDAL - by TheOldPresbyope - 09-04-2018, 12:24 AM
RE: TIDAL - by gza123 - 09-04-2018, 08:24 AM
RE: TIDAL - by TheOldPresbyope - 09-04-2018, 01:45 PM
RE: TIDAL - by gza123 - 09-04-2018, 03:42 PM
RE: TIDAL - by TheOldPresbyope - 09-04-2018, 04:26 PM
RE: TIDAL - by gza123 - 09-04-2018, 07:43 PM
RE: TIDAL - by TheOldPresbyope - 09-04-2018, 10:59 PM
RE: TIDAL - by gza123 - 09-05-2018, 08:19 AM
RE: TIDAL - by TheOldPresbyope - 09-05-2018, 05:00 PM
RE: TIDAL - by gza123 - 09-09-2018, 09:29 AM
RE: TIDAL - by dekac - 10-06-2018, 04:32 PM
RE: TIDAL - by dekac - 10-06-2018, 05:31 PM
RE: TIDAL - by Tim Curtis - 10-06-2018, 05:57 PM
RE: TIDAL - by serverbaboon - 09-09-2018, 12:30 PM
RE: TIDAL - by TheOldPresbyope - 09-09-2018, 02:03 PM
RE: TIDAL - by serverbaboon - 09-09-2018, 03:11 PM
RE: TIDAL - by TheOldPresbyope - 09-09-2018, 03:45 PM
RE: TIDAL - by Tim Curtis - 09-04-2018, 07:52 PM
RE: TIDAL - by gza123 - 09-04-2018, 08:34 PM
RE: TIDAL - by Tim Curtis - 09-09-2018, 01:01 PM
RE: TIDAL - by serverbaboon - 09-09-2018, 03:50 PM
RE: TIDAL - by Bernd - 09-11-2018, 06:37 PM
RE: TIDAL - by rikardo1979 - 09-12-2018, 09:17 AM
RE: TIDAL - by TheOldPresbyope - 09-12-2018, 03:38 PM
RE: TIDAL - by Bernd - 09-12-2018, 08:52 PM
RE: TIDAL - by TheOldPresbyope - 09-12-2018, 10:39 PM
RE: TIDAL - by Bernd - 09-13-2018, 06:16 AM
RE: TIDAL - by kit1cat - 09-13-2018, 09:33 AM
RE: TIDAL - by dekac - 10-06-2018, 04:21 PM
RE: TIDAL - by Tim Curtis - 10-06-2018, 05:16 PM
RE: TIDAL - by dekac - 10-06-2018, 05:33 PM
RE: TIDAL - by dekac - 10-06-2018, 06:31 PM
RE: TIDAL - by dekac - 10-07-2018, 11:54 AM
RE: TIDAL - by Tim Curtis - 10-07-2018, 03:09 PM
Tidal - does not work - by Bernd - 09-10-2018, 08:31 PM
RE: Tidal - does not work - by rikardo1979 - 09-11-2018, 08:34 AM
RE: Tidal - does not work - by TheOldPresbyope - 09-11-2018, 02:48 PM

Forum Jump: