Thomas Pfarr <firstname.lastname@example.org> wrote in article <email@example.com>…
This tends to indicate the nameserver is not making the query properly up
the food chain. One thing to try is to use a different nameserver. How
you posting to this newsgroup?
I’m posting from work where the nameservers are translating all your sites
correctly. I can traceroute to router.qnx.com (220.127.116.11) but no
further. I assume you have the packets blocked beyond that point.
I guess Adam said that at other branch of this thread above.
From home on the @home network the > www.qnx.com > and qdn.qnx.com do not
translate to addresses from the @home namesevers. support.qnx.com does
translate but I guess that server no longer exists.
qdn.qnx.com is the same as support.qnx.com
It stays third after router.qnx.com. It works perfectly, but not for me ;-(
(or I should use other proxy, exactly that’s I’m doing now)
I can reach quics.qnx.com (“developers stuff”), this site is a second after router
[18.104.22.168], but cannot reach get.qnx.com (third too in tracert table)
I can’t ping it from
I will try to contact someone in the @home network. (May the force be with