Skip to main content

Massive Drop in Awstats

Comments

5 comments

  • Infopro
    Output removed. Please don't post that sort of output without removing/modifying all information like emails, IPs, domain names.
    0
  • kwmlr439
    Output removed. Please don't post that sort of output without removing/modifying all information like emails, IPs, domain names.

    Thank you so much! That is one of the reasons I made a note for the admin in there since I am new to the VPS world; it is much appreciated. :)
    0
  • cPanelMichael
    Hello :) The following third-party URL may help to explain the differences in how Awstats calculates visitors compared to other statistics applications: Google Analytics vs Awstats " which is better, more accurate, useful? | Ultimate Web Builder Blog You may also find this document helpful: Apparent Discrepancies in Bandwidth Usage Statistics - Documentation - cPanel Documentation Thank you.
    0
  • kwmlr439
    Hi Michael, After a couple days digging on what's the issue I found out that a server misconfiguration is perhaps the cause. After a DNS health check I found the following errors; hope you can help. Superfluous name server listed at parent: ns1.bluehost.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. Superfluous name server listed at parent: ns2.bluehost.com A name server listed at the parent, but not at the child, was found. This is most likely an administrative error. You should update the parent to match the name servers at the child as soon as possible. Total parent/child glue mismatch. The parent lists name servers that the child doesnt know about, see details in advanced. This configuration could actually work but breaks very easily if one of these zones change slightly. Too few IPv4 name servers (1). Only one IPv4 name server was found for the zone. You should always have at least two IPv4 name servers for a zone to be able to handle transient connectivity problems. Reverse for XXX.XXX.XXX.XXX points to an unknown host name (XXX.XXX.XXX.XXX.unifiedlayer.com). The PTR record for the address points to an unknown host name. Reverse for XXX.XXX.XXX.XXX points to an unknown host name (XXX.XXX.XXX.XXX.unifiedlayer.com). The PTR record for the address points to an unknown host name. 2 different serials found. The SOA serial is not the same on all name servers. This is usually due to misconfiguration, but can sometimes be the result of slow zone propagation to secondary name servers. 2 different SOA records found. The SOA record are not the same among all name servers. This is usually due to misconfiguration. Reverse for XXX.XXX.XXX.XXX points to an unknown host name (XXX.XXX.XXX.XXX.unifiedlayer.com). The PTR record for the address points to an unknown host name. Delivery over IPv4 to root@server.maindomainname.com[/EMAIL] could not be done. Failed to deliver email for SOA RNAME of focusdomain.com (root.server.maindomain.com) using root@server.maindomain.com[/EMAIL]. DNSCheck failed to deliver email to the email address listed as the one responsible for the zone.
    0
  • cPanelMichael
    The output you provided should not make a difference with statistics calculation unless the domain name does not resolve to the correct IP address. Are you using your domain registrar's/hosting provider's name servers or are you attempting to create and utilize your own private name servers? This guide should help explain the difference: [Tutorial] Nameserver configuration on cPanel servers Thank you.
    0

Please sign in to leave a comment.