Problems connecting to Lynxmotion.com

Since at least Friday until today I have not been able to connect to Lynxmotion.com on either my desktop or my notebook :frowning: I tried several things including flushing my DNS cache and the like. But today I decided to do something about it when I could not see the pictures in Zenta’s post :wink: On both of my machines I was using the default DNS servers from my provider.

I just finally resolved it :smiley:. Here is what I did. I did a goggle of: DNS Server List.
I connected up to: dnsserverlist.org/

This showed me a list of preferred servers. The top two were the same, so I then went to configure my computer, by bringing up the TCP/IP parameters. On Windows 7 I did this by bringing up the Network and Sharing control panel. I clicked on the Local Area network link (main computer) which brought up a status dialog and I clicked on properties on the resulting dialog I then double clicked on the TCP/IPv4 line which brought up another properties dialog, which shows the current DNS server properties. Mine was set to Obtain DNS server address automatically. I changed this to manual. For the preferred DNS server item I used the one that DNSSERVERLIST gave me. For alternate DNS server, I did what Nathan (AcidTech) recommended and set it to a goggle DNS server ( 8.8.8.8 ). I then OKed out of the dialogs, closed my browsers and opened a new one…

Hope this helps anyone else that may be having this problem.
Kurt

What happened was we moved our website to a better host location a while back. We are getting fiber here very soon so we decided to hold off on moving the mail. They asked me 2 weeks ago about moving the mail and I told them not yet. Well they forgot and moved the server that was doing our mail. That was bad enough, but to make matters worse the same server was our DNS server! This caused the hit and miss availability of the website. In fact I never had a problem connecting and didn’t know anyone else was. So it is all back to normal now. Anyone unable to connect would be due to DNS caching the wrong information.