DNS resolution problems from certain locations
We have received several reports on July 7th from clients who were experiencing problems with their Wild Apricot sites. Typical symptoms included 'Browser not supported' messages, site formatting and layout not properly loading, administration backend not functioning.
At the same time all our systems were running normal and our own tests for the same websites did not show any malfunctions - everything was loading up fine in our tests.
We believe that the root of the problem is related to DNS issues with one of the domains. Basically, from certain geographic locations / ISPs, one of the domains we use to host Javascript code and CSS code was not resolving.
The problem can be confirm by going into command line and running the following command:
ping f.camp8.org -n 20
If your location/ISP is affected, you would see an error message like this:
Ping request could not find host f.camp8.org. Please check the name and try again.
We have made a temporary configuration change this morning to serve Javascript and CSS files from another domain - this should resolve the problem for the moment. Make sure to clear your browser cache and restart your browser.
We are still investigating the root cause of the problem. If you have experienced this problem yesterday and/or still have this problem, please run the following commands:
1) (from the command line)
nslookup f.camp8.org >c:\test.txt
2) (from the command line)
nslookup origin-f.camp8.org >c:\test2.txt
3) (in your browser)
http://whatismyip.com - to determine your external IP address
Send the results (your external IP address and test.txt file) to our support team at support AT wildapricot.com
-
Dmitry Buterin commented
Problem resolution confirmed by at least one client.
-
Dmitry Buterin commented
We believe we have found the root of this problem (related to DNS configuration settings for one of our domains) and made appropriate adjustments. This should correct the problem right away in most cases - though it depends on DNS servers configuration of each Internet Service Provider and in some cases might take longer (up to 24-48 hours) until they update their DNS servers.
-
Dmitry Buterin commented
It sounds like the configuration change we made overnight did not solve the problem :-(
If you are experiencing this problem, we would really appreciate a full set of data from you:
1) Go to http://whatismyip.com - to determine your external IP address
2) Start button / All programs / Accessories / Right-click on 'Command prompt' under accessories, select 'Run as administrator')
Run 4 commands:
ping f.camp8.org -n 20 > c:\result.txt
ping f.camp8.org.edgesuite.net -n 20 > c:\result2.txt
nslookup f.camp8.org > c:\result3.txt
nslookup origin-f.camp8.org > c:\result4.txt
Send 4 resulting files (they will be in your C:\ folder - result.txt to result4.txt) and your external IP address to support.