Ok, here we go.
First, the problem in it's most basic form: I can not access the following domain from any device that is behind my router: https://mylocaldirectory.co.business
Second, a brief timeline leading up to the problem:
Day 1: Purchased domain and hosting from the same provider.
Day 2: Install WordPress and start to construct website (full access).
Day 3: Denied access to that domain, the WordPress admin page associated with that domain and the cpanel page associated with that domain BUT ONLY FROM BEHIND MY ROUTER. I've had at least 10 people, including the AT&T tech who came to my house to diagnosis the problem (obviously unsuccessfully), that have been able to pull up those pages on their computers or their phones via 4G networks.
The consensus so far is a DNS issue. (I forgot about Experts Exchange initially, so this consensus is from posting on some other forums and from AT&T.)
That may or not be the case, but it does sound like a logical place to begin.
I'm at a crossroads now in this post. Do I now list all of the things that have been suggested to me to attempt to fix the issue or do I now list what I think are the KEY points of the issue and why nothing that has been presented as a possible solution could not have (and have not) solved the problem?
I'm not a techie although I can navigate thru Windows a little bit. But I am fairly good at analyzing possibilities and so this is what I consider as the key points to consider while diagnosing this issue: (Spoiler: number 6 is the variable)
1. Access is only denied from behind my router.
2. When not behind the router, sites are fully accessible (as I'm sure you will test).
3. I'm only denied access to this one domain page and its associated pages
. All other pages load and function normally.
4. I installed Hide My IP VPN and when it's enabled I can access the domain pages from behind the router.
5. AT&T came out and installed a new upgraded router (physical device) with a new firmware version. This leads me to believe that even if it is a DNS problem, that a DNS issue internally within the router is not a practical possibility as having the same DNS issue that was not an issue two days prior, in a two-year-old router and then the same issue popping up instantly in a brand new router would be a PowerBall winner type of statistical possibility. But then again, someone eventually does win the PowerBall.
I'm asking for forgiveness as I don't mean to come across as rude in this next part. That's certainly not my intention, but this next key point is where the diagnosis needs to begin. Right now everyone who has read the post up to this point is now thinking how to diagnosis a DNS issue on the Windows devices on my side of the router. BUT TAKE NOTE:
6. MY ANDROID PHONE IS ALSO DENIED ACCESS TO THAT DOMAIN WHEN TRYING TO ACCESS THAT DOMAIN FROM BEHIND THE ROUTER. My Android phone has nothing to do with the Windows computers, other than they both are using the router as a gateway. The phone is communicating directly with the router. This tells me that the problem is not with the DNS configuration of the Windows computers, else my Android would not be affected.
A. Is it a problem with my Window 10 DNS config? No, or else the Android would be able to access the domains via the router.
B. Is it a problem with the physical device? The router has been changed and upgraded. So, highly unlikely.
C. Is it a problem with the DNS settings inside the router? I don't see how as again, the router was replaced. But I guess that is a possibility though not likely.
D. Is it a problem on the AT&T side of the router? They did all kinds of tests and say "no".
E. Is it a problem with my hosting provider? They can access the domain page as well and anyone else I've asked to visit that page as a test, as well as I can access that page on my Android (via 4g). So I would have to say "no" to this one as well.
So what's left? The solution, I guess.
Not being a techie but an analyst, my question would be: What could change from Day 2 to Day 3, DNS or otherwise, (and what would cause that change?) that would deny me access to ONLY ONE SPECIFIC domain page, and that denial only from behind my router, that affects both Windows and Android, but can be "worked around" via VPN, and has seemingly nothing to do with the physical router itself? What kind of DNS issue could that be? Or is it even a DNS issue at all?
Where are all the non-Windows DNS configurations located? At the router? Beyond the router? What else besides a DNS config could be the issue? If I wanted to deny access of a specific IP to a specific web page, what are the options to accomplish that goal, DNS or otherwise?
I need a logic-based diagnosis here vs a testing-based diagnosis, as any test that only incorporated the Windows eco-system would seem to be irrelevant at this point.
But for all of you who just have to know, and will only focus on the Windows side, here are the relevant background details:
Devices denied access behind the router: Two specification-qualified Windows 10 computers (no relics). One is Wifi, the other is hard-wired.
One personal Android phone. Access denied behind the router, access available via 4G network.
One AT&T tech guy's phone, (didn't ask if it was Android or IOS). Same results, access denied behind router, access available via G network.
Computer solution actions:
Both computers restarted multiple times.
Anti-virus and firewalls temporarily disabled.
VPN installed on one computer to test. Test successful, access available via VPN.
Attempted multiple browsers, (Edge, Chrome, Opera). No variances, access denied via all browsers.
No known Windows update, programs installed or Configuration changes within those two days. With two computers, it's possible that I did download something that I've forgotten about, during those two days. But I certainly didn't download anything to both computers, and again, that would seem to have nothing to do with the Android.
Various people did Pings and some type of NSlookup (something like that), which as far as I can tell (I'm not a techie!) returned no definitive information of any value (other than that those things aren't the problem, which I guess has some value under normal circumstances, but again, nothing to do with the Android.)
Rebooted router several times
AT&T remote testing of router.
AT&T onsite testing of router.
Factory reset of router.
Replacement of router.
Supposedly AT&T also did a forced port change. But I have no way of know if they actually did that. I can confirm that with the AT&T tech directly next week, but I'm 100% certain he doesn't want a call from me this weekend. A port issue could actually account for both Windows and Android devices, but what could have changed overnight that one port that had been working correctly would now deny me access to just one particular site page? What would have to happen that a port would just stop allowing access of just one domain?
Tried the 8888/8844 thing.
Scanned for malware and virus'. (No virus', a couple of low-grade malware infected programs that I use and have been installed loooooong before this issue arose. No common malware flagged programs installed on both computers and not relevant to the Android access denial.)
Banged head on wall incessantly for several days. That didn't do anything to solve my domain access denial but I believe I did my part as an American, to prop up head-ache relief stock prices during recent stock market volatility. If a solution is discovered, I will also do my part to prop up alcohol stock prices as well. :)
It doesn't seem likely that I would have been site-jacked on a site that was only one day old, unpublished and that to which I can still gain entrance (when I'm not behind my router) and that utilizes a fairly strong password.
Blacklisting seems unlikely as the domain provider and the hosting company are the same and they can access the web page and everyone else that's tried and not behind my router can access the page.
Don't think it's a firewall issue. Standard Windows firewall - nothing there to block Android.
All of the potential solutions provided thus far by the other forums and AT&T have completely disregarded the Android not being reliant on the Windows 10 DNS configurations component of the equation. As proper testing techniques go, completing all of those tests is probably the thing to do just to eliminate those as possibilities. And I have completed all of the above suggestions.
Seems like any possible solution would need to take into account both Windows and Android devices starting at the router at a minimum.
Wow. All this to access one domain. Ironically it's the one site that I need to access to earn some income this week. Can't sell spots in my directory if I can't finish compiling the site. That Murphy guy. As per his reputation, has shown up at the most inopportune time.
Thanking you in advance for your time, help and effort.