*** This bug has been confirmed by popular vote. ***

I updated to 44-1 successfully using WLAN connection without any problem.

I have a UK variant device. 
Perhaps firewall issue with your WLAN.

(In reply to comment #2)
> I updated to 44-1 successfully using WLAN connection without any problem.
> 
> I have a UK variant device. 
> Perhaps firewall issue with your WLAN.
> 

No, because the same domains resolve on the same device on the same WLAN if I
access them through the device's web browser. The domains only fail to resolve
if I use the device's app manager.

Try setting your WLAN on N900 to use Goggle's DNS

8.8.8.8
8.8.4.4

(In reply to comment #4)
> Try setting your WLAN on N900 to use Goggle's DNS
> 
> 8.8.8.8
> 8.8.4.4
> 

If it was the DNS, why would it resolve on the N900's web browser?

The first post shows you are getting different DNS results between Cellular and
WLAN connections.  Whilst the address may resolve in the browser that does not
necessarily mean you are getting to the right server, there may be some
configuration problem in the caching network effecting your ISP.  

For anyone having this problem it would be worth trying different DNS servers, 
and posting what ISP you are using and your public IP address from
http://www.whatismyip.org/ so that it can be looked into.

(Should this be moved this to maemo.nokia.com website product for now so that
the appropraite people who can check the server config will see it?)

Comment 7 Andre Klapper 2010-01-22 16:58:38 UTC

Has this happened again in version 2.2009.51-1?

(maemo.nokia.com has nothing to do with the repositories.)

From time to time I've got the same problem (with version 2.2009.51-1).
To work around I deactivate both repositories and reactivate them after a few
seconds.

I have had the same issue, I don't have a 3G data connection so it was quite
noticeable for me. My workaround was to manually set the DNS servers using the
maemo gui for the wifi connection. I set my primary as a local ISP dns server
and the secondary to one of the opendns servers.

This seems to have resolved the issue, but is still a royal pain to set for
each new wifi connection.

But at least I can now install apps from the official repo and install deps
that were required for apps in the extras repo.

(In reply to comment #9)

Also please note that when doing an nslookup on downloads.maemo.nokia.com did
return a pingable IP address! For some reason it returned an IP (after a few
seconds) that obviously didn't have the repo stored on it...

Please look into hot repository-and-HAM discussion -

http://talk.maemo.org/showthread.php?t=41544&page=10

It can explain why there is a difference between Akamai caching servers on
cellular access and wifi access.

Your cell provider uses akamai and it caches a repository Release and signature
file (look into discission a couple of pages). Your WiFi provider uses either
direct server address or another cache server.

Comment 12 Andre Klapper 2010-02-16 20:31:13 UTC

So this is not a bug according to comment 11?
This still happens in 3.2010.02-8 I assume?

(In reply to comment #12)
> So this is not a bug according to comment 11?
> This still happens in 3.2010.02-8 I assume?
> 

I can't really comment on if it's the same as comment #11 or not as I don't
really understand what they are talking about there.

I do know the issue still exists in 3.2010.02-8.002 (according to "About
product") though. Also please note that it's not just the update manager that's
affected in my case. It also affects desktop widgets and pixelpipe and anything
seemingly that relies on a direct network connection. (MicroB seems to work
really slowly, but it works eventually strangely enough)

My fix for it is when I change from "nameserver 127.0.0.1" to "nameserver <isp
dns server ip>" in my resolv.conf, everything seems to function correctly.

Some sort of dnsmasq misconfiguration issue somewhere? (I haven't touched any
of the dnsmasq config outside /etc/resolv.conf)

If anyone needs more info, I'm more than happy to provide. (I don't have a
cellular data connection however) It's a very strange bug. 100% repeatable
though.

I've been having this since PR 1.1. I can't try PR 1.1.1, because the bug
breaks the updater, and UK doesn't get the update in any case.

Tried both OpenDNS and TalkTalk.

i have changed the nameserver to the dns ip of my isp and now it works not only
the installation from ovi store but the imap.gmail too :)
thanks

(In reply to comment #15)
> i have changed the nameserver to the dns ip of my isp and now it works not only
> the installation from ovi store but the imap.gmail too :)
> thanks
> 

the problem is that this setting works only at home because with wap i have to
put again 127.0.0.1

Comment 17 Andre Klapper 2010-03-27 18:43:42 UTC

(Questions that miss technical background:)
So is this an application manager issue? Is a proxy setting somehow involved?

(In reply to comment #17)
> (Questions that miss technical background:)
> So is this an application manager issue? Is a proxy setting somehow involved?
> 

In my case at least, it seems to be a dnsmasq issue when using WLAN. No
proxies. Setting resolv.conf to point to my isp dns server when in WLAN mode
fixes the issue, but that's not ideal obviously.

Ah, I've had a similar bug (Bug #9448) which was blocking my IMAP in Modest
(comment #15 had that problem too). I just realised this is a DNS problem. I
have a dodgy router (iiNet BoB) which also causes problems in Ubuntu.

Setting my DNS to 8.8.8.8 in resolv.conf instantly fixes this for me (for
email, apt-get, OM Weather, and everything else). However, what I don't get is
that setting the DNS server in the connection setup has no effect.

That is; if I select my WiFi connection, go to Advanced Settings, IP Addresses,
uncheck "Auto-retrieve DNS" and enter 8.8.8.8 and 8.8.4.4 in the Primary and
Secondary DNS addresses, it will still fail.

If I look in resolv.conf, I see 127.0.0.1 still. Why doesn't resolv.conf
reflect my active WiFi connection's DNS servers? I would like a way to fix this
without having to manually edit resolv.conf (because I want to use the custom
DNS servers only for this particular connection).

Comment 20 dwilms 2010-05-11 13:32:08 UTC

*** Bug 8722 has been marked as a duplicate of this bug. ***

Timeouts for 
Modest (pop.gmx.de, pop.gmail.com) and 
App Manager with repositories at https://downloads.maemo.nokia.com/
but only in a certain router/isp combination:

Wifi Router: Alice Modem 1121 WLAN which is an ISP branded Siemens
S1621-Z220-A.
ISP: Alice Hansenet Germany.
N900: Global PR1.2 (Nearly vanilla - only root access is installed, so i could
use ping) and before with PR1.1, too 
No proxies; no router firewall enabled; browsing including https-sites does
work 

Using google DNS 8.8.8.8, 8.8.4.4 everything works fine.

I have the exact same problem after a fresh install of the newest firmware.

The problem is that Nokia is using an invalid Akamai Certificate, which is
publishing the Akamai domain name instead of the Nokia domain name which is
expected from the Apt manager.

Nokia needs to get the person who does the web certificates within their
organization to check that Akamai is also forwarding Nokia certificates instead
of their own.

(Akamai is a service hired by Nokia, NOT by anyones ISP).

This is the hint from the logging

apt-worker: =====Ignoring version from wrong domain=====: tutorial-home-applet
0.6.14+0m5

Because apt-worker is expecting nokia.com and getting the file from akamai.com

When will this annoying bug get resolved? Who is taking care of it?

Hi guys,

same issue for me. I've got the N900 a few weeks ago (I have a data option) and
everything worked fine. This month I've used the mobile connection more
intensively and used up the data volume. No problem so far I thought, since I
can fetch mail and updates on the Wifi. But it's not possible. Mail for
exchange (MfE) always says "Invalid host address for Exchange server" and the
update manager has problems with the repos located at nokia (As mentioned
before). Foreca-weather isn't able to get its data as well. However, browsing
the Internet and fetching IMAP-Mails works fine.
To do some research I then set up a Wifi connection using my notebook whilst
running Wireshark. Obviously, there is a problem with host name resolution.
If I run "nslookup downloads.maemo.nokia.com", the output looks like that:

Standard query AAAA downloads.maemo.nokia.com
Standard query response, No such name
Standard query AAAA downloads.maemo.nokia.com
Standard query response, No such name
Standard query A downloads.maemo.nokia.com
Standard query response CNAME downloads.maemo...
Standard query PTR 238.221...
Standard query response, No such name

wheras type "AAAA" means "IPv6 address" (Uh?!) and "A" means just "Host
address".

In contrast to this, the update manager produces output as follows (running
apt-get update as root):

[...]
Standard query AAAA downloads.maemo.nokia.com
Standard query response, No such name
Standard query response, No such name
Standard query AAAA moff.mozilla.com
Standard query AAAA downloads.maemo.nokia.com
Standard query response, No such name
Standard query response, No such name
Standard query A moff.mozilla.com
Standard query AAAA downloads.maemo.nokia.com
Standard query response, No such name
Standard query response A 63.245...
[...]

There is no try to get the "Host address" of downloads.maemo.nokia.com, however
there is for moff.mozilla.com. The list contains many more such request, most
of them with this strange "AAAA" type and a negative answer.

Any ideas what to do? It's a bit annoying...
Thanks in advance.

Do you have IPv6 enabled in your WiFi router?

(In reply to comment #26)
> Do you have IPv6 enabled in your WiFi router?
> 

Nope, since it does not support that. I wanted to try it with the ad-hoc
network (where I can see what really goes on), but I wasn't able to set it up
with IPv6 support.
I'm at school tomorrow and will try again with their network. I guess they have
IPv6 enabled. We will see...

Just tried it in the school network, works like a charm here. *confused*

I had the same problem. It was something to do with the DNS in the Netopia
router on my network. I tried a Linksys router and it worked ok.

Any news in this issue? I can't really believe that I should buy a new
Access-Point only because of a new mobile. I've tried a few other devices in
the WLAN and none of them had any trouble accessing the internet through this
AP. So it shouldn't be completely wrong...
The other thing is: What if it doesn't even work with another Access-Point?

(In reply to comment #30)
> Any news in this issue? I can't really believe that I should buy a new
> Access-Point only because of a new mobile.

No news, but did you try what I said in comment #19: work around the issue by
changing your DNS servers to another one such as Google's (8.8.8.8 and
8.8.4.4). But as I said there, you have to do it by editing /etc/resolv.conf;
it doesn't seem to work by setting DNS servers in the UI.

Also try updating your router's firmware to the latest. I did and eventually
Belkin fixed the issue so I don't have to use that workaround any more.

(In reply to comment #31)
> No news, but did you try what I said in comment #19: work around the issue by
> changing your DNS servers to another one such as Google's (8.8.8.8 and
> 8.8.4.4). But as I said there, you have to do it by editing /etc/resolv.conf;
> it doesn't seem to work by setting DNS servers in the UI.

Just tried it (with the google NS, as well as the one of my ISP), no
difference. APT still isn't able to resolve downloads.maemo.nokia.com.

> Also try updating your router's firmware to the latest. I did and eventually
> Belkin fixed the issue so I don't have to use that workaround any more.

I've this already with no success. The new firmware dates to Feb 2008, so it's
not that old...

I've also tried to add the IP of the server in question to my hosts file, not
even this works.

But what could cause this problem? It's really just APT with
downloads.maemo.nokia.com and Mail for exchange with our school server. Pinging
these servers for example works perfectly, so the device basically *can*
resolve the host name.

This issue is really annoying!

(In reply to comment #32)
> (In reply to comment #31)
> > No news, but did you try what I said in comment #19: work around the issue by
> > changing your DNS servers to another one such as Google's (8.8.8.8 and
> > 8.8.4.4). But as I said there, you have to do it by editing /etc/resolv.conf;
> > it doesn't seem to work by setting DNS servers in the UI.
> 
> Just tried it (with the google NS, as well as the one of my ISP), no
> difference. APT still isn't able to resolve downloads.maemo.nokia.com.

UPDATE: Previously, I've added the Google NS as a secondary DNS, which didn't
work. Now I've made it the only entry in my resolv.conf and it works somehow.
Somehow because I can access the official repos, but it sometimes is terribly
slow (2Bytes/s o.O) and Mail for exchange still won't synchronize. It spins for
about a minute and then runs into a timeout.

very slow to do anything in app manager howerver, faster app manager works fine