Hi, this is not so much a question, but a solution to a problem I encountered when using PRTG. I'm a home user, and though this problem really applies to anyone running a server for the first time, it applied in my case when trying to access the web interface of PRTG.
After resetting my router, my registered domain, a private site with an SSL, could no longer reach my PRTG server PRTG. Let's call it "myprtgsite.net" At first I tried contacting my web hosting provider, and I struggled for days with them, but they couldn't help. Along the way I realized I could still connect to the site by entering my computer name along with the port number. So "MyPC:443" worked for example. Finally, I could connect.
However, my SSL was gone when I did this, and I didn't like that workaround anyway. I had paid for the domain name with the expectation that it would work. Finally, I reached someone at the web hosting company who recommended I call my ISP, so I did.
This turned out to be the right decision. Verizon, my hosting provider, has SON, or "self organizing network" turned on by default. They suggested turning it off, and wallah! My website name worked again. After a week, the problem was solved. "myprtgsite.net" didn't lead to oblivion anymore.
Being more of a networker in training than most of you guys, I'm sure, I don't quite understand how the SON feature interfered with the DNS server and blocked the URL from connecting. The lady at Verizon explained that the feature could be a little buggy and needed updating. Well, until it does, I know I'm going nowhere near it. But does anyone have a better answer, as to why exactly the SON feature blocked my server from being accessed by my domain name? Thanks!