Any idea on the following error in the log file? Can't post in discord otto thinks it's a repeat message, otto should be schooled!!!.

0:00:00.368 E/NET: Download failed with error: 6 for URL http://lookup.x-plane.com/_lookup_12_/server_list_12.txt
0:00:00.368 E/HTTP: Error: Couldn't resolve host name (for URL http://lookup.x-plane.com/_lookup_12_/server_list_12.txt)
0:00:00.368 E/HTTP: Curl Error Buffer: Could not resolve host: lookup.x-plane.com
0:00:00.368 E/HTTP: HTTP Headers:
0:00:00.368 E/NET: Download failed with error: 6 for URL http://lookup.x-plane.com/_lookup_12_/server_message_12.txt
0:00:00.368 E/HTTP: Error: Couldn't resolve host name (for URL http://lookup.x-plane.com/_lookup_12_/server_message_12.txt)
0:00:00.368 E/HTTP: Curl Error Buffer: Could not resolve host: lookup.x-plane.com

No, Otto is right. Out of 7 lines, 3 are duplicate.

Well, otto has kept this message and other from getting to the powers that be!!! Maybe it will get fixed, maybe it won't. Won't be bothering with reporting anymore, done wasting my time.

Is the message accepted if you only post the last 4 lines?

 

P.S: The links in that message work for me.

Edited October 19, 2025Oct 19 by Bjoern

6 hours ago, Bjoern said:

Is the message accepted if you only post the last 4 lines?

 

P.S: The links in that message work for me.

Nope, must be time timestamp or http doing it. They work today, must of been a problem on L/R's servers.

Can I just say, Discord is NOT the place for bug reports. It's at best... another way to ask for community help. Please use the bug reporter or official support for anything urgent or related to betas. Otherwise we will not see it.

On 10/17/2025 at 4:28 PM, Mike_CFII_MEL said:

0:00:00.368 E/HTTP: Error: Couldn't resolve host name (for URL http://lookup.x-plane.com/_lookup_12_/server_list_12.txt)

There was a DNS problem. I'm sure their servers were fine.

Cheers

7 hours ago, Luke said:

There was a DNS problem. I'm sure their servers were fine.

Cheers

I agree. 

It surprises me that people who are tech savvy enough to alter the lights in X-Plane 12 and run a multi-monitor setup AND stream that experience regularly on the internet get totally thrown off the road by something as obvious as this. Even if you are not very versed in internet protocol or reading the log.txt just typing in:

"What does could not resolve host mean"

into your internet browser will give you a very suitable explanation of the problem (most notably that the error is very likely on your side), and one can save himself the trouble of trying to file a "bug report on Discord 😐" or take up Laminar Supports time.

 

12 minutes ago, Litjan said:

I agree. 

It surprises me that people who are tech savvy enough to alter the lights in X-Plane 12 and run a multi-monitor setup AND stream that experience regularly on the internet get totally thrown off the road by something as obvious as this. Even if you are not very versed in internet protocol or reading the log.txt just typing in:

"What does could not resolve host mean"

into your internet browser will give you a very suitable explanation of the problem (most notably that the error is very likely on your side), and one can save himself the trouble of trying to file a "bug report on Discord 😐" or take up Laminar Supports time.

 

I connect just fine with 12.3.b5 on not one but "four" computers and with 12.3.b6 just minutes later on all four computers I can't connect with the above message, then back to 12.3.b5 and all is fine... sorry, the issue was not on my end!

8 hours ago, DeltaWho said:

Can I just say, Discord is NOT the place for bug reports. It's at best... another way to ask for community help. Please use the bug reporter or official support for anything urgent or related to betas. Otherwise we will not see it.

Hence my attempt to post on discord FIRST to see if others were having the same issue before posting what could be a bogus bug report. But with ottobot Discord has become a waste of time on more than one occasion. 

Edited October 20, 2025Oct 20 by Mike_CFII_MEL

2 hours ago, Mike_CFII_MEL said:

I connect just fine with 12.3.b5 on not one but "four" computers and with 12.3.b6 just minutes later on all four computers I can't connect with the above message, then back to 12.3.b5 and all is fine... sorry, the issue was not on my end!

There are certainly server outages and internet quirks sometimes - usually when I suffer something like this I start with rebooting my router and DSL modem and then run the network troubleshooting in Windows, which will often reset my network adapter. If that does not help I wait for a few hours...and often these things clear up all by themselves.

If there is a prolonged outage at Laminar´s side you would certainly read about it here and/or on other forums 🙂

 

From a CMD window one can always run a very simple test:

> nslookup <target internet name>

to get an answer like :

C:\WINDOWS\system32>nslookup sapo.pt
Server:  UnKnown
Address:  192.168.157.10

Non-authoritative answer:
Name:    sapo.pt
Address:  213.13.145.114

C:\WINDOWS\system32>

or, if you want to "dig" more into the DNS service

> nslookup (ENTER)

which will show you what default DNS server is being used and from there you can start testing names like:

> lookup.x-plane.com
Server:  UnKnown
Address:  192.168.157.10

Non-authoritative answer:
Name:    lookup.x-plane.com
Addresses:  108.157.113.109
          108.157.113.10
          108.157.113.40
          108.157.113.68

>

You exit "nslookup" with "exit"  or CTRL-C

If you get an error for the name you're trying to resolve, like:

C:\WINDOWS\system32>nslookup x-planeIStheBest.x-plane.com
Server:  UnKnown
Address:  192.168.157.10

*** UnKnown can't find x-planeIStheBest.x-plane.com: Non-existent domain

C:\WINDOWS\system32>

then something is wrong with either your DNS service or the server being queried "on the other side".

You can use many services to try to find more about the error to isolate the source, such as "downforeveryoneorjustme" or "digwebinterface" which gives you a web interface to run different DNS queries in a rather efficient way.

 

Edited October 20, 2025Oct 20 by jcomm

8 hours ago, Litjan said:

There are certainly server outages and internet quirks sometimes - usually when I suffer something like this I start with rebooting my router and DSL modem and then run the network troubleshooting in Windows, which will often reset my network adapter. If that does not help I wait for a few hours...and often these things clear up all by themselves.

If there is a prolonged outage at Laminar´s side you would certainly read about it here and/or on other forums 🙂

 

Whenever I have a network/connect type issue, side from rebooting the router and my switch I also perform the following via powershell. I wouldn't trust Windows troubleshooting to do anything! Most of the time it's unable to help at all and all it does is waste time.

1. ipconfig /flushdns
2. ipconfig /release
3. ipconfig /renew
4. netsh winsock renew

Then a fresh reboot of my computers.

Edited October 20, 2025Oct 20 by Mike_CFII_MEL

It was likely the major AWS outage.