Recent Comments
Archives
- May 2012 (8)
- April 2012 (11)
- March 2012 (10)
- February 2012 (11)
- January 2012 (5)
- December 2011 (13)
- November 2011 (12)
- October 2011 (10)
- September 2011 (7)
- August 2011 (5)
- July 2011 (11)
- June 2011 (21)
- May 2011 (22)
- April 2011 (36)
- March 2011 (43)
- February 2011 (23)
- January 2011 (24)
- December 2010 (34)
- November 2010 (19)
- October 2010 (16)
- September 2010 (15)
- August 2010 (10)
- July 2010 (12)
- June 2010 (3)
- May 2010 (3)
- April 2010 (4)
- March 2010 (8)
- February 2010 (14)
- January 2010 (13)
- December 2009 (16)
- November 2009 (28)
- October 2009 (24)
- September 2009 (12)
- August 2009 (7)
- July 2009 (10)
- June 2009 (11)
- May 2009 (22)
- April 2009 (21)
- March 2009 (18)
- February 2009 (7)
- January 2009 (32)
- December 2008 (19)
- November 2008 (12)
- October 2008 (15)
- September 2008 (14)
- August 2008 (15)
- July 2008 (18)
- June 2008 (20)
- May 2008 (19)
- April 2008 (27)
- March 2008 (22)
- February 2008 (21)
- January 2008 (15)
- December 2007 (22)
- November 2007 (17)
- October 2007 (29)
- September 2007 (31)
- August 2007 (34)
- July 2007 (31)
- June 2007 (36)
- May 2007 (23)
- April 2007 (22)
- March 2007 (30)
- February 2007 (50)
- January 2007 (75)
- December 2006 (48)
- November 2006 (59)
- October 2006 (89)
- September 2006 (29)
- August 2006 (48)
- July 2006 (14)
- June 2006 (35)
- May 2006 (62)
- April 2006 (63)
- March 2006 (72)
- February 2006 (83)
- January 2006 (56)
- December 2005 (46)
- November 2005 (60)
- October 2005 (27)
- September 2005 (54)
- August 2005 (83)
Tags
amazon android api aws bittorrent browser cdn certificate chrome cloud cloudfront cpan database dns ec2 facebook firefox freebsd google hosting html https ie image ipv6 javascript jquery js linux mobile mozilla mysql p2p performance perl php secure security ssl twitter ubuntu video web wordpress yahooCategories
- Anime (25)
- AWS (51)
- BBS (17)
- Blog (201)
- Book (18)
- Bridge (1)
- Browser (283)
- CDN (21)
- Cloud (66)
- CMS (33)
- Comic (17)
- Computer (1980)
- Computer and Network Center (32)
- CSS (31)
- Database (132)
- DNS (50)
- Editor (11)
- Financial (37)
- Firefox (149)
- Food (11)
- FreeBSD (115)
- Game (25)
- GoogleChrome (25)
- Hardware (144)
- IE (64)
- Joke (131)
- Lab (3)
- Linux (72)
- MacOS (4)
- Mail (69)
- Movie (18)
- Murmuring (2056)
- Music (37)
- MySQL (97)
- NCTU (63)
- NetBSD (7)
- Network (1486)
- OpenBSD (3)
- Opera (21)
- OS (205)
- P2P (86)
- Photo (57)
- Political (48)
- Programming (315)
- Recreation (372)
- RSS (65)
- Safari (22)
- Science (28)
- Search Engine (126)
- Security (336)
- SMS (5)
- Social (60)
- Software (1062)
- Spam (86)
- Sport (4)
- Telephone (62)
- Television (35)
- Usenet (13)
- Vim (3)
- Wiki (25)
- Windows (48)
- WWW (782)
Blogroll
Meta
Category Archives: DNS
分析 Y Combinator 的 Startup 所使用的服務…
在 HN (Hacker News) 上看到的分析資料 (文章是 ReadWriteWeb 的):「The Services Used By Y Combinator Startups [Infographic]」,文章裡面分析了 Y Combinator「旗下」的 startup 所使用的服務。 統計資料在「Y Combinator」這邊,另外有「Quantcast Top 100」的資料也可以看看,這邊就不提 Quantcast Top 100 的情況了。 網站主機的部份,可以看到是 Amazon Web Services 與 Rackspace Cloud 兩家雲端服務最大,如果把同屬於 Rackspace 下的 Slicehost 一起併進去算的話就幾乎相同了。不過自己 hosting … Continue reading
Route 53 的幾個網頁操作介面
目前 Route 53 還沒有 AWS Console 可以用,必須自己寫 API 呼叫,或是透過比較信任的 3rd-party website 更新。 比較早出現的是 DNS 30,背後其實就是 Bucket Explorer 與 SDB Explorer 的公司,介面簡單而且容易懂。由於宣稱不會將 secret key 存起來,所以每次登入後都要輸入 access key 與 secret key… 另外一個是 Ylastic,這家公司前幾天也宣佈支援 Route 53 了:「AWS Route 53 DNS Management」,他們所提供的 Screenshot 看起來也還蠻簡單易懂的: … Continue reading
Amazon Web Services 新服務:Route 53
當有多個 Data Center 的時候就應該要做的事情!Amazon 總算是出手了… Amazon 官方的新聞稿在這:「Amazon Route 53 – The AWS Domain Name Service」,CTO Werner Vogels 的介紹在這:「Expanding the Cloud with DNS – Introducing Amazon Route 53」,產品的介紹頁在這:「Amazon Route 53」。 Route 53 是利用 Amazon 目前已經有的 Data Center (依照 CloudFront 的名單,看起來是同一組機房),加上 IPv4 … Continue reading
Comcast 實驗 DNSSEC
Comcast 在官方的 blog 上宣佈,開始提供有 DNSSEC 驗證功能的 DNS resolver:「DNSSEC」,如果要測試的人可以手動改到 75.75.75.75 & 75.75.76.76。 非 Comcast 用戶沒有辦法參與,丟 query 過去會收到: ;; ->>HEADER<<- opcode: QUERY, status: REFUSED, id: 54496 ;; flags: qr rd ra; QUERY: 0, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
EveryDNS 被 Dyn Inc. 買下
正式的公告在 Dyn Inc. 的網站上:「Dyn Inc. Further Cements Position as Global Managed DNS Leader Through Acquisition of EveryDNS」。 在這個領域主要的競爭對手是 DynDNS。這次買 EveryDNS 算是擴展版圖,讓 Dyn Inc. 的的產品線更完整。
Google 提供 Public DNS Resolver
在 TC 看到 Google 公開了 Public DNS Resolver 服務:「Google Gets Into The DNS Business. Here’s What That Means」。 與 OpenDNS 不同,他不會把無法 resolve 的 request 導到廣告頁,另外又因為密度比 OpenDNS 高 (因為 Google 在很多地方有機房),IP address 又好寄 (分別是 8.8.8.8 與 8.8.4.4),就基本的 resolver 功能來說,OpenDNS 沒有優勢。 不過我發現如果是查詢 … Continue reading
Posted in Computer, DNS, Murmuring, Network 2 Comments
CDN – 技術面
要決定使用者應該要到哪組 server 通常有這些方法: GeoDNS Anycast HTTP Redirect (會比較差) 這幾種不衝突,常見的是前兩者搭配著用。將 DNS server IP anycast,當下載者要抓某個 domain 時,近的 server 就會知道大致的區域。再配合 GeoDNS 判斷使用者的 IP address 適合到哪個 node。 不過這些問題對 HiNet 就很麻煩。(留到現場講) 再來就是 reverse proxy cache 所產生的問題,這個部份再想看看要怎麼寫。
Posted in Computer, DNS, Murmuring, Network 3 Comments
CNAME to CNAME
不知道是從哪邊傳出 CNAME 不能設到 CNAME 的觀念,剛剛特地找資料,發現可能被「誤解」的地方。 在 RFC 1034 裡因為效率問題「建議」不要 CNAME to CNAME,但也強調這不應該視為錯誤:(5.2.2. Aliases) Multiple levels of aliases should be avoided due to their lack of efficiency, but should not be signalled as an error. 參考:「Cname of Cname」。
Posted in Computer, DNS, Murmuring, Network 2 Comments
Google 宣佈服務將會延伸到 IPv6
Google 宣佈服務將會延伸到 IPv6 network 上:「Access Google services over IPv6」。 目前 www.google.com 的 AAAA record 必須透過 IPv6 的 DNS query 才能拿到。一般人還是得透過 tunnel 或其他軟體才有機會使用。
Posted in Computer, DNS, Murmuring, Network Leave a comment
