TwoFlowersLuggage wrote:
Yeah - it looks like Bryan moved the problem nameserver from the primary to the tertiary
I did try that for a while, but ended up having to remove the dang thing altogether
IMO, DNS issues are THE worst as it takes a long time to see results of any changes made due to propagation & that has been my focal point since early on.
Turned out that anything associated with the ip address that nameserver was pointing to ended up going wonky. I was using the ip as AAPK's main ip starting last Wednesday night, which was newly issued to us with new server I set up at that time.
Had to remove it from anything & everything associated with our domain to finally make headway.
I've moved AAPK to a new server probably 10 times since inception, & this has been by far the most trying experience. I was honestly expecting it to be a one night job
Hope to get the all lingering issues cleared up & get the looks & full functionality of the forum shaped up here in the next couple days.
Please bear with me on things a bit longer. Appreciate everyone's kind words & input.
) spot in the list. That means it is getting far fewer hits (probably none in most situations) and the performance has significantly improved.
