Solved 3CX 3BC Raspberry Pi Download link does not resolve?

[highptech]

Hi everyone,

I am trying to set-up a back-up secondary SBC on a Raspberry Pi 3 B+ for testing. Our RPI 4s are on order.
When i try to download the software from any of the links below:

wget http://downloads.3cx.com/downloads/sbc/3cxsbc.zip -O- | sudo bash

or

wget https://downloads-global.3cx.com/downloads/misc/d10pi.zip; sudo bash d10pi.zip

it give me the following error messages:

" --2020-12-02 13:42:43-- http://downloads.3cx.com/downloads/sbc/3cxsbc.zip
Resolving downloads-global.3cx.com (downloads-global.3cx.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address downloads-global.3cx.com

or

" --2020-12-02 13:42:43-- https://downloads-global.3cx.com/downloads/misc/d10pi.zip
Resolving downloads-global.3cx.com (downloads-global.3cx.com)... failed: Temporary failure in name resolution.
wget: unable to resolve host address downloads-global.3cx.com
bash: d10oi.zip: No such file or directory"

I tried this with 2 new 32GB Class Micros SD cards and 2 different versions of Raspbian OS Lite and i got the same results.

MicroSD #1 Debian 10.6 Buster

MicroSD #2 Debian 9.8 Stretch

can anyone point me to the right direction?

 

[cobaltit]

That's a DNS issue. It has nothing to do with pi3 vs pi4 or sd cards. Can you ping downloads.3cx.com or downloads-global.3cx.com from network?

 

[JohnS_3CX]

You are facing DNS resolution issues, so your Pi is unable to resolve the IP of the downloads server.

I can confirm that the downloads server is working correctly. If you believe your local DNS is also working correctly then you should look up "wget temporary failure in name resolution"

 

[highptech]

You are facing DNS resolution issues, so your Pi is unable to resolve the IP of the downloads server.

I can confirm that the downloads server is working correctly. If you believe your local DNS is also working correctly then you should look up "wget temporary failure in name resolution"

Thank you...I managed to figure out what the issue was.

I was able to ping 8.8.8.8 but not google.com from Raspberry PI but everything was fine from my computer through Command Prompt.

In RPI, command sudo /etc/resolv.conf was showing me the following the details:
nameserver ::1

which was very weird because i even set the static IP details and nameservers to gateway address and 8.8.8.8. It is suppose to show:
nameservers (my gateway address)
namerserver 8.8.8.8

After looking up different solutions online with no good result for my case, i took the Raspberry Pi home and did a test there and everything was fine even though it is the same ISP and Modem.

Anyways, for my case the solution was to turn off the IPv6 in the router/modem setting at the office and everything was fine after. Somehow the IPv6 was turned on after recent firmware update and router was in dual mode (IPv4 and IPv6).