unlinking an IP from a config
New user here, so I apologize if the answer is elementary. Please excuse my ignorance.
My problem is that I have two residences; Jersey and a place in Upstate NY. When the kids school get closed due to Covid, we all head on up to the upstate cabin. Who wants to stay in Jersey?
The router up there has the NextDNS servers configured and everything is copacetic... that is until we came back down to NJ. I was looking at the upstate config and the Linked IP was not green. I knew I should't click on it - but I did. Now all logs have stopped and basically that config is kaput.
Q: Is there anyway to unlink or otherwise enforce the IP of the router up there so I can resume collecting logs?
Is there no way to programmatically update the linked IP by calling:
... if only I knew the encoding used in the last segment of the URI ... I bet I could fix this
There would no functional difference for me to create a new profile, only to have to be there in person to link the IP. Luckily, I made it up last weekend and hit the link button on the original profile. Everything is copacetic. It's just that I cannot believe I'm the only schmo who's done this. A proper support staff could have easily fixed it... but no. Nobody, and I mean NextDNS, get up out of your chairs to help me, I got this.