[EMAIL PROTECTED] ~]$ dig security1.debian.org @samosa.debian.org.
; <<>> DiG 9.2.5 <<>> security1.debian.org @samosa.debian.org.
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 14151
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;security1.debian.org. IN A
;; AUTHORITY SECTION:
debian.org. 3600 IN SOA samosa.debian.org. hostmaster.debian.org. 2005082501 10800 3600 604800 3600
;; Query time: 74 msec
;; SERVER: 192.25.206.57#53(192.25.206.57)
;; WHEN: Wed Aug 24 23:32:04 2005
;; MSG SIZE rcvd: 92
On 8/26/05, Timo Veith <[EMAIL PROTECTED]> wrote:
Alvin Oga schrieb:
> either case can be solved by: security1.debian.org in LA
> and security2.debian.org in NYC and security3.debian.org in berlin :-)
This is interessting but:
Reading Package Lists... Done
Building Dependency Tree
Reading extended state information
Initializing package states... Done
Err http://security3.debian.org sarge/updates/main Packages
Could not resolve 'security3.debian.org'
Err http://security2.debian.org sarge/updates/main Packages
Could not resolve 'security2.debian.org'
Err http://security1.debian.org sarge/updates/main Packages
Could not resolve 'security1.debian.org'
Err http://security3.debian.org sarge/updates/main Release
Could not resolve 'security3.debian.org'
Err http://security1.debian.org sarge/updates/main Release
Could not resolve ' security1.debian.org'
Err http://security2.debian.org sarge/updates/main Release
Could not resolve 'security2.debian.org'
...
Regards,
Timo
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
