Jump to content

Recommended Posts

Posted

Apparently the dcs_update binary has an issue with DNS lookups for update.eagle.ru on ipv6 enabled systems.

 

For some reason ipv6 name servers can't get a valid record for update.eagle.ru using google's opendns(8.8.8.8) there is a record being returned:

 

E:\DCS World OpenBeta\bin>nslookup update.eagle.ru 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    1231349722.rsc.cdn77.org
Address:  185.59.220.12
Aliases:  update.eagle.ru
         updates.digitalcombatsimulator.com

 

While using google's ipv6 opendns(2001:4860:4860::8888) there is no valid record:

 

E:\DCS World OpenBeta\bin>nslookup update.eagle.ru
Server:  google-public-dns-a.google.com
Address:  2001:4860:4860::8888

*** google-public-dns-a.google.com can't find update.eagle.ru: Non-existent doma
in

 

This is likely a faulty setup on your bind or cdn77.org's setup.

 

The workaroung involves adding the ips manually to your host file.

Posted

IPv6 as the cause

 

So I ran into this as well, and I turned off IPv6 and it worked without incident (where this doesn't seem to be a problem with the non-beta DCS). I'd file this one off as a bug -

 

for the uninitiated - start-->run-->ncpa.cpl

right-click on your NIC and go to properties

uncheck IPv6.

  • Recently Browsing   0 members

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