Intermittent connectivity to pilotedge.net

[Keith Smith]

it would be great to get some debugging on this. If anyone is having the issue and is familiar with pinging and opening a command prompt, please execute the process I listed above (ping the server, let me know if it resolves to an IP).

Do this when you encounter a case where you can't reach the web site or connect to the server from the pilot client/plugin. The web site is hosted separately to the flight server, so something tells me this is DNS related rather than a connectivity issue at one of the facilities.

[dave_paige]

Don't know if this is related but yesterday, for the first time in a long time, the PE client for FSX just quit on me with no error message, disconnecting me from PE and I didn't even know. I fly in full screen mode so I didn't see the window go away. I just had a suspicion because I didn't hear any comms for a few minutes, went to check and it was gone. I restarted the client, reconnected and continued the flight with no further issues.

Dave

[JeffK]

Ok here is from about 6:50PM PST. You will notice that I did start pinging after the DNS flush. I was actually watching a stream of someone on twitch who couldn't contact anyone on the radio so he just kept trying to reach someone while disconnecting and reconnecting. He eventually got a hold of someone about 5-10 minutes later. The controller came back and said he was coming in broken.

PS C:\Users\Jeff> ping pilotedge.net
Ping request could not find host pilotedge.net. Please check the name and try again.
PS C:\Users\Jeff> ping pilotedge.net
Ping request could not find host pilotedge.net. Please check the name and try again.
PS C:\Users\Jeff>
PS C:\Users\Jeff> tracert pilotedge.net
Unable to resolve target system name pilotedge.net.
PS C:\Users\Jeff> tracert pilotedge.net
Unable to resolve target system name pilotedge.net.
PS C:\Users\Jeff> ping pilotedge.net
Ping request could not find host pilotedge.net. Please check the name and try again.
PS C:\Users\Jeff> ipconfig /flushdns

Windows IP Configuration

Successfully flushed the DNS Resolver Cache.
PS C:\Users\Jeff> ping pilotedge.net

Pinging pilotedge.net [72.14.185.55] with 32 bytes of data:
Reply from 72.14.185.55: bytes=32 time=67ms TTL=49
Reply from 72.14.185.55: bytes=32 time=68ms TTL=49
Reply from 72.14.185.55: bytes=32 time=65ms TTL=49
Reply from 72.14.185.55: bytes=32 time=65ms TTL=49

Ping statistics for 72.14.185.55:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 65ms, Maximum = 68ms, Average = 66ms
PS C:\Users\Jeff> tracert pilotedge.net

Tracing route to pilotedge.net [72.14.185.55]
over a maximum of 30 hops:

1 <1 ms <1 ms <1 ms DLJSGateway [192.168.0.1]
2 * * * Request timed out.
3 10 ms 12 ms 12 ms dtr02arsnca-tge-0-0-0-7.arsn.ca.charter.com [96.34.120.197]
4 26 ms 36 ms 25 ms dtr04snloca-bue-2.snlo.ca.charter.com [96.34.120.40]
5 27 ms 22 ms 27 ms bbr02snloca-bue-1.snlo.ca.charter.com [96.34.2.2]
6 39 ms 31 ms 31 ms bbr01snjsca-bue-6.snjs.ca.charter.com [96.34.0.0]
7 31 ms 32 ms 30 ms prr01snjsca-bue-5.snjs.ca.charter.com [96.34.3.1]
8 27 ms 27 ms 29 ms 96-34-154-58.static.unas.ca.charter.com [96.34.154.58]
9 26 ms 27 ms 41 ms ae7.bbr02.eq01.sjc02.networklayer.com [173.192.18.165]
10 30 ms 31 ms 32 ms ae0.bbr02.cs01.lax01.networklayer.com [173.192.18.151]
11 33 ms 34 ms 35 ms ae7.bbr01.cs01.lax01.networklayer.com [173.192.18.166]
12 72 ms 79 ms 77 ms ae19.bbr01.eq01.dal03.networklayer.com [173.192.18.140]
13 64 ms 65 ms 66 ms po31.dsr01.dllstx3.networklayer.com [173.192.18.225]
14 66 ms 64 ms 75 ms po31.dsr01.dllstx2.networklayer.com [70.87.255.66]
15 111 ms 79 ms 66 ms po1.car02.dllstx2.networklayer.com [70.87.254.82]
16 70 ms 68 ms 67 ms router2-dal.linode.com [67.18.7.94]
17 89 ms 77 ms 67 ms helns.timbabwe.com [72.14.185.55]

Trace complete.

[Keith Smith]

This confirms what I thought, there's a serious DNS issue going on. I'll get hold of the DNS provider or we'll have to relocate it quickly.

[JeffK]

Well I'm not so sure yet, it might be an intermediary's fault. I'm not an expert but the DNS servers on the internet propagate entries amongst themselves somehow. I was also just having difficulty getting forums.pilotedge.net working while the homepage was working. I jus switched the DNS servers on my adapter to Google's (8.8.8.8 and 8.8.4.4) and then the forums loaded. I'll try staying on Google DNS for a bit and see how if I notice a difference.

[kullery]

For what it's worth, yesterday we had issues reaching selected sites (including pilotedge.net and the forums) from NE Ohio while using Time Warner DNS servers (209.18.47.61, 209.18.47.62). We added the google DNS servers (8.8.8.8, 8.8.4.4) on all of our devices and all access was restored.

Called Time Warner and they told us that they were not aware of any issues, but they admitted that all of their support people also use 8.8.8.8, 8.8.4.4 as additional DNS emtries.

[Keith Smith]

We're not using dynamic DNS, the servers are on static IP's. Working with GoDaddy now.

[Keith Smith]

godadfy verified there was an issue and says they will make some changes.

if anyone has problems resolving the web site, forum, voice server or main server, let me know here.

[Peter Grey]

Just had the issue for a split second with the forum, took a reload to be able to connect to it. Ping showed normal.

[Pieces]

Same issue as Peter just now.