Nameservers were pointed to CF originally. A developer fired up his own CF account and moved the dns control to that account. They left, and we would like to point back to the original CF account as the records are all still there. The nameservers are the same, tho. So NS is pointing to CF, but my CF account is not realizing it should be controlling the DNS… Is there a way to tell CF to refresh the account or anything like that?
What feature, service or problem is this related to?
Thanks for the reply- actually it seems that the control is back to the original account, the one I own… NS were pointing correctly, but my account just wasnt’ actually making changes that impacted the website, so when I added a validation record, for example, it would not validate, IPs would not change, etc… the site continued to serve and ping to the same IP. But it appears to be working now.
It’s odd - the traffic and overviews showed zero traffic- zero visitors, zero requests, etc. All flatlined, 30 days out. Until a few minutes ago. Not sure what happened, nothing has changed, but now this account seems to be fully functional. Strange, but at least working.