http://cdn.debian.net/debian/
For example (from grml_2009.10):
/etc/apt/sources.list.d/debian.list
deb http://cdn.debian.net/debian/ sid main contrib non-free
deb-src http://cdn.debian.net/debian/ sid main contrib non-free
This "cdn.debian.net" seems to be a kind of load balanced servers. Theoretically, it should be good. But, not for me. I don't really know why I always have problem with "cdn.debian.net". Maybe, my dns servers are not good? I tried with my local ISP's dns servers, Google Public DNS servers and OpenDNS. All of them have the same "not found" problem.
Anyway, I just always change it to:
ftp://ftp.debian.org/debian/
instead so my debian.list becomes:
deb ftp://ftp.debian.org/debian unstable main contrib non-free
deb-src ftp://ftp.debian.org/debian unstable main contrib non-free
and all the "not found" problems are gone!
![[FSF Associate Member]](http://static.fsf.org/nosvn/associate/fsf-12534.png)
Posts
3 comments:
"nslookup cdn.debian.net" gave me the URL deb.cdn.araki.net
(and seven IP addresses).
Yeah I sent the info to him. I am finding time to perform some checking and send him back the test result...
Here is the update. I sent a question to Araki Yasuhiro whom some nice guy in #grml (irc.freenode.net) suggested me. He is so nice and promptly he replied with a check list I had to perform and sent the result back to him.
In summary, I had the problem because I used Google Public DNS (8.8.8.8 and 8.8.4.4) which I will refer to it as GPD. When I used GPD to resolve ip address of cdn.debian.net, I somehow got ip address of a load balance server located in the US which then caused me trouble as I am in Thailand. It is also a misused of location based system.
To resolve the problem, I have to use any local DNS servers in Thailand and they will get a correct location based ip address of cdn.debian.net for me.
Post a Comment