Jump to content

Recommended Posts

Posted

I can´t not enter on the site, not sure what happens

For Work/Gaming: 28" Philips 246E Monitor - Ryzen 7 1800X - 32 GB DDR4 - nVidia RTX1080 - SSD 860 EVO 1 TB / 860 QVO 1 TB / 860 QVO 2 TB - Win10 Pro - TM HOTAS Warthog / TPR / MDF

Posted (edited)

Works fine here.

 

My guess is that there's something funny going on with your ISP DNSes.

 

EDIT: Try with a different DNS - https://developers.google.com/speed/public-dns/

Edited by EtherealN

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted

Same. Maybe they changed their public IP.

"You see, IronHand is my thing"

My specs:  W10 Pro, I5/11600K o/c to 4800 @1.32v, 64 GB 3200 XML RAM, Red Dragon 7800XT/16GB, monitor: GIGABYTE M32QC 32" (31.5" Viewable) QHD 2560 x 1440 (2K) 165Hz.

Posted

Yeah, dug a bit and I appear to be getting different IP's when I track the simhq domain through a web service and when I track it from my own machine. Might simply be that something happened to the domain, but my ISPs DNS hasn't noticed yet and thus still gives the correct IP.

 

EDIT: there we go. Good news.

 

Probably was an IP change and it just took different amounts of time to propagate for different ISPs.

[sIGPIC][/sIGPIC]

Daniel "EtherealN" Agorander | Даниэль "эфирныйн" Агорандер

Intel i7 2600K @ 4.4GHz, ASUS Sabertooth P67, 8GB Corsair Vengeance @ 1600MHz, ASUS GTX 560Ti DirectCU II 1GB, Samsung 830series 512GB SSD, Corsair AX850w, two BENQ screens and TM HOTAS Warthog

DCS: A-10C Warthog FAQ | DCS: P-51D FAQ | Remember to read the Forum Rules |

|
| Life of a Game Tester
Posted
Interesting... My office and home are on the same ISP, but I can only access SIMHQ at home.

What sorcery is this!? :shocking:

 

Maybe you get different nameservers from the two locations? Sounds like trouble with DNS Time-to-Live in conjunction with an unplanned or badly prepared IP-change.

Posted

Their Twitter page now explains the problem:

LP

 

modules:

F5-E / A4-E / A-10A / AJS-37 / SA-342 / UH-1H / Ka-50 / Mi-8 / CA

 

would buy:

OH-58 /AH-64A / AH-1 / Sepecat Jaguar / F-111

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...