HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
2020-07-14 15:15:37
Model: HS103  
Hardware Version: V2
Firmware Version: 1.1.2

I have an IoT VLAN setup for all my smart plugs, Fire Sticks, tablets, scales, etc..  My IoT allows all access outbound and access back into my LAN to my PiHole DNS servers.  All of my other IoT devices have been working flawlessly with this.  If I have my router supply 8.8.8.8 as the DNS I can control, as in, schedule the HS103 outlets I have.  As soon as I point them back at my PiHole, I can't.  Even if I disable PiHole for x minutes, they I still can't control them.  They say local anytime DNS is my PiHole and don't have local only when they have 8.8.8.8.  Does anyone have any ideas?

 

Basically anytime my HS103's have my PiHole as DNS they're local only.  When they're 8.8.8.8 they don't have local only.

 

My home network is Ubiquiti Unifi with a Dream Machine Pro with nanoHD APs.

 

Any help is greatly appreacated. 

 

Thanks!

  0      
  0      
#1
Options
4 Reply
Re:HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
2020-07-15 15:13:54 - last edited 2020-07-16 14:36:07

@RichJ 

 

The HS103 require the DNS be able to resolve the following addresses:

 

devs-gw.tplinkcloud.com 
deventry.tplinkcloud.com 

 

It seems the pi-hole is not doing that.

  0  
  0  
#2
Options
Re:HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
2020-07-17 15:00:58

@Tony 

 

 

Both of these can be resolved before and after I added them to the whitelist in PiHole.  I added them to the whitelist with wildcard, meaning any subdomain is also whitelisted also.  Switched them back from 8.8.8.8 and rebooted them.   Still the same result. :-(

 

Any other ideas?

 

PS H:\> nslookup deventry.tplinkcloud.com 192.168.1.15
Server:  raspberrypi-1
Address:  192.168.1.15

Non-authoritative answer:
Name:    deventry.tplinkcloud.com
Addresses:  54.204.63.77
          3.216.21.164

 

PS H:\> nslookup devs-gw.tplinkcloud.com 192.168.1.15
Server:  raspberrypi-1
Address:  192.168.1.15

Non-authoritative answer:
Name:    use1-devs-gw.tplinkcloud.com
Addresses:  34.205.22.181
          52.206.116.115
          3.225.235.82
          34.204.115.126
          3.215.31.202
          34.205.86.210
          3.226.66.87
          50.19.49.116
Aliases:  devs-gw.tplinkcloud.com

PS H:\>

  0  
  0  
#3
Options
Re:HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
2020-07-22 18:25:44

@RichJ 

 

Try one more cloud server name which is actually the default one:

 

devs.tplinkcloud.com

 

If that still does not work, please DM me the MAC address of your smart plug.

  0  
  0  
#4
Options
Re:HS103 - can't control/schedule outlets unless my IoT network supplies 8.8.8.8 as the DNS.
2020-07-22 19:22:12

@Tony 

 

That one works also.

 

PS H:\> nslookup devs.tplinkcloud.com 192.168.1.15
Server:  raspberrypi-1
Address:  192.168.1.15

Non-authoritative answer:
Name:    prd-elb-connector-0-563583643.us-east-1.elb.amazonaws.com
Addresses:  34.199.227.235
          3.215.211.164
          3.224.235.192
          34.199.172.24
          34.225.47.234
          52.21.18.148
          3.211.201.183
          52.203.141.21
Aliases:  devs.tplinkcloud.com

PS H:\>

 

I don't understand it.  Something they're trying to get to obviously can't resolve.  :-/ 

  0  
  0  
#5
Options