3 ms·
It always somewhat bugged me they used an actual domain for this, was there no other alternative like using a fake TLD? I'm not sure of what a router is entirel
by giancarlostoro 10y ago
It always somewhat bugged me they used an actual domain for this, was there no other alternative like using a fake TLD? I'm not sure of what a router is entirely capable of doing, but if you could filter a request to "configure.tplink" or something that would make it far less likely to hijack the domain, that and the fact the domain didn't always work every time I would try it... or I couldn't remember it at times.
- chipperyman573 10y agoYou don't need a TLD at all... They added .com to make it more approachable to users (presumably)
- kevinoconnor7 10y agoWhy is that an issue? Owning the domain is the correct thing to do. They just screwed up by losing ownership of it.
- giancarlostoro 10y agoOwning the domain isn't my issue, using one that doesn't always work is my issue. They could of used a hostname or something else that the router picks up?