Thursday, November 27, 2014

Friday, November 7, 2014

Android Lollipop

Key Developer Features

歡迎光臨 Android 5.0 棒棒糖 — — 規模最大、最雄心勃勃的 Android 尚未釋放！

此版本被擠滿新的功能，為使用者和數以千計的新的 Api，開發人員了。它延伸 Android 更進一步，從手機、平板電腦和衣物，到電視和汽車。

仔細看看新的開發人員 Api，請參閱 Android 5.0 API 概述。或者，閱讀更多關於 Android 5.0 為消費者在 www.android.com。

To test your apps on a real device, flash a Nexus 5 or Nexus 7 with the
ANDROID PREVIEW SYSTEM IMAGE.

材料設計

Android 5.0 帶來材料設計對安卓系統，給出了你擴展的 UI 工具組將納入新的設計模式很容易在您的應用程式。

新的 3D 視圖允許您設置 z 級別，以提高從視圖層次結構和演員即時陰影，元素，即使當他們移動。

內置活動轉換採用使用者無縫地從一個狀態到另一個優美、動畫的動作。材料的主題添加轉換為您的活動，包括在活動中使用共用的可視元素的能力。

To replay the movie, click on the device screen

波紋動畫按鈕、核取方塊和其他觸摸控制在您的應用程式中可用。

此外可以在 XML 中定義向量畫板，並對它們在以各種方式進行動畫處理。向量畫板規模而不會丟失的定義，所以它們非常適合單一顏色的應用程式圖示。

稱為 RenderThread 一個新的系統管理的處理執行緒保持動畫平滑，即使在主 UI 執行緒有延誤。

性能焦點

Android 5.0 提供了更快、更順暢、更強大的計算體驗。

Android 現在完全在建成從地面到支援混合的超前 (AOT) 中，即時 (JIT) 的新藝術運行時上運行和解釋的代碼。它在胳膊上，x 86 和 MIPS 體系結構支援，並且是完全 64 位相容。

藝術可以提高應用程式性能和回應能力。有效的垃圾收集可以減少和 GC 事件，適合在 v 同步視窗內所以您的應用程式暫停的持續時間不會跳過幀。藝術還可以動態地移動記憶體來優化性能，用途前景。

Android 5.0 引入了平臺支援 64 位體系結構 — — 由 Nexus 9 NVIDIA Tegra K1 使用。優化提供更大的位址空間和改進的性能對於某些計算的工作負載。用 JAVA 語言編寫的應用程式自動運行作為 64 位應用程式 — — 需要不作任何修改。如果您的應用程式使用本機代碼，我們把延長 NDK 去支援新 ABIs 為手臂 v8 和 x86-64 和 MIPS-64。

對光滑性能繼續集中力量，Android 5.0 提供了改進的 A / V 同步。音訊和圖形管道已檢測更準確的時間戳記，使視頻應用程式和遊戲顯示平滑的同步的內容。

通知

通知在 Android 5.0 中的是可見的、可行的並且可配置。

可變通知的詳細資訊可能出現在鎖屏上如果使用者所需。使用者可以選擇允許任何全部或部分，通知內容，安全鎖定螢幕上顯示。

關鍵通知警報如本機號碼在單挑的通知中 — — 一個小的浮動視窗，允許使用者作出回應或解雇無需離開當前的應用程式。

現在可以將新的中繼資料添加到通知來收集相關聯的連絡人（的排名）、分類和優先順序。

新的媒體通知範本提供一致的媒體控制達 6 動作按鈕，如包括自訂控制項"大拇指"通知 — — 不再需要 RemoteViews ！

你在大螢幕上的應用程式

Android 電視為您的應用程式大螢幕經驗提供了一個完整的電視平臺。Android 電視被圍繞一種簡化的主畫面體驗，允許使用者發現內容很容易，有個人化的推薦和語音搜索。

您現在可以創建大的 Android 電視，大膽的為您的應用程式或遊戲內容和支援與交互遊戲控制器和其他輸入的設備的經驗。為了説明您構建電視電影，10 英尺的 Ui，Android 提供了在 v17 支援函式庫的 leanback UI 框架。

Android 電視輸入框架 (TIF) 允許電視應用程式來處理來自 hdmi、電視調諧器和 IPTV 接收機等來源的視頻流。它還啟用直播電視搜索和建議通過發表電視輸入介面的中繼資料，並包括一個 HDMI CEC 控制服務，以處理多個設備與一個單一的遙控器。

電視輸入框架提供對種類繁多的即時電視輸入源的訪問，並將它們集中在單一的使用者介面為使用者流覽、查看和享受的內容。構建電視輸入的服務為您的內容，可以説明使你的內容更容易在電視的設備上。

以以文件為主的應用程式

Android 5.0 引入了一個重新設計的概述空間（以前稱為歷史），是更通用和有用的多工處理。

新的 Api 允許您在您的應用程式中顯示單獨的活動，作為單個文檔）和其他最近的螢幕。

你可以利用並行檔，提供給更多的內容或服務的使用者即時訪問。例如，您可能使用併發檔來表示在一個生產力應用程式，在遊戲中，玩家比賽或聊天消息的應用程式中的檔。

高級連接能力

Android 5.0 中添加新的 Api 允許應用程式來執行平行作業與藍牙低能量 (BLE)，允許掃描（中央模式）和廣告（週邊模式）。

新的多網路功能允許應用程式查詢可用的網路的可用功能，如他們是否 Wi-fi、蜂窩，計量，或提供某些網路功能。然後應用程式可以請求連接並對網路連接的丟失或其他網路的變化作出反應。

NFC Api 現在允許應用程式動態地註冊 NFC 應用程式 ID （AID）。他們還可以設置每個主動服務首選的卡模擬服務並創建包含 utf-8 文本資料的 NDEF 記錄。

高性能顯卡

支援時下 OpenGL ES 3.1 現在提供遊戲和其他應用程式的高性能 2D 和 3D 圖形功能在受支援的設備上。

OpenGL ES 3.1 添加計算著色器、模具紋理、加速視覺效果、高品質 ETC2/EAC 紋理壓縮、先進的紋理繪製、標準化的紋理大小和渲染緩衝的格式，和更多。

智樂的對手騎士使用 ASTC （自我調整可縮放紋理壓縮）從 AEP 和計算著色器從 ES 3.1 提供 HDR (高動態範圍) 綻放效果以及更多的圖形細節。

Android 5.0 還介紹了 Android 擴展包（AEP），一組功能，如鑲嵌著色器、幾何著色器，ASTC 紋理壓縮，每樣條插值和網底，給您訪問的 OpenGL ES 擴展和其他高級呈現功能。AEP 與你能提供高性能顯卡 Gpu 範圍跨越。

更強大的音訊

新的音訊捕捉設計提供低延遲音訊輸入。新的設計包括：永遠不會阻止除讀取；過程中的快速捕獲執行緒快速跟蹤捕獲用戶端在本機取樣速率、通道數以及位深度；和正常捕獲用戶端提供重採樣，上下通道混合和上下位深度。

多通道音訊流混合允許專業音訊的應用程式，混合達八個電視頻道，包括 5.1 和 7.1 的管道。

應用程式可以公開他們的媒體內容和流覽媒體從其他應用程式，然後要求播放。內容通過查詢介面公開和不需要駐留在該設備上。

應用程式可以通過語音設定檔與特定的語言環境，品質和延遲評級相關聯的文本到語音合成更細細微性控制。新的 Api 也提高合成錯誤檢查、網路綜合、語言發現和網路後備支援。

安卓系統現在包括標準 USB 音訊周邊設備，允許使用者連接 USB 耳機、揚聲器、麥克風或其他高性能數位週邊設備的支援。Android 5.0 還添加了電視劇的音訊編解碼器支援。

新 MediaSession Api，可用於控制媒體播放現在使它容易跨螢幕和其他控制器提供一致的媒體控制。

增強的觀景窗和視頻

Android 5.0 引入了所有新的觀景窗 Api 允許您捕獲原始格式（如 YUV 和拜耳原料和控制參數如曝光時間、 ISO 感光度和幀持續時間在每個幀的基礎上。新的完全同步相機管道允許您捕獲壓縮高解析度 YUV 圖像在每秒 30 幀在支援的設備上。

隨著圖像，您也可以捕獲像雜訊模型和從相機的光學資訊的中繼資料。

在網路上發送視頻流的應用程式現在可以利用的 H.265 高效率視頻編碼（HEVC）用於優化的編碼和解碼的視頻資料。

Android 5.0 中還添加了支援多媒體的隧道，以提供最好的體驗為超高清晰度 (4k) 內容和發揮能力壓縮音訊和視頻資料在一起。

Users have a unified view of their personal and work apps, which are badged for easy identification.

Android 在工作場所

若要啟用帶-你-自己的設備為企業環境中，一個新的託管資源調配過程設備上創建了一個安全的工作設定檔。發射器，顯示應用程式與工作徽章以指示該應用程式及其資料都內部的工作設定檔由 IT 管理員管理。

兩個通知的個人和工作的設定檔是在統一的視圖中可見。每個設定檔的資料總是保持獨立和從彼此，包括相同的應用程式使用兩個設定檔時的安全。

公司擁有設備，IT 管理員可以開始一個新的設備，並將其配置與設備擁有者。雇主可以發出這些設備已安裝的設備擁有者應用程式，可以配置全球設備設置。

螢幕捕獲和共用

Android 5.0 允許您添加螢幕捕獲和共用到您的應用程式功能的螢幕。

與使用者的許可權，您可以捕獲非安全視頻從顯示並傳送網路，如果您選擇。

新類型的感應器

在 Android 5.0 中，一種新型的傾斜儀感應器有助於提高活動識別在支援的設備，和心率感應器報告心率接觸設備的人。

新的相互作用的複合感應器現可用於探測如醒來的手勢、姿態，撿和眼手勢的特殊相互作用。

Chromium Web 視圖

最初的版本，對於 Android 5.0 包括Chromium版為 web 視圖基於Chromium M37 版本中，添加對 WebRTC、 WebAudio 和 WebGL 的支援。

Chromium M37 還包括對所有 Web 元件的規範的本機支援：自訂元素、影子 DOM、 HTML 進口和範本。這意味著你可以使用聚合物及其材料設計項目在 web 視圖中而無需 polyfills。

儘管 web 視圖以自 Android 4.4 基礎Chromium，Chromium層現在是從谷歌播放可更新的。

以Chromium變得可用的新版本，使用者可以更新從谷歌播放，以確保他們獲得最新的增強功能和 web 視圖，提供最新的 web Api 的 bug 修復和應用程式使用 web 視圖上 Android 5.0 和更高的 bug 修復。

協助工具和輸入

新的協助工具 Api 可以檢索有關的詳細資訊的屬性視窗看見螢幕上的使用者可以與交互並定義標準或自訂 UI 元素的輸入的操作。

新的輸入法編輯器 (IME) 的 Api 使更快地切換到其他輸入法直接從輸入法。

用於構建電池高效的應用程式的工具

新工作調度 Api 允許您通過延遲使系統運行在稍後的時間或根據指定的條件，如該設備時充電或連接到無線網路的工作優化電池壽命。

新的 dumpsys batterystats 命令將生成可用於瞭解全系統電源使用和理解的影響您的應用程式在設備電池的電池使用方式統計資訊。你可以看看歷史電源事件，近似每 UID 和系統元件，和更多的用電。

電池的歷史學家是一種新的工具，統計資料從 dumpsys batterystats 轉換為電池相關調試視覺化。 You can find it at https://github.com/google/battery-historian.

Thursday, August 21, 2014

「孤独のグルメSeason4」特別編!真夏の博多出張スペシャル

Saturday, August 9, 2014

US Carries Out More Airstrikes Against ISIS in Iraq

ABC News | More ABC News Videos

Thursday, July 31, 2014

Four Taiwan youths nabbed with $130M in ice in Melbourne

The Australian Federal Police (AFP) arrested four Taiwan youths and seized four suitcases of methamphetamine, commonly called ice, in an inner-city apartment in the city Tuesday night. The AFP and Australian Crime Commission (ACC) were acting on a search warrant following a tip forwarded by an ad hoc task force to combat drugs in Australia. The AFP seized 135 kilograms of methamphetamine with a street value of A$130 million (NT$3.69B), said to represent 1.3 million street deals of the drug. The four men, Chun Lan, 28, Ming Hsuan Ou and Li Ping Chen, both 23, and Shu Yi Lin, 20, appeared briefly in the Melbourne Magistrates Court Wednesday. They were all charged with possessing and trafficking a commercial quantity of a border-controlled drug. The charges carry a maximum penalty of life in prison. The four men told the court through a translator they all have Australian tourist visas and their arrest Tuesday was their first time in custody. They are scheduled to appear in court on November 5.

Thursday, July 24, 2014

간장게장,양념게장,낙지볶음

Friday, July 18, 2014

1597년 임진왜란 6년

電影名稱:鳴梁-漩渦之海
韓國上映日期:2014年7月30日
簡介:是一部講述了1597年壬辰倭亂6年，朝鮮名將李舜臣在鳴梁海峽以12艘板屋船擊退330餘艘日艦，創下世界海戰史上的一個奇跡的「鳴梁大捷」的戰爭動作大片。
主演:崔岷植、柳承龍、李貞賢、魯敏宇

Sunday, July 13, 2014

指定席券売機の使い方―自由席購入編

Saturday, July 12, 2014

오리지널 타코야키

Saturday, July 5, 2014

アンガールズ田中、号泣会見　野々村竜太郎　ものまね

Sunday, June 1, 2014

[ENG SUB] 무한도전 가요제 - 머리부터 발끝까지 정형돈이 꼼꼼히 스타일링한 지드래곤의 '삐딱하게' M/V 20131012

Wednesday, May 21, 2014

Title:Swipe Tap Love, Artist:Jinny Ng (Hong Kong's Female Pop Singer) | (Yue Dialect/Guangdong Dialect)

Monday, May 19, 2014

★列車に乗って|2014年5月18日　門司港・下関の旅(1)

Tuesday, May 13, 2014

機動戦士ガンダムUC×特急ラピート赤い彗星の再来特急ラピートネオ・ジオンバージョン

Friday, May 9, 2014

Taiwan Self-guided Tour within One Week

【台湾一周1人旅】 part 1 【環台】
http://smile-cln63.nicovideo.jp/smile?m=23464763.7541

Wednesday, May 7, 2014

東京の激安寿司屋

Saturday, May 3, 2014

【愛知】五色園第8次修復活動

Thursday, May 1, 2014

A Concert Of Music By Super Girls(Hong Kong's Female Pop Group) | (Yue Dialect/Guangdong Dialect) <Traditional Chinese Subtitle>

Sunday, April 27, 2014

Ukraine: Local self-defense units surround Ukrainian military base

Sunday, March 30, 2014

클로즈업 홍콩

Friday, March 28, 2014

아3인 JSA

웹접근성을 고려한 tv팟 플레이어입니다. 아3인 JSA / 코미디빅리그2 15ROUND 동영상을 재생하시려면 클릭해 주세요.

북한 '땅굴위협' 아직 끝나지 않았다

Friday, March 21, 2014

Video Diary of a Panda Kid

Thursday, March 20, 2014

鉄砲の伝来～キリスト教と西洋技術～ 1/2

Monday, March 17, 2014

香取神道流剣術

Sunday, March 16, 2014

伊勢長島願證寺，一向一揆殉教の碑

物流拠点としての経済的成長を背景に台頭してきたのが、長島願證寺の勢力。明応10年(1501)、浄土真宗(一向宗)の中興の祖・蓮如の子蓮淳が長島願證寺に入ったことにより、浄土真宗の教勢は拡大。その勢力は長島・桑名を中心に。現在の尾張西部・美濃南部・北勢地方に広がっていった。交通の要衝であり、低湿地で要害の地である長島は一向宗拡大を図るための重要な拠点。天文6年(1537)に、願證寺は長島を支配していた伊藤一族を追放し、長島は願證寺の領地となった。益々強大化する一向宗の勢力を危惧したのは、尾張地方を中心に着々と勢力拡大を図っていた織田信長であった。天下をめざす信長は京へ上る前年の永禄10年(1567)北勢に侵入した北勢48家といわれた豪族達を破り、続いて永禄12年には南勢の北畠氏も滅ぼした。こうして信長は伊勢全土を制圧するが、なおも信長に反抗していたのが願證寺を中心とする長島の一向門徒達。10万人を超える勢力であった。この一向門徒達と信長の間で起った戦いが『長島一向一揆』と呼ばれる日本の歴史上で最も有名な宗教戦争であり、激しく悲惨な戦いであった。元亀2年(1571)を皮切りに戦いは3回に渡って行われ、最期まで砦に残っていた男女2万人余りは、周囲に柵を設けて閉じ込められ、四方から火を放たれて焼き殺された。その死者は現在の長島町の人口の2倍以上。こうして長島一向宗は壊滅した。

Friday, March 14, 2014

196 日本語新常用漢字リスト

Wednesday, March 12, 2014

Malay Sorcerer at Kuala Lumpur Airport Performs Rituals with Coconut and Magic Stick to Find Jet Plane(MH370)

Sunday, March 9, 2014

Passengers on stolen passports in missing Malaysian plane had ‘Asian faces’

March 10, 2014 4:02PM ( UTC+11 )
TWO passengers who used stolen passports to board a Malaysia Airlines plane that went missing with 239 people aboard had “Asian facial features”, Malaysia’s interior minister says.
Malaysia Airlines flight MH370 from Kuala Lumpur to Beijing vanished over waters somewhere between Malaysia and Vietnam early on Saturday about an hour after taking off.
No trace has been found of the plane, despite earlier reports of debris being spotted.
Six Australians were aboard the aircraft.
Fears of a terror attack have surfaced after it was revealed that at least two passengers boarded the plane with stolen passports -- one from Italy and one from Austria. The passport owners have been found to be safe.
“I am still puzzled how come (immigration officers) cannot think: an Italian and Austrian but with Asian facial features,” Home Minister Zahid Hamidi was quoted as saying by Malaysia’s national news agency Bernama.
The report did not elaborate. Malaysian officials had earlier said they were examining CCTV images of the passengers.
“We will conduct an internal probe, particularly on the officers who were on duty at the KLIA (Kuala Lumpur International Airport) immigration counter during flight MH370,” Mr Zahid said.
Vietnamese searchers late yesterday spotted debris off their coast but it has not been confirmed whether that was from the missing Boeing 777.
Malaysia’s transport minister said the government was looking into the possibility of a terror incident and was liaising with intelligence agencies of other countries including the US Federal Bureau of Investigation.
Interpol confirmed it knew about the stolen passports but said no authorities checked its vast databases on stolen documents before the Boeing jetliner departed Saturday from Kuala Lumpur en route to Beijing.
INVESTIGATION: Terrorism fears as plane vanishes
There were six Australians on the flight and
Aboard the flight wdere two Brisbane couples, Rodney and Mary Burrows and Robert and Catherine Lawton, who were travelling to holiday in China. Also on board were a Sydney couple, Li Yuan and Gu Naijun, and Paul Weeks, a New Zealand citizen living in Perth who was about to start a fly-in fly-out mining job in Mongolia.
Prime Minister Tony Abbott yesterday said Malaysia had accepted the offer of two RAAF P-3C Orion maritime surveillance aircraft to help in the search for the missing flight.
“This is obviously a horrible, horrible business,” the Prime Minister said. “Our thoughts and prayers are with the passengers and their families on that ill-fated aircraft, particularly to the six Australian passengers and their families that have now been confirmed to be on board.”
GALLERY: Mystery of the vanished plane
More than two days after Malaysia Airlines Flight MH370 went missing, the final minutes before its disappearance remained a mystery. The plane lost contact with ground controllers somewhere between Malaysia and Vietnam.
However, searchers in a low-flying plane spotted an object that appeared to be one of the plane’s doors, the state-run Thanh Nien newspaper said, citing the deputy chief of staff of Vietnam’s army, Lt. Gen. Vo Van Tuan.
Two ships from the maritime police were headed to the site about 60 miles (90 kilometers) south of Tho Chu island in the Gulf of Thailand, the same area where oil slicks were spotted Saturday.
“From this object, hopefully (we) will find the missing plane,” Tuan said.
The jetliner apparently fell from the sky at cruising altitude in fine weather, and the pilots were either unable or had no time to send a distress signal — unusual circumstances under which a modern jetliner operated by a professional airline would crash.
PLANE: Past autopilot problems raised
Authorities were checking on the identities of the two passengers who boarded the plane with stolen passports. On Saturday, the foreign ministries in Italy and Austria said the names of two citizens listed on the flight’s manifest matched the names on two passports reported stolen in Thailand.
“I can confirm that we have the visuals of these two people on CCTV,” Malaysian Transport Minister Hishammuddin Hussein said at a news conference late Sunday, adding that the footage was being examined. “We have intelligence agencies, both local and international, on board.”
The thefts of the two passports — one belonging to Austrian Christian Kozel and the other to Luigi Maraldi of Italy — were entered into Interpol’s database after they were stolen in Thailand in 2012 and last year, the police body said.
Electronic booking records show that one-way tickets with those names were issued Thursday from a travel agency in the beach resort of Pattaya in eastern Thailand. A person who answered the phone at the agency said she could not comment.
But no authorities in Malaysia or elsewhere checked the passports against the database of 40 million stolen or lost travel documents before the Malaysian Airlines plane took off.
In a forceful statement, the Interpol chief said he hoped “that governments and airlines worldwide will learn from the tragedy.”
“Now, we have a real case where the world is speculating whether the stolen passport holders were terrorists,” Noble said. “Interpol is asking why only a handful of countries worldwide are taking care to make sure that persons possessing stolen passports are not boarding international flights.”
PASSPORTS: Disaster exposes security loophole
Details also emerged Sunday about the itineraries of the two passengers traveling on the stolen passports.
A telephone operator on a China-based KLM hotline confirmed Sunday that passengers named Maraldi and Kozel had been booked on one-way tickets on the same KLM flight, flying from Beijing to Amsterdam on Saturday. Maraldi was to fly on to Copenhagen, Denmark, and Kozel to Frankfurt, Germany.
She said the pair booked the tickets through China Southern Airlines, but she had no information on where they bought them.
As holders of EU passports with onward flights to Europe, the passengers would not have needed visas for China.
Interpol said it and national investigators were working to determine the true identities of those who used the stolen passports to board the flight. White House Deputy National Security Adviser Tony Blinken said the U.S. was looking into the stolen passports, but that investigators had reached no conclusions.
Interpol has long sounded the alarm that growing international travel has underpinned a new market for identity theft: Bogus passports are mostly used by illegal immigrants, but also pretty much anyone looking to travel unnoticed such as drug runners or terrorists. More than 1 billion times last year, travelers boarded planes without their passports being checked against Interpol’s database of 40 million stolen or lost travel documents, the police agency said.
Possible causes of the crash included some sort of explosion, a catastrophic failure of the plane’s engines, extreme turbulence, or pilot error or even suicide. Establishing what happened with any certainty will need data from flight recorders and a detailed examination of any debris, something that will take months if not years.
Malaysia’s air force chief, Rodzali Daud, said radar indicated that before it disappeared, the plane may have turned back, but there were no further details on which direction it went or how far it veered off course.
“We are trying to make sense of this,” Daud said at a news conference. “The military radar indicated that the aircraft may have made a turn back, and in some parts this was corroborated by civilian radar.”
Malaysia Airlines Chief Executive Ahmad Jauhari Yahya said pilots are supposed to inform the airline and traffic control authorities if the plane does a U-turn. “From what we have, there was no such distress signal or distress call per se, so we are equally puzzled,” he said.
A total of 34 aircraft and 40 ships from Vietnam, Malaysia, Thailand, Australia, Singapore, Indonesia, China and the United States were deployed to the area where ground controllers lost contact with the plane on the maritime border between Malaysia and Vietnam.
Of the 227 passengers and 12 crew members on board, two-thirds were Chinese, while the rest were from elsewhere in Asia, Europe and North America, including three Americans.
Family members of Philip Wood, a 50-year-old IBM executive who was on board the plane, said they saw him a week ago when he visited them in Texas after relocating to Kuala Lumpur from Beijing, where he had worked for two years.
“There is a shock, a very surreal moment in your life,” said Wood’s brother, James Wood.
The other two Americans were identified on the passenger manifest as 4-year-old Nicole Meng and 2-year-old Yan Zhang. It was not known with whom they were traveling.
After more than 30 hours without contact with the aircraft, Malaysia Airlines told family members they should “prepare themselves for the worst,” Hugh Dunleavy, the commercial director for the airline, told reporters.
Finding traces of an aircraft that disappears over sea can take days or longer, even with a sustained search effort. Depending on the circumstances of the crash, wreckage can be scattered over a large area. If the plane enters the water before breaking up, there can be relatively little debris.
A team of American experts was en route to Asia to be ready to assist in the investigation into the crash. The team includes accident investigators from the National Transportation Safety Board, as well as technical experts from the Federal Aviation Administration and Boeing, the safety board said in a statement.
Malaysia Airlines has a good safety record, as does the 777, which had not had a fatal crash in its 19-year history until an Asiana Airlines plane crashed last July in San Francisco, killing three passengers, all Chinese teenagers.
AP/AFP

Share EX2 初期ノード情報

XU4we36JH3aixC5BzDn9LWvZpFlMTpuWlxQHSQi9ENzx9unwu2Fx
Kn6k6JIAYQQY1qPqmxYDLDgBtPslfvbsa5BNRFrtZWCbUoQMBQ
ssVo20C+KbGkIbLUf39HiYnJ43m9xeVGIiinaKdD8t9F2MDQGg
LL9c6BS0NfnRl3WPfP8Y4UecHSE8v2+3crm4HoHUJOuXoS0gmSE
PpSCT5RX19sBl0YYgabGKLmQPYs3lD2qT8d6vZiM2A
8PaPEqzIyUMDEBK6k1R6Q4iVPzzg9geoHXw5c0/rpqev+7sRQlo
5oRBYI7PwMThcyGtQ+fsQZ3q0IXphNMt0OnqLrRT5VIwuOUCiw
OjOVPoTVBFMIiUOSHPfLWArqr601M393ty6P+NwhSEyasdnRlg
piaZ3GGv7zSdzERNKrKf+qZfF8moJu4F8mN32gsXffS8INWq
tXxFaH3WcmMq34R24PMeqm6bHlq6fFsFaFZKBeEMhavORKBmZg
gUi/t0rqL0MBnkzlnG6VkesiJN2OSP2zOszKKpmmB5N6vgg7kw
7nOCwt3Oar0zLleD6pm0fmqnkoPhc/aMUMCJZCjoeVFVXGCiSg
AU7k2zhUWL4rdmfx/hjnaKw0SLgOTsT0oAq/6fjEDbyi94Sqyw
NLGdGzz4SfmxmProDS6B2JowBU4ksfXVmJSaYiC60SfLwIZRsHg
4Y/fIqqg6769yDJByd74FGYZ7wrwjz2qTlRnJusdtJFBe3502Cqz
QTTS8s7jlX29Is3vZOBmIQvBLMFRNJe/p/eAusGYjOAJIFGdUNQ
1cfsOC2XYYJRlj/J1FDkL+l6LbXFxxg5kSlTTAuvpIYD/7gqN4o
Y5yjOe8+T2YPnY90LVUtMQ1TGPBynIi8amz0LnzZW7nYOoSA2p9V
oioI+sOea257J2yMbbOrDGtsBfSsKpuWkxExJSmUFIJIoqAm
kt/ZlCmDsf93t24DO0Ro9xgTBDuC377BKBycd8uqGQEMUNm/mxs
ZBYK/ljaRssvYVUdqQfcEbKhWlhqFkW9SFH/3cKCNw7R5GUa
I+CoCfFQLLsuXRc0ZtOvnIYZFKAz4IZkibc9Pavyd4WZoCfPd/o
B8zOTKoWf5OSPdpW7qrayj3fpEwXzIm9urn+gnni+Oh6qdWWBxc
LL9c6BS0NfnRl3WPfP8Y4UecHSE8v2+3crm4HoHUJOuXoS0gmSE
yNaK1oJ0wsCzl/izWKH0zfgSErXZ1iYZXn5Q9YyT0aaH8rr0p+jm
LFBKXMsIsF5PG+dQKx5hFhLW0TMjUCIC5MlupzpPRp9XvVXsug
peB3Aj4/wI4wLj0AyoPFbiYUE6G14LgKHhuun/nNgR7BL8OLNaM
gSIzlcA3m/dKZdfiZhaIbuOlbmuOIuP9D0Mavc902bPxZQiocA
XahalMB5vnz3qtkaewj+uO5rb0tNqEUwqrwiQwJXAHFsYsxtOlg
yc1btXdy4SdvFW//P7oe50oGVgHYzTNZ5nEu6J9z41ZPmtiQq5Pr
Wh+ZdlRQy2C9rM/KgM7VHS49kg1UH8lmaAFWMSZWE6CW9JQg
HhXexQ/iCxFKsdDHQfIZtR67HAYOFQj/9hkVkUfpfo9ujcVmjJ8
jaMOcs3FPKiardwEiCjWWeVpArmdo4i8am+/VCJJputyCL/PP7I
pCsm6vlsOkOBFrFwYdBDjkvn6P+0K/82p3VDTMPY8qU2xSkEz/E
VVnaIx8bly7mY+FloSJsa8LzOepaWQRCTlUCvgqKDgFXm5olzg
QTTS8s7jlX29Is3vZOBmIQvBLMFRNJe/p/eAusGYjOAJIFGdUNQ
STgMvS9dDBq0b5Im84qLng2O0JxZOMbTtTMwjl0NY/zaefoqJr8
91lVpnEVu6RryFeE+XBxN/AslYzmWZ3vTFwQrDVXO2RmvhlKUAMO
4HDakrTyv1KPckVMJI8KXv4WeIbwcJuWlxQHSQi9ENzx9uwADSw
LFBKXMsIsF5PG+dQKx5hFhLW0TMjUCIC5MlupzpPRp9XvVXsug
gP5DQwK5tbRJYTn6eRGar+KCMxmR/nDBGsVAkicOpcFxDyQUqzq1
mapYTgopMbR1s6v8oMK+Tzvn+++Wqj3ooS18L7A7pFs6r3ev8g
UGsbM+2XctVqjm9W3lOPR4F9OpBAa6IZRXiki82ezk/mjGlkMZA
agekuClVb/RcpQDz/9kjHrK6lvR7Bwj/9hkVkUfpfo9m4gSOcvEw
AnZYUi5hVsyGmVL5eQrrn08R4hMMdsYTHfWfvKb3l92td/ZB
KQGTU2kWAX5oCrfUTgkmjJNWSH84ARh0gEb1rn+ydyEGaaM89/0W
Q8oug4qDYo1YTe6rRKZc5l9UKuhOyvpAKFCJkWKC2sMSDuo
nh1aAl3RMK12dh1NKva+2gmZx2uRHfXVmxW7HcYMFqTOpSiRkA
yc1btXdy4SdvFW//P7oe50oGVgHYzTNZ5nEu6J9z41ZPmtiQq5Pr
QTTS8s7jlX29Is3vZOBmIQvBLMFRNJe/p/eAusGYjOAJIFGdUNQ
PpSCT5RX19sBl0YYgabGKLmQPYs3lD2qT8d6vZiM2A
XA6yY40yVv4GT/N7I6clW24wWqtNDp3vTFwQrDVXO2RmuZDFeGdw
piaZ3GGv7zSdzERNKrKf+qZfF8moJu4F8mN32gsXffS8INWq
nys4VTR1B3/u1qiljJgWWInV65COK0UwqrwiQwJXAHFsYs6VZhYu
V1C4Dhidut/2D9StDClIrM/qWJxGUJmwFwK9BZt6lvB5dZOkjCfh
JiCsDt33LIuV++yEqxudKl67KKI3IInAocxaw1cbnBov3pY1x3/K
ZcHHL6Z0NteG9QCzMH0/zbCvulVqwQj/9h0Og2xmCyOCVUbtRw
opdF4gg0MWZIy9jLXboC+jlAhYCtl5e/pK1wKSd+0Q++MFTUFg
jHrcT3yZ6x2dCK4XhJGBZT4XbGuceuieZ5MbipSXmyuUAtOdf0c
AnZYUi5hVsyGmVL5eQrrn08R4hMMdsYTHfWfvKb3l92td/ZB
STgMvS9dDBq0b5Im84qLng2O0JxZOMbTtTMwjl0NY/zaefoqJr8
/NtYkvnfffSZUu73yyRAXwvZ1mLs2/cLuiazwOjBsvjWXlHdw0M
Wh+ZdlRQy2C9rM/KgM7VHS49kg1UH8lmaAFWMSZWE6CW9JQg
4k6YXv/D8PU244w6XYzo2xz440nzTu8/b9oMzTHX1QgzRTwD4xVF
ICJBa185NxI76Fe05vvJ2LFkRR8vIv5w/zg5Fej2dmNPITuDMQ
QTTS8s7jlX29Is3vZOBmIQvBLMFRNJe/p/eAusGYjOAJIFGdUNQ
bOFIC+OFLFlFvRHdA2cBXaa4uk994ezI6LORehoCJtRjY4+fL1nN
opdF4gg0MWZIy9jLXboC+jlAhYCtl5e/pK1wKSd+0Q++MFTUFg
/NtYkvnfffSZUu73yyRAXwvZ1mLs2/cLuiazwOjBsvjWXlHdw0M
r86/Qw0gO1nWyZjgcFstNoTQtauhziUwKvimfRaUvdl+LVtw
djCEkTx7bBU9HUYV+rLqAIQJcmh5MMT0oAq/6fjEDboRyQ3bNw
AnZYUi5hVsyGmVL5eQrrn08R4hMMdsYTHfWfvKb3l92td/ZB
STgMvS9dDBq0b5Im84qLng2O0JxZOMbTtTMwjl0NY/zaefoqJr8
67DQEDeElBP55XMIg0ocvty8vDP7sC9mHr8fWc7S0i5UVZLHKNw
qvvnKFvKHFjJVOfJt98FnbWQ79O7+5e/p/6dvP1+U5hMOI86AUES
BRs4S5BNR4Fynj0qgLEAY6V0l8IVGzfJJRuqxRVTUoqlA12DLoc
yc1btXdy4SdvFW//P7oe50oGVgHYzTNZ5nEu6J9z41ZPmtiQq5Pr
GalRT3tjxKPtZ7M4ITC7r7o0krYJqZ3vTFwcK5eIXB42/KJybyI
gSIzlcA3m/dKZdfiZhaIbuOlbmuOIuP9D0Mavc902bPxZQiocA
Pem+cHj2pv76ffgy/XfsCgQj8p4t6Ze/p/eDPVwGAx17Nx1qGAA
AnZYUi5hVsyGmVL5eQrrn08R4hMMdsYTHfWfvKb3l92td/ZB
STgMvS9dDBq0b5Im84qLng2O0JxZOMbTtTMwjl0NY/zaefoqJr8
piaZ3GGv7zSdzERNKrKf+qZfF8moJu4F8mN32gsXffS8INWq
jaMOcs3FPKiardwEiCjWWeVpArmdo4i8am+/VCJJputyCL/PP7I
Rz2QxaeDhKYlwyNZG8Y6GK/sEiBWPSYZXn5Q9YyT0aaEMXmwlHpW
L6TvSx8LcUgRHdPGxMjX3+6SA84gpMgU57UW736oY0O9hb2Etg
5oRBYI7PwMThcyGtQ+fsQZ3q0IXphNMt0OnqLrRT5VIwuOUCiw
qvvnKFvKHFjJVOfJt98FnbWQ79O7+5e/p/6dvP1+U5hMOI86AUES
Zmy+7T/msAeZ86lMOmiw524vAtRvbBIoMtacX04/Lg
7nOCwt3Oar0zLleD6pm0fmqnkoPhc/aMUMCJZCjoeVFVXGCiSg
rgO3vCpgx0wAPT01etbQfwDJHoihAxwrzLNPA5yCrvjhWw7pSg
AnZYUi5hVsyGmVL5eQrrn08R4hMMdsYTHfWfvKb3l92td/ZB
k4YOSaU4iQTbD7UlDOMUlyo7wqSchlsFaFZKBeEMhavN//nFlQ
qsZhAUOtgPii/WgDqSL2XeKiRiW6xsT0pNksfzkXNnQ1p5K/R2A
STgMvS9dDBq0b5Im84qLng2O0JxZOMbTtTMwjl0NY/zaefoqJr8
yc1btXdy4SdvFW//P7oe50oGVgHYzTNZ5nEu6J9z41ZPmtiQq5Pr
qvvnKFvKHFjJVOfJt98FnbWQ79O7+5e/p/6dvP1+U5hMOI86AUES
v1tZV/Hp7OBa9OZP30avwSHIgpyuW1egZybezid3lC+3Q2qvvJrk
y6q7XsrHLwb6QedilVMoL1ZXHzLEqssTUDAPW6SUqxrixQq6QQ
wotMBGD46ZyeDrM4tNMgBM/HdpDSi5Uphj1dY+EgfIDddoUs3NE

Friday, March 7, 2014

독수리 오형제 극장판 예고편

Tuesday, March 4, 2014

Scientists revive 30,000 year old 'giant virus' from Siberian permafrost - and warn more could be exposed due to global warming

Warn melting ice around the world could uncover new biological threats that 'might not be exempt from future threats to human or animal health'
Virus was able to infect amoeba cells - although not believed to pose a threat to human health

By Mark Prigg
PUBLISHED: 21:52 GMT, 3 March 2014 | UPDATED: 22:05 GMT, 3 March 2014

Scientsts have successfully revived a 30,000 year old giant virus frozen in ice.They say the virus is a type never before seen - and warn that global warming could lead to more being uncovered.
The researchers say the find could reveal viruses are far more diverse than previously thought - and warn the ancient viruses could affect humans.

A closeup of the 30,000 year old virus infecting an amoeba cell. They say the virus is a type never before seen - and warn that global warming could lead to more being uncovered

REVIVING A VIRUS

The team incubated 30,000-year-old Siberian permafrost core samples with Acanthamoeba castellanii, a common host of giant viruses.
They found the cells exploded, and when examined under a microscope, showed the presence of a giant virus particle known as a pandovirus, a type previously unseen.

The authors of the new paper, a mix of French and Russian researchers, identified the virus by taking a culture of amoebas found in the permafrost, and adding some of the permafrost.
Dubbed Pithovirus sibericum, the virus was found in a 30-metre (98-foot) -deep sample of permanently frozen soil taken from coastal tundra in Chukotka, near the East Siberia Sea, where the average annual temperature is minus 13.4 degrees Celsius (7.8 degrees Fahrenheit).

The team thawed the virus and watched it replicate in a culture in a petri dish, where it infected a simple single-cell organism called an amoeba.

Radiocarbon dating of the soil sample found that vegetation grew there more than 30,000 years ago, a time when mammoths and Neanderthals walked the Earth, according to a paper published in the US journal Proceedings of the National Academy of Sciences (PNAS).

More...

They found the cells exploded, and when examined under a microscope, showed the presence of a giant virus particle known as a pandovirus.
'While initiating a survey of the Siberian permafrost, we isolated a third type of giant virus combining the Pandoravirus morphology with a gene content more similar to that of icosahedral DNA viruses,' the team wrote.

he authors of the new paper, a mix of French and Russian researchers, identified the virus by taking a culture of amoebas found in the permafrost, and adding some of the permafrost.

P. sibericum is, on the scale of viruses, a giant -- it has 500 genes, whereas the influenza virus has only eight.

It is the first in a new category of viral whoppers, a family known as Megaviridae, for which two other categories already exist.

The virus gets its name from "pithos," the ancient Greek word for a jar, as it comes in an amphora shape.
It is so big (1.5 millionths of a metre) that it can be seen through an optical microscope, rather than the more powerful electron microscope.

Unlike the flu virus, though, P. sibericum is harmless to humans and animals, for it only infects a type of amoeba called Acanthamoeba, the researchers said.

The work shows that viruses can survive being locked up in the permafrost for extremely long periods, France's National Centre for Scientific Research (CNRS) said in a press statement.

'It has important implications for public-health risks in connection with exploiting mineral or energy resources in Arctic Circle regions that are becoming more and more accessible through global warming,' it said.

'The revival of viruses that are considered to have been eradicated, such as the smallpox virus, whose replication process is similar to that of Pithovirus, is no longer limited to science fiction.

'The risk that this scenario could happen in real life has to be viewed realistically.'

The researchers warn that rising temperatures cold release more viruses from areas such as Siberia (pictured)

They believe the finding could mean there are far more diverse types of virus than previously thought.
'This suggests that pandoravirus-like particles may correspond to an unexplored diversity of unconventional DNA virus families.'
The virus was was found frozen in ice close to the East Siberian Sea.
The team say the find was unusual because fo the size of the virus.
'Giant DNA viruses are visible under a light microscope and their genomes encode more proteins than some bacteria or intracellular parasitic eukaryotes.'
They want that global warming could lead to potential health threats.
'The revival of such an ancestral amoeba-infecting virus used as a safe indicator of the possible presence of pathogenic DNA viruses, suggests that the thawing of permafrost either from global warming or industrial exploitation of circumpolar regions might not be exempt from future threats to human or animal health.'

Monday, March 3, 2014

ハッシュアプリフォント Font 書体数字日本語中国語繁体字中国語簡体字韓国語欧文記号

(アプリ) [Font] メイリオ系フォントVer6.20(日本語15書体・中国語簡体字6書体・中国語繁体字6書体・韓国語3書体).zip 98,104,451 70080eedb67cc80698972493f7fee4c1ee57e80f (アプリ)[フォント] (改良版) 游明朝体 Pr6N M (Kinoppy for Android版→Windows使用可に改変)[OpenTypeFont]..zip FeTiB5R4C3 7,655,311 fcd3dd5a09e900f9ef2dfd013051ad519cae394f (アプリ)[フォント] (OTF)游明朝体 Pr6N M (Kinoppy for Android版→Windowsで使用可能に改変)[OpenTypeFont]..zip 7,655,311 fcd3dd5a09e900f9ef2dfd013051ad519cae394f (アプリ) [Font] 游系日本語TTFフォント6書体 (2013.08.22.改訂版).zip 41,207,679 e00b20d7e64a69d7eb893bb26309165dabdd3290 [フォント] 游明朝・游ゴシック(ttf)2書体各3ウェイト計6ファイル [Windows8.1以降搭載日本語Font](2013.08.22.改訂版).zip 41,207,679 e00b20d7e64a69d7eb893bb26309165dabdd3290 [フォント] (改良版) 游明朝体 Pr6N M (Kinoppy for Android版→Windows使用可に改変)[OpenTypeFont].zip FeTiB5R4C3 7,655,311 fcd3dd5a09e900f9ef2dfd013051ad519cae394f [Font] モリサワフォント2011.08改訂 A-OTFリュウミン・新ゴ(AdobeJapan1-6N準拠)＝2書体86ファイル.zip 374,196,746 c16b96b4aced9b625be520be9e74d1c7e406ba59 [Font] モリサワフォント2011.08改訂 A-OTFゴシックMB101・中ゴPr6・Pr6N(AdobeJapan1-6N準拠)＝2書体16ファイル.zip 85,988,629 c67a610004610b8973ae9470f2a5789f728d7093 [Font] フォントワークス LETS 2010年度（パッチ済）[2010-2-09]（ロダン・筑紫明朝Pr5Nほか54書体260箇）.rar 833,529,861 16cc05631b13177804151b0f0b157b69cea91245 (アプリ) [Font] フォントワークス日本語OTFフォント260書体 (2010.02.09.改訂版).zip 1,019,115,432 9c227e0928ba0564e865710004c62ba0df61f2c6 (アプリ) [Font] モリサワOTFフォント243書体・数字448書体 (2007.10.15.改訂版).zip 566,398,897 5a085dd7110f0d7b41a5201318cd87954a565f57 (アプリ) [Font] モリサワOTFフォント263書体・数字 (2008改訂版).zip 645,238,392 0d104d8642060742c905ce3e4e84e2fc8fdd82ee (アプリ) [Font] モリサワOTFフォント405書体・数字464書体・欧文20書体・記号24書体 (2011.08.01.改訂版).zip 1,366,890,667 753a834ce983557b776e222c1f92bf23d486843e (アプリ) [Font] モリサワフォント 2011.08改訂 A-OTFリュウミン・新ゴ(AdobeJapan1-6N準拠)＝2書体86ファイル.zip 374,196,746 c16b96b4aced9b625be520be9e74d1c7e406ba59 (アプリ) [Font] モリサワフォント 2011.08改訂 A-OTFゴシックMB101・中ゴPr6・Pr6N(AdobeJapan1-6N準拠)＝2書体16ファイル.zip 85,988,629 c67a610004610b8973ae9470f2a5789f728d7093 (アプリ) [Font] モリサワフォント2010年度(パッチ済) OTF UD新ゴ・UD新ゴNT・UD新丸ゴ・UD藜ミン＝4書体24ファイル.zip 86,435,849 609d95b736725556f8bb1656bcfeac4aabc17e18 [フォント] 視覚デザイン研究所 TrueTypeFont11書体51箇（テラG・メガG・ラインG・ロゴG・ペンG・ギガjr・ロゴjr・ギガ丸・メガ丸・ロゴ丸・ペンLady）.zip 118,387,370 436ae0a2d09ad43148ed949d17c5e941f72da3d1 [フォント] (OTF)小塚明朝・ゴシック×Pr6N・Pro(ver6.014／4.013)各６ウェイト計24書体(2012.04.15.改訂版AdobeCS6より抽出)[OpenTypeFont].zip 100,720,825 6d85eca86fffcd47223ae7c53f3af9c5e6249655 [アプリ][フォント][Font]厨隔離スレ既出パック.7z yiijudeiBhwqzMqIWr 344,129,511 4b069c57ac3a3c2fde3a61c0f89d3946290b7c36

Friday, February 28, 2014

eMule Server

Sunday, February 16, 2014

【GTA5実況】赤髪のともと愉快な仲間たち

Saturday, February 15, 2014

Siriに「話して」って言ったらめっちゃ長い物語聞かされた

Friday, February 14, 2014

스텔라 - 마리오네트

Saturday, February 8, 2014

Using Google Public DNS

Configuring your network settings to use Google Public DNS When you use Google Public DNS, you are changing your DNS "switchboard" operator from your ISP to Google Public DNS. In most cases, the IP addresses used by your ISP's domain name servers are automatically set by your ISP via the Dynamic Host Configuration Protocol (DHCP). To use Google Public DNS, you need to explicitly change the DNS settings in your operating system or device to use the Google Public DNS IP addresses. The procedure for changing your DNS settings varies according to operating system and version (Windows, Mac or Linux) or the device (computer, phone, or router). We give general procedures here that might not apply for your OS or device; please consult your vendor documentation for authoritative information. Note: We recommend that only users who are proficient with configuring operating system settings make these changes. Important: Before you start Before you change your DNS settings to use Google Public DNS, be sure to write down the current server addresses or settings on a piece of paper. It is very important that you keep these numbers for backup purposes, in case you need to revert to them at any time. We also recommend that you print this page, in the event that you encounter a problem and need to refer to these instructions. Google Public DNS IP addresses The Google Public DNS IP addresses (IPv4) are as follows: 8.8.8.8 8.8.4.4 The Google Public DNS IPv6 addresses are as follows: 2001:4860:4860::8888 2001:4860:4860::8844 You can use either number as your primary or secondary DNS server. You can specify both numbers, but do not specify one number as both primary and secondary. You can configure Google Public DNS addresses for either IPv4 or IPv6 connections, or both. Changing your DNS servers settings Because the instructions differ between different versions/releases of each operating system, we only give one version as an example. If you need specific instructions for your operating system/version, please consult your vendor's documentation. You may also find answers on our user group. Many systems allow you to specify multiple DNS servers, to be contacted in a priority order. In the following instructions, we provide steps to specify only the Google Public DNS servers as the primary and secondary servers, to ensure that your setup will correctly use Google Public DNS in all cases. Note: Depending on your network setup, you may need administrator/root privileges to change these settings. Microsoft Windows DNS settings are specified in the TCP/IP Properties window for the selected network connection. Example: Changing DNS server settings on Microsoft Windows 7 Go the Control Panel. Click Network and Internet, then Network and Sharing Center, and click Change adapter settings. Select the connection for which you want to configure Google Public DNS. For example: To change the settings for an Ethernet connection, right-click Local Area Connection, and click Properties. To change the settings for a wireless connection, right-click Wireless Network Connection, and click Properties. If you are prompted for an administrator password or confirmation, type the password or provide confirmation. Select the Networking tab. Under This connection uses the following items, select Internet Protocol Version 4 (TCP/IPv4) or Internet Protocol Version 6 (TCP/IPv6) and then click Properties. Click Advanced and select the DNS tab. If there are any DNS server IP addresses listed there, write them down for future reference, and remove them from this window. Click OK. Select Use the following DNS server addresses. If there are any IP addresses listed in the Preferred DNS server or Alternate DNS server, write them down for future reference. Replace those addresses with the IP addresses of the Google DNS servers: For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Restart the connection you selected in step 3. Test that your setup is working correctly; see Testing your new settings below. Repeat the procedure for additional network connections you want to change. Mac OS X DNS settings are specified in the Network window. Example: Changing DNS server settings on Mac OS 10.5 From the Apple menu, click System Preferences, then click Network. If the lock icon in the lower left-hand corner of the window is locked, click the icon to make changes, and when prompted to authenticate, enter your password. Select the connection for which you want to configure Google Public DNS. For example: To change the settings for an Ethernet connection, select Built-In Ethernet, and click Advanced. To change the settings for a wireless connection, select Airport, and click Advanced. Select the DNS tab. Click + to replace any listed addresses with, or add, the Google IP addresses at the top of the list: For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Click Apply and OK. Test that your setup is working correctly; see Testing your new settings below. Repeat the procedure for additional network connections you want to change. Linux In most modern Linux distributions, DNS settings are configured through Network Manager. Example: Changing DNS server settings on Ubuntu In the System menu, click Preferences, then click Network Connections. Select the connection for which you want to configure Google Public DNS. For example: To change the settings for an Ethernet connection, select the Wired tab, then select your network interface in the list. It is usually called eth0. To change the settings for a wireless connection, select the Wireless tab, then select the appropriate wireless network. Click Edit, and in the window that appears, select the IPv4 Settings or IPv6 Settings tab. If the selected method is Automatic (DHCP), open the dropdown and select Automatic (DHCP) addresses only instead. If the method is set to something else, do not change it. In the DNS servers field, enter the Google Public DNS IP addresses, separated by a space: For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Click Apply to save the change. If you are prompted for a password or confirmation, type the password or provide confirmation. Test that your setup is working correctly; see Testing your new settings below. Repeat the procedure for additional network connections you want to change. If your distribution doesn't use Network Manager, your DNS settings are specified in /etc/resolv.conf. Example: Changing DNS server settings on a Debian server Edit /etc/resolv.conf: sudo vi /etc/resolv.conf If any nameserver lines appear, write down the IP addresses for future reference. Replace the nameserver lines with, or add, the following lines: For IPv4: nameserver 8.8.8.8 nameserver 8.8.4.4 For IPv6: nameserver 2001:4860:4860::8888 nameserver 2001:4860:4860::8844 Save and exit. Restart any Internet clients you are using. Test that your setup is working correctly; see Testing your new settings below. Additionally, if you are using DHCP client software that overwrites the settings in /etc/resolv.conf, you will need to set up the client accordingly by editing the client's configuration file. Example: Configuring DHCP client sofware on a Debian server Back up /etc/resolv.conf: sudo cp /etc/resolv.conf /etc/resolv.conf.auto Edit /etc/dhcp3/dhclient.conf: sudo vi /etc/dhcp3/dhclient.conf If there is a line containing domain-name-servers, write down the IP addresses for future reference. Replace that line with, or add, the following line: For IPv4: prepend domain-name-servers 8.8.8.8, 8.8.4.4; For IPv6: prepend domain-name-servers 2001:4860:4860::8888, 2001:4860:4860::8844; Save and exit. Restart any Internet clients you are using. Test that your setup is working correctly; see Testing your new settings below. Routers Every router uses a different user interface for configuring DNS server settings; we provide only a generic procedure below. For more information, please consult your router documentation. Note: Some ISPs hard-code their DNS servers into the equipment they provide; if you are using such a device, you will not be able to configure it to use Google Public DNS. Instead, you can configure each of the computers connected to the router, as described above. To change your settings on a router: In your browser, enter the IP address to access the router's administration console. When prompted, enter the password to access network settings. Find the screen in which DNS server settings are specified. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference. Replace those addresses with the Google IP addresses: For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Save and exit. Restart your browser. Test that your setup is working correctly; see Testing your new settings below. Mobile or other devices DNS servers are typically specified under advanced wi-fi settings. However, as every mobile device uses a different user interface for configuring DNS server settings, we provide only a generic procedure below. For more information, please consult your mobile provider's documentation. To change your settings on a mobile device: Go to the screen in which wi-fi settings are specified. Find the screen in which DNS server settings are specified. If there are IP addresses specified in the fields for the primary and seconday DNS servers, write them down for future reference. Replace those addresses with the Google IP addresses: For IPv4: 8.8.8.8 and/or 8.8.4.4. For IPv6: 2001:4860:4860::8888 and/or 2001:4860:4860::8844 Save and exit. Test that your setup is working correctly; see Testing your new settings below. Testing your new settings To test that the Google DNS resolver is working: From your browser, type in a hostname (such as http://www.google.com/). If it resolves correctly, bookmark the page, and try accessing the page from the bookmark. If both of these tests work, everything is working correctly. If not, go to step 2. From your browser, type in a fixed IP address. You can use http://18.62.0.96/ (which points to the website http://www.eecs.mit.edu/) as the URL.* If this works correctly, bookmark the page, and try accessing the page from the bookmark. If these tests work (but step 1 fails), then there is a problem with your DNS configuration; check the steps above to make sure you have configured everything correctly. If these tests do not work, go to step 3. Roll back the DNS changes you made and run the tests again. If the tests still do not work, then there is a problem with your network settings; contact your ISP or network administrator for assistance. * Google thanks MIT for granting permission to use this URL for the purposes of testing web connectivity. Diagnosing resolution problems If you are encountering problems when resolving particular names, and want to verify whether the problem is with Google Public DNS, please try running the following diagnostic procedures. If you want to report a problem to the Google Public DNS user group, please copy and paste the results of the commands in your email. This information is vital to help us to identify the cause of the problem. Step 1: Check to see if the authoritative nameservers are correct If Google Public DNS (or any open resolver) has trouble resolving a site, or returns inconsistent answers, sometimes it is because the authoritative nameservers are having trouble. There are various tools and sites to help you check this. Some users (and Google Public DNS engineers) have found intoDNS very helpful. For example, if you have trouble visiting www.example.com, visit intodns.com and enter example.com (the domain for www.example.com), or visit http://intodns.com/example.com directly. Additionally, DNSViz is useful for diagnosing DNSSEC related issues. For example, visit dnsviz.net and enter example.com (the domain for www.example.com), or visit http://dnsviz.net/d/example.com/dnssec/ directly. If these tools identify a nameserver configuration issue, please contact the owner of the nameserver to fix it. If none of these tools finds any issue with the nameserver, continue to step 2. Step 2: Verify that your client can communicate with the Google Public DNS servers IPv4 Open a command prompt, and run the following command: On Windows tracert -d 8.8.8.8 On Mac OS X /usr/sbin/traceroute -n -w 2 -q 2 -m 30 8.8.8.8 On Linux sudo traceroute -n -w 2 -q 2 -m 30 8.8.8.8 If the last line of the output does not list 8.8.8.8 as the final hop, or if there are significant timeouts, there may be a network problem preventing you from contacting our servers. Please include the output of the command in any communication with the Google Public DNS team. If the last line of the output does list 8.8.8.8 as the final hop, continue to step 3. IPv6 Open a command prompt, and run the following command: On Windows tracert -d 2001:4860:4860::8888 On Mac OS X /usr/sbin/traceroute6 -n -w 2 -q 2 -m 30 2001:4860:4860::8888 On Linux sudo traceroute -n -w 2 -q 2 -m 30 2001:4860:4860::8888 If the last line of the output does not list 2001:4860:4860::8888 as the final hop, or if there are significant timeouts, there may be a network problem preventing you from contacting our servers. Try configuring Google Public DNS for IPv4 to diagnose whether the problem is due to IPv6 connectivity on your network. If IPv4 works for you, you may want to revert your IPv6 configuration and use Google Public DNS with IPv4 exclusively. Otherwise, please include the output of the command in any communication with the Google Public DNS team. If the last line of the output does list 2001:4860:4860::8888 as the final hop, continue to step 3. Step 3: Verify that Google Public DNS can resolve the selected hostname In the following steps, replace www.example.com. with the name that you had difficulty resolving. (Put a period at the end of the name to avoid problems with domain suffixes and search lists.) IPv4 At the command prompt, run the following command: On Windows nslookup -debug www.example.com. 8.8.8.8 On Mac and Linux dig @8.8.8.8 www.example.com. If the output shows an answer section with an A record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team. If the output does not show an answer for the hostname, continue to step 4. IPv6 At the command prompt, run the following command:* On Windows nslookup -debug -type=AAAA www.example.com. 2001:4860:4860::8888 On Mac and Linux dig @2001:4860:4860::8888 www.example.com. AAAA If the output shows an answer section with an AAAA record for the hostname, then Google Public DNS is able to resolve the name. Check your settings to make sure your system is correctly configured to use Google Public DNS. If you are still unable to solve the problem, please include the output of the command in any communication with the Google Public DNS team. If the output shows an answer section with an A (IPv4) record for the hostname, then Google Public DNS is able to resolve the name, but the host and/or its nameserver are not configured to return IPv6 results. If you want to verify that you are correctly receiving AAAA records, you can use the hostname ipv6.google.com as a generic test. If the output for ipv6.google.com, or another host for which you are certain IPv6 records exist, does not show an answer, continue to step 4. * Note: Google properties will not return AAAA records for all users. Please see the Google over IPv6 page for more information about whether your system qualifies. Step 4: Verify that Google Public DNS can resolve the selected hostname without performing DNSSEC validation Google Public DNS performs DNSSEC validation for all DNS queries by default. When a nameserver fails DNSSEC validation, Google Public DNS returns SERVFAIL. To verify whether Google Public DNS can resolve the hostname without performing DNSSEC validation, run the following command: On Windows Unfortunately, nslookup does not support DNSSEC and cannot help diagnosis here. Continue to step 5. On Mac and Linux IPv4 dig @8.8.8.8 www.example.com. +cd IPv6 dig @2001:4860:4860::8888 www.example.com. AAAA +cd If you cannot get a successful result without DNSSEC validation either, continue to step 5. If you get a successful result, this usually indicates a DNSSEC misconfiguration at the nameserver. Please make sure that you have followed through step 1. If none of the tools finds any issue with the nameserver, continue to step 5. Step 5: Verify that another open resolver can resolve the selected hostname At the command prompt, run one of the following commands: On Windows nslookup www.example.com. 4.2.2.1 nslookup www.example.com. 4.2.2.2 nslookup www.example.com. 208.67.222.222 nslookup www.example.com. 208.67.220.220 On Mac and Linux dig www.example.com. @4.2.2.1 dig www.example.com. @4.2.2.2 dig www.example.com. @208.67.222.222 dig www.example.com. @208.67.220.220 (The first two commands test Level 3's DNS servers. The last two commands test OpenDNS's DNS servers.) If you are unable to get a successful result, this means that there is most likely a problem with the server you are trying to contact. Wait some time and try running the tests again. This may be a temporary problem on the server's side that will likely resolve itself eventually. If it does not, you should contact the owner of the server. If you are able to get a successful result, there may be a problem with Google Public DNS. Please follow the directions here to report an issue to the Google Public DNS team, and include the output of the commands you ran in the report. Switching back to your old DNS settings If you had not previously configured any customized DNS servers, to switch back to your old settings, in the window in which you specified the Google IP addresses, select the option to enable obtaining DNS server addresses automatically, and/or delete the Google IP addresses. This will revert your settings to using your ISP's default servers. If you need to manually specify any addresses, use the procedures above to specify the old IP addresses. If necessary, restart your system.

I Like It !