WHM/CPanel login DNS error/page not found

[digitalSite]

I have been having this problem for a few months and it happens every now and then. Sometimes I cannot access it before 5pm; sometimes i cannot access after 5pm; and then other times I cannot access them for an entire day, but at midnight, it all goes back to normal and i can see all the pages again.

I cannot log into WHM or CPanel using:

http://mydomain.com:2086
https://mydomain.com:2087
http://myIP.com:2086
https://myIP.com:2087

I get a "Page Cannot Be Displayed" page that says "Cannot find server or DNS error."

I now have a reseller who says that his clients get a the same error page when trying to view the reseller's site or their own web sites. I am exhausted and have spent weeks trying to figure out what the problem is.

I thought it was my ISP's problem, but after reseller complained, now I am thinking it may be a DNS error? I have visited the dnsreport.com site and my server provider said that everything seems fine. I have also checked reseller's nameservers - they seem fine too. Only one reseller has complained about this issue.

Can someone double check that I have created resellers' nameservers correctly?
1) Register domain name.
2) Assign namservers to Ips in the "Manage Namerserver IPs" are in WHM
3) Register domain name's nameservers at registrar: ns1.domain.com, ns2.domain.com
That's it, right? (I have gotten confused with all the entry A and entry B talk...don't know if I need to do this or not)...

Anyway, all of my resellers have a bunch of clients, but this one reseller is saying that his clients are "sometimes" unable to view his sites.

I don't understand. Is anyone else having similar problems or this just me? Can someone offer some advice on what may be causing this "Page Cannot Be Displayed" error pages?

Any help is GREATLY appreciated.
Thank you!

cPanel.net Support Ticket Number:

[GrimReaper]

Hi There,

I know this was posted a while ago and this probably won't help you. However I just had this problem and found that it was caused by the user having screwed up their .htaccess file in their "www" directory.

Anyone experiencing this problem may want to check it first before mucking things up on their server(s).

Chris.