@james123 said in Reolink Camera wont show on Alexa TV [SOLVED]:

/etc/init.d/dnsmasq force-reload

Really interested in this post - i’ve got exactly the same problems with Reolink cameras, although i don’t have the same router as you. My router is a UK plusnet router, any ideas on how to get DNS binding active on that router?

Thanks in advance,
Martin

Hi,
I have Hikvision cameras and a Plusnet One Hub. Can find anywhere how to do the rebinding. I followed the guide on nslookup and its point to the binding issue. Anyone able to help a novice with some pointers?

Thanks

Steve

One of my cameras has audio which, whilst supposedly G711 compliant, reported a spurious codec when viewed using VLC and so I’ve resorted to using the gateway (installed as a Synology docker container) and using the @noaudio tag.

I was still struggling though and turns out to be a DNS rebinding issue as described here. I’m running a Unifi network with USG as the router and DNS is not one of its strengths. After confirming via nslookup that it may be a rebinding issue, I’ve added a static config on the USG via SSH (set system static-host-mapping host-name <hostname> inet <ip address>) and which has solved my problem. It’s only temporary as the static config will be over-written on the next reboot/provisioning however I’ll figure out the permanent fix next.

Video now working great via the Echo Show 8…really helpful forum post

/etc/init.d/dnsmasq force-reload

Really interested in this post - i’ve got exactly the same problems with Reolink cameras, although i don’t have the same router as you. My router is a UK plusnet router, any ideas on how to get DNS binding active on that router?

Thanks in advance,
Martin

I would think that the Unifi USG would support DNS rebinding options as well. Although your static routing will work perfectly fine.

DNSMasq file:
rebind-domain-ok=/mproxy.io/

I don’t have any USG devices, but maybe this example config may be applicable. https://community.ubnt.com/t5/UniFi-Routing-Switching/json-file-help/m-p/2463090/highlight/true#M104288

{
  "service": {
    "dns": {
      "forwarding": {
        "options": [
          "rebind-domain-ok=/mproxy.io/"
        ]
      },

1. As a root on usg shh then create/edit file:

vi /etc/dnsmasq.d/dnsmasq.static.conf

2. Put the hosts in

address=/FQDN.mproxy.io/10.10.1.10
address=/FQDN2.mproxy.io/10.10.1.10

3. Save it (:wq) and then run command

/etc/init.d/dnsmasq force-reload

Then check with an nslookup. Should be good to go.

@Monocle Thanks for your help. Feel free to add this to your troubshoting page for other users with UniFi kit.

Great, glad we have narrowed it down. We hope to add additional tools in future versions of the Monocle Gateway to help diagnose these types of issues quickly and easily.

Hopefully with the Unifi equipment they offer a simple means to whitelist a particular domain from DNS REBINDING. I use a PFSense router here and it was as simple as adding a custom option to the DNS Forwarder: rebind-domain-ok=/mproxy.io/

Once you have the DNS rebind sorted on your router, you may also need to reboot the Alexa devices to clear any internal DNS caches.

Thanks, Robert

Looks like you are bang, sorry i missed that bit in the help docs) on the 8.8.8.8 lookup gives 10.10.1.11 (which is correct) the first nslooup gives the default gateway response of 10.10.1.1 (not correct).

Wrong:

Correct:

Now i just need to work out how to do the DNS REBINDING on a Unifi network. Will post the answer to help others.

Thanks for the super quick advice.

This also coincides with the log file you have shown. There are no log entries for incoming connections to the Monocle Gateway from any Alexa devices.

So let’s step back a minute and determine if the networking is working properly for your Monocle Gateway instance.

First make sure that 443 is not being blocked by a firewall on the Monocle Gateway server.

On startup the Monocle Gateway prints our the local IP address it detected for your gateway instance. Is this the correct IP address? (the auto-detection just finds the first network interface and assumes it is the correct one.). If the private IP is correct, then take a look at the unique FQDN DNS hostname. This is the host address that we provide to the Alexa system to access your cameras via your Monocle Gateway instance. Try performing a nslookup on this hostname record (ideally from another computer on your network) to make sure it’s resolving to your gateway’s private IP address. If nslookup returns the correct IP address, then try to ping that address to make sure you can resolve it locally on your network. If the address is not correct, then the issue could be DNS REBINDING. See this page for more details.

Examples:

Perform the DNS lookup locally on your network.
(Use your actual FQDN instead of the example below)

nslookup c5b4w3q2-bv4f-4sdf9-dsf-28a852ecae54.mproxy.io

Perform the DNS lookup directly against a public DNS server (bypassing your local DNS server/router)
(Use your actual FQDN instead of the example below)

nslookup c5b4w3q2-bv4f-4sdf9-dsf-28a852ecae54.mproxy.io 8.8.8.8

If the local DNS attempt fails but the public DNS server returns the correct address, then this is most likely a DNS REBINDING issue.