el_pedr0
Occasional Visitor
Summary: I see different behaviour when I use the ip address of an internal machine compared to when I use it's hostname concatenated with the RT-AC68U's Domain Name. Please help me diagnose what's going on.
Symptoms:
I have an audiobookshelf instance on a host called abshost in my home network which allows me to stream audiobooks. I also have the audiobookshelf android app. I can configure the app to point to my server either using the address: 192.168.xxx.xxx:13378, or using the abshost.home.real.domain:13378 where home.real.domain is the value set in the RT-AC68U's Domain Name field of LAN > LANIP. (for this thread I've replaced a real domain that I own with 'real.domain').
Within the app, there is a 'cast' button which I can click to cast the stream to my chrome cast devices.
When I click the cast button, I can hear the chime on the speakers indicating that a connection is being established. However, the stream only makes it to the speakers when I have configured the app using the IP address rather than the abshost.home.example.com. The app itself can accept urls rather than ip addresses.
In both cases, the traffic has to be handled by the router to route it to the host. But why should it behave differently when it adds an internal DNS lookup to resovle the abshost.home.real.domain? The subdomain home.real.domain is defined within the router configuration as the router's Domain Name, and while the root real.domain has public records, the home.real.domain does not appear in any public dns records.
How can I start diagnosing what's going on here?
(edited to clarify addresses)
Symptoms:
I have an audiobookshelf instance on a host called abshost in my home network which allows me to stream audiobooks. I also have the audiobookshelf android app. I can configure the app to point to my server either using the address: 192.168.xxx.xxx:13378, or using the abshost.home.real.domain:13378 where home.real.domain is the value set in the RT-AC68U's Domain Name field of LAN > LANIP. (for this thread I've replaced a real domain that I own with 'real.domain').
Within the app, there is a 'cast' button which I can click to cast the stream to my chrome cast devices.
When I click the cast button, I can hear the chime on the speakers indicating that a connection is being established. However, the stream only makes it to the speakers when I have configured the app using the IP address rather than the abshost.home.example.com. The app itself can accept urls rather than ip addresses.
In both cases, the traffic has to be handled by the router to route it to the host. But why should it behave differently when it adds an internal DNS lookup to resovle the abshost.home.real.domain? The subdomain home.real.domain is defined within the router configuration as the router's Domain Name, and while the root real.domain has public records, the home.real.domain does not appear in any public dns records.
How can I start diagnosing what's going on here?
(edited to clarify addresses)
