{"id":476906,"date":"2023-08-09T09:05:02","date_gmt":"2023-08-09T09:05:02","guid":{"rendered":""},"modified":"2023-09-05T11:13:38","modified_gmt":"2023-09-05T11:13:38","slug":"dns-ns-record","status":"publish","type":"wiki","link":"https:\/\/oneproxy.pro\/tr\/wiki\/dns-ns-record\/","title":{"rendered":"DNS NS kayd\u0131"},"content":{"rendered":"<p>DNS (Alan Ad\u0131 Sistemi) NS kayd\u0131, DNS altyap\u0131s\u0131n\u0131n kritik bir bile\u015fenidir ve alan adlar\u0131 ile bunlara kar\u015f\u0131l\u0131k gelen yetkili ad sunucular\u0131 aras\u0131nda \u00f6nemli bir ba\u011flant\u0131 g\u00f6revi g\u00f6r\u00fcr. NS, &quot;Ad Sunucusu&quot; anlam\u0131na gelir ve bu kay\u0131tlar, belirli bir etki alan\u0131 i\u00e7in DNS sorgular\u0131n\u0131n i\u015flenmesinden hangi ad sunucular\u0131n\u0131n sorumlu oldu\u011funu tan\u0131mlar. Bir kullan\u0131c\u0131 web taray\u0131c\u0131s\u0131na bir alan ad\u0131 girdi\u011finde, DNS NS kayd\u0131, iste\u011fin uygun ad sunucusuna y\u00f6nlendirilmesine yard\u0131mc\u0131 olarak kullan\u0131c\u0131n\u0131n web sitesini bar\u0131nd\u0131ran do\u011fru web sunucusuna ula\u015fmas\u0131n\u0131 sa\u011flar.<\/p>\n<h2>DNS NS kayd\u0131n\u0131n k\u00f6keninin tarihi ve ilk s\u00f6z\u00fc<\/h2>\n<p>Alan Ad\u0131 Sistemi, internet kaynaklar\u0131na eri\u015fmek i\u00e7in insanlar taraf\u0131ndan daha okunabilir bir yol sa\u011flamak amac\u0131yla 1980&#039;lerin ba\u015f\u0131nda da\u011f\u0131t\u0131lm\u0131\u015f bir adland\u0131rma sistemi olarak tan\u0131t\u0131ld\u0131. DNS&#039;den \u00f6nce, merkezi bir HOSTS.TXT dosyas\u0131 korunuyordu, ancak internetteki ana bilgisayar say\u0131s\u0131 artt\u0131k\u00e7a bu kullan\u0131\u015fs\u0131z hale geldi. Bu bilginin da\u011f\u0131t\u0131lmas\u0131 ve tek bir hata noktas\u0131ndan ka\u00e7\u0131n\u0131lmas\u0131 ihtiyac\u0131, DNS&#039;nin geli\u015ftirilmesine yol a\u00e7t\u0131.<\/p>\n<p>NS kayd\u0131yla temsil edilen yetkili ad sunucular\u0131 kavram\u0131, Kas\u0131m 1987&#039;de yay\u0131nlanan RFC 1034 ve RFC 1035&#039;te tan\u0131t\u0131ld\u0131. Bu belgeler, NS kayd\u0131 da dahil olmak \u00fczere DNS sisteminin mimarisini ve \u00f6zelliklerini \u00f6zetledi. NS kayd\u0131, ba\u015flang\u0131c\u0131ndan bu yana DNS altyap\u0131s\u0131n\u0131n ayr\u0131lmaz bir par\u00e7as\u0131 olmu\u015ftur ve internetin i\u015fleyi\u015fi i\u00e7in temel olmaya devam etmektedir.<\/p>\n<h2>DNS NS kayd\u0131 hakk\u0131nda ayr\u0131nt\u0131l\u0131 bilgi \u2013 DNS NS kayd\u0131 konusunu geni\u015fletme<\/h2>\n<p>DNS NS kayd\u0131, alan adlar\u0131n\u0131n kar\u015f\u0131l\u0131k gelen IP adreslerine \u00e7\u00f6z\u00fcmlenmesi i\u00e7in gereklidir. Her etki alan\u0131, NS kay\u0131tlar\u0131 kullan\u0131larak belirtilen ve o etki alan\u0131 i\u00e7in DNS kay\u0131tlar\u0131n\u0131n depolanmas\u0131ndan sorumlu olan en az bir yetkili ad sunucusuna sahip olmal\u0131d\u0131r.<\/p>\n<h2>DNS NS kayd\u0131n\u0131n i\u00e7 yap\u0131s\u0131 \u2013 DNS NS kayd\u0131 nas\u0131l \u00e7al\u0131\u015f\u0131r?<\/h2>\n<p>DNS NS kayd\u0131n\u0131n i\u00e7 yap\u0131s\u0131 basittir. Bir alan ad\u0131 ve bir ad sunucusu adresinden olu\u015fur. Alan ad\u0131, ad sunucusunun yetkili oldu\u011fu b\u00f6lgeyi tan\u0131mlar ve ad sunucusu adresi, yetkili sunucunun IP adresini belirtir.<\/p>\n<p>Bir kullan\u0131c\u0131 bir alan ad\u0131n\u0131 sorgulad\u0131\u011f\u0131nda, DNS \u00e7\u00f6z\u00fcmleyicisi yetkili ad sunucusunu belirlemek i\u00e7in ilk olarak NS kayd\u0131n\u0131 arar. \u00c7\u00f6z\u00fcmleyici, yetkili ad sunucusunun IP adresini ald\u0131ktan sonra, alan ad\u0131 i\u00e7in gerekli DNS bilgilerini almak \u00fczere \u00f6zellikle s\u00f6z konusu ad sunucusuna yeni bir sorgu g\u00f6nderir. Bu i\u015fleme \u00f6zyinelemeli DNS \u00e7\u00f6z\u00fcmlemesi ad\u0131 verilir.<\/p>\n<h2>DNS NS kayd\u0131n\u0131n temel \u00f6zelliklerinin analizi<\/h2>\n<p>DNS NS kayd\u0131, DNS hiyerar\u015fisinde \u00e7ok \u00f6nemli bir rol oynar ve \u00e7e\u015fitli temel \u00f6zellikler ve avantajlar sunar:<\/p>\n<ol>\n<li>\n<p><strong>Art\u0131kl\u0131k ve Hata Tolerans\u0131:<\/strong> Y\u00f6neticiler, bir etki alan\u0131 i\u00e7in birden fazla NS kayd\u0131na izin vererek birden fazla yetkili ad sunucusu atayabilir. Bu yedeklilik, sanki bir ad sunucusu kullan\u0131lamaz hale gelirken di\u011ferleri hala etki alan\u0131 i\u00e7in DNS sorgular\u0131n\u0131 i\u015fleyebiliyormu\u015f gibi hata tolerans\u0131 sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Delegasyon:<\/strong> NS kayd\u0131, alan sahiplerinin alt alan adlar\u0131n\u0131 farkl\u0131 ad sunucular\u0131na devretmesine olanak tan\u0131yarak b\u00fcy\u00fck ve karma\u015f\u0131k altyap\u0131lar\u0131n y\u00f6netilmesinde esneklik ve \u00f6l\u00e7eklenebilirlik sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Y\u00fck dengeleme:<\/strong> NS kay\u0131tlar\u0131n\u0131 birden fazla ad sunucusuna da\u011f\u0131tmak, y\u00fck dengelemeyi kolayla\u015ft\u0131rabilir; \u00e7\u00fcnk\u00fc DNS \u00e7\u00f6z\u00fcmleyicileri, ad sunucular\u0131ndan birini rastgele se\u00e7erek sorgu y\u00fcklerini e\u015fit \u015fekilde da\u011f\u0131tabilir.<\/p>\n<\/li>\n<\/ol>\n<h2>DNS NS kayd\u0131 t\u00fcrleri<\/h2>\n<p>DNS NS kayd\u0131, etki alan\u0131n\u0131n yap\u0131land\u0131rmas\u0131na ve gereksinimlerine ba\u011fl\u0131 olarak farkl\u0131 t\u00fcrlerde olabilir. En yayg\u0131n t\u00fcrler \u015funlar\u0131 i\u00e7erir:<\/p>\n<table>\n<thead>\n<tr>\n<th>Tip<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>\u0130nternette)<\/td>\n<td>\u00c7o\u011fu internet alan\u0131 i\u00e7in kullan\u0131lan standart NS kayd\u0131.<\/td>\n<\/tr>\n<tr>\n<td>CH (Kaos)<\/td>\n<td>Nadiren kullan\u0131l\u0131r, \u00f6zellikle sunucu durumunu sorgulamak i\u00e7in kullan\u0131l\u0131r.<\/td>\n<\/tr>\n<tr>\n<td>HS (Hesiodos)<\/td>\n<td>Hesiod ad alan\u0131 sistemlerinde kullan\u0131l\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>DNS NS kayd\u0131n\u0131 kullanma yollar\u0131, kullan\u0131mla ilgili sorunlar ve \u00e7\u00f6z\u00fcmleri<\/h2>\n<h3>DNS NS kayd\u0131n\u0131 kullanma yollar\u0131:<\/h3>\n<ol>\n<li>\n<p><strong>Alan Ad\u0131 Tescili:<\/strong> Alan ad\u0131 kayd\u0131 s\u0131ras\u0131nda, alan ad\u0131 kay\u0131t kurulu\u015fu genellikle kullan\u0131c\u0131lar\u0131n alan ad\u0131 i\u00e7in yetkili ad sunucular\u0131n\u0131 NS kay\u0131tlar\u0131 arac\u0131l\u0131\u011f\u0131yla belirtmesini gerektirir.<\/p>\n<\/li>\n<li>\n<p><strong>DNS B\u00f6lge Y\u00f6netimi:<\/strong> Y\u00f6neticiler, DNS b\u00f6lgelerini y\u00f6netmek ve alt alan adlar\u0131n\u0131 farkl\u0131 ad sunucular\u0131na devretmek i\u00e7in NS kay\u0131tlar\u0131n\u0131 kullan\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Bar\u0131nd\u0131rma Sa\u011flay\u0131c\u0131lar\u0131n\u0131 De\u011fi\u015ftirme:<\/strong> Bir web sitesini yeni bir bar\u0131nd\u0131rma sa\u011flay\u0131c\u0131s\u0131na ta\u015f\u0131rken, NS kay\u0131tlar\u0131n\u0131n g\u00fcncellenmesi, yeni sa\u011flay\u0131c\u0131n\u0131n ad sunucular\u0131n\u0131n DNS sorgular\u0131n\u0131 i\u015flemesine olanak tan\u0131r.<\/p>\n<\/li>\n<\/ol>\n<h3>DNS NS kayd\u0131n\u0131n kullan\u0131m\u0131na ili\u015fkin sorunlar ve \u00e7\u00f6z\u00fcmleri:<\/h3>\n<ol>\n<li>\n<p><strong>Yay\u0131lma Gecikmeleri:<\/strong> NS kay\u0131tlar\u0131n\u0131 de\u011fi\u015ftirirken, DNS yay\u0131lma gecikmeleri meydana gelebilir ve bu da genel olarak tutars\u0131z yan\u0131tlara neden olabilir. Bunu azaltmak i\u00e7in y\u00f6neticiler, de\u011fi\u015fiklikten \u00f6nce DNS kay\u0131tlar\u0131n\u0131n TTL&#039;sini (Ya\u015fam S\u00fcresi) azaltarak yay\u0131lma s\u00fcresini azaltabilir.<\/p>\n<\/li>\n<li>\n<p><strong>Yanl\u0131\u015f yap\u0131land\u0131r\u0131lm\u0131\u015f NS Kay\u0131tlar\u0131:<\/strong> Yanl\u0131\u015f NS kay\u0131tlar\u0131 DNS \u00e7\u00f6z\u00fcmleme hatalar\u0131na yol a\u00e7abilir. Y\u00f6neticiler, NS kay\u0131tlar\u0131n\u0131n do\u011fru \u015fekilde ayarland\u0131\u011f\u0131ndan ve ge\u00e7erli ad sunucusu IP adreslerine i\u015faret etti\u011finden emin olmal\u0131d\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>DNS \u00d6nbellek Zehirlenmesi:<\/strong> K\u00f6t\u00fc niyetli akt\u00f6rler, DNS \u00f6nbelleklerini yanl\u0131\u015f NS kay\u0131tlar\u0131yla zehirlemeye \u00e7al\u0131\u015fabilir. DNSSEC&#039;nin (Alan Ad\u0131 Sistemi G\u00fcvenlik Uzant\u0131lar\u0131) uygulanmas\u0131, DNS verilerine dijital imzalar ekleyerek bu t\u00fcr sald\u0131r\u0131lara kar\u015f\u0131 koruma sa\u011flayabilir.<\/p>\n<\/li>\n<\/ol>\n<h2>Ana \u00f6zellikler ve benzer terimlerle kar\u015f\u0131la\u015ft\u0131rmalar<\/h2>\n<table>\n<thead>\n<tr>\n<th>Terim<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>DNS NS Kayd\u0131<\/td>\n<td>Bir etki alan\u0131 i\u00e7in yetkili ad sunucular\u0131n\u0131 belirtir.<\/td>\n<\/tr>\n<tr>\n<td>DNS A Kayd\u0131<\/td>\n<td>Bir alan ad\u0131n\u0131 bir IPv4 adresiyle e\u015fler.<\/td>\n<\/tr>\n<tr>\n<td>DNS AAAA Kayd\u0131<\/td>\n<td>Bir alan ad\u0131n\u0131 bir IPv6 adresiyle e\u015fler.<\/td>\n<\/tr>\n<tr>\n<td>DNS CNAME Kayd\u0131<\/td>\n<td>Ba\u015fka bir alan ad\u0131 (kanonik ad) i\u00e7in takma ad olu\u015fturur.<\/td>\n<\/tr>\n<tr>\n<td>DNS MX Kayd\u0131<\/td>\n<td>Bir alan ad\u0131 i\u00e7in e-posta almaktan sorumlu posta sunucular\u0131n\u0131 tan\u0131mlar.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>DNS NS kayd\u0131yla ilgili gelece\u011fin perspektifleri ve teknolojileri<\/h2>\n<p>DNS altyap\u0131s\u0131, ortaya \u00e7\u0131kan zorluklar\u0131n \u00fcstesinden gelmek ve performans\u0131 art\u0131rmak i\u00e7in s\u00fcrekli olarak geli\u015fmektedir. DNS NS kay\u0131tlar\u0131yla ilgili gelecekteki baz\u0131 potansiyel geli\u015fmeler \u015funlar\u0131 i\u00e7erir:<\/p>\n<ol>\n<li>\n<p><strong>IPv6&#039;n\u0131n Kabul\u00fc:<\/strong> IPv6&#039;n\u0131n benimsenmesi artt\u0131k\u00e7a, DNS NS kay\u0131tlar\u0131n\u0131n IPv6 adreslerini etkili bir \u015fekilde desteklemesi gerekecektir.<\/p>\n<\/li>\n<li>\n<p><strong>Da\u011f\u0131t\u0131lm\u0131\u015f DNS:<\/strong> Da\u011f\u0131t\u0131lm\u0131\u015f defterlerin veya blockchain teknolojisinin kullan\u0131lmas\u0131, DNS&#039;nin merkezi olmamas\u0131 ve g\u00fcvenli\u011finde iyile\u015ftirmeler getirebilir.<\/p>\n<\/li>\n<\/ol>\n<h2>Proxy sunucular\u0131 nas\u0131l kullan\u0131labilir veya DNS NS kayd\u0131yla nas\u0131l ili\u015fkilendirilebilir?<\/h2>\n<p>Proxy sunucular\u0131, istemciler ve web sunucular\u0131 aras\u0131nda arac\u0131 g\u00f6revi g\u00f6r\u00fcr, istemci isteklerini iletir ve sunucu ad\u0131na yan\u0131tlar\u0131 d\u00f6nd\u00fcr\u00fcr. Proxy sunucular\u0131 do\u011frudan DNS NS kay\u0131tlar\u0131yla ili\u015fkili olmasa da, DNS \u00e7\u00f6z\u00fcmlemesini a\u015fa\u011f\u0131daki yollarla dolayl\u0131 olarak etkileyebilirler:<\/p>\n<ol>\n<li>\n<p><strong>\u00d6nbelle\u011fe almak:<\/strong> Proxy sunucular\u0131, DNS yan\u0131tlar\u0131n\u0131 \u00f6nbelle\u011fe alarak DNS sorgu s\u00fcrelerini ve istemciler i\u00e7in genel gecikme s\u00fcresini azaltabilir.<\/p>\n<\/li>\n<li>\n<p><strong>Y\u00fck dengeleme:<\/strong> Proxy sunucular\u0131, gelen istemci isteklerini birden fazla arka u\u00e7 web sunucusuna da\u011f\u0131tarak y\u00fck dengeleme sa\u011flayabilir ve web sitesi performans\u0131n\u0131 art\u0131rabilir.<\/p>\n<\/li>\n<li>\n<p><strong>G\u00fcvenlik ve Gizlilik:<\/strong> Proxy&#039;ler, m\u00fc\u015fterinin IP adresini web sunucusundan gizleyerek ve k\u00f6t\u00fc ama\u00e7l\u0131 trafi\u011fi filtreleyerek g\u00fcvenli\u011fi ve gizlili\u011fi art\u0131rabilir.<\/p>\n<\/li>\n<\/ol>\n<h2>\u0130lgili Ba\u011flant\u0131lar<\/h2>\n<ul>\n<li><a href=\"https:\/\/tools.ietf.org\/html\/rfc1034\" target=\"_new\" rel=\"noopener nofollow\">RFC 1034 \u2013 Alan Adlar\u0131 \u2013 Kavramlar ve Tesisler<\/a><\/li>\n<li><a href=\"https:\/\/tools.ietf.org\/html\/rfc1035\" target=\"_new\" rel=\"noopener nofollow\">RFC 1035 \u2013 Alan Adlar\u0131 \u2013 Uygulama ve Belirtim<\/a><\/li>\n<li><a href=\"https:\/\/www.oreilly.com\/library\/view\/dns-and-bind\/9781449305050\/\" target=\"_new\" rel=\"noopener nofollow\">DNS ve BIND<\/a> Kriket Liu ve Paul Albitz taraf\u0131ndan<\/li>\n<li><a href=\"https:\/\/www.cloudflare.com\/learning\/dns\/what-is-dns\/\" target=\"_new\" rel=\"noopener nofollow\">DNS&#039;ye giri\u015f<\/a> \u2013 Cloudflare \u00d6\u011frenme Merkezi<\/li>\n<li><a href=\"https:\/\/www.internetsociety.org\/resources\/doc\/2022\/dnssec-a-primer\/\" target=\"_new\" rel=\"noopener nofollow\">DNSSEC: Bir Ba\u015flang\u0131\u00e7<\/a> \u2013 \u0130nternet Toplulu\u011fu<\/li>\n<\/ul>","protected":false},"featured_media":476907,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"class_list":["post-476906","wiki","type-wiki","status-publish","has-post-thumbnail","hentry"],"acf":{"faq_title":"Frequently Asked Questions about <mark>DNS NS Record: A Comprehensive Overview<\/mark>","faq_items":[{"question":"What is a DNS NS record?","answer":"<p>A DNS NS record, also known as a Name Server record, is an essential component of the Domain Name System (DNS). It specifies the authoritative nameservers responsible for handling DNS queries for a specific domain. When you enter a domain name in your web browser, the DNS NS record helps direct the request to the correct nameserver, ensuring you reach the right web server hosting the website.<\/p>"},{"question":"How did the DNS NS record originate?","answer":"<p>The DNS NS record was introduced as part of the Domain Name System in the 1980s. Before DNS, a centralized HOSTS.TXT file managed internet hosts, but it became impractical as the internet grew. The need for distributing information and avoiding single points of failure led to the development of DNS. The concept of authoritative nameservers, represented by the NS record, was defined in RFC 1034 and RFC 1035 published in November 1987.<\/p>"},{"question":"How does the DNS NS record work internally?","answer":"<p>The internal structure of a DNS NS record is straightforward. It comprises a domain name and a nameserver address. The domain name indicates the zone for which the nameserver is authoritative, and the nameserver address specifies the IP address of the authoritative server. When you query a domain name, your DNS resolver looks for the NS record to determine the authoritative nameserver. Then, it sends a new query specifically to that nameserver to fetch the required DNS information for the domain.<\/p>"},{"question":"What are the key features of the DNS NS record?","answer":"<p>The DNS NS record offers several key features:<\/p><ol><li>Redundancy and Fault Tolerance: Multiple NS records can designate several authoritative nameservers, ensuring fault tolerance and reliability.<\/li><li>Delegation: NS records allow domain owners to delegate subdomains to different nameservers, facilitating scalability and management.<\/li><li>Load Balancing: Distributing NS records across multiple nameservers enables load balancing, enhancing query response times.<\/li><\/ol>"},{"question":"What types of DNS NS records exist?","answer":"<p>DNS NS records can be of different types based on domain configurations:<\/p><ul><li>IN (Internet): Standard NS record used for most internet domains.<\/li><li>CH (Chaos): Rarely used, primarily for querying server status.<\/li><li>HS (Hesiod): Used in Hesiod namespace systems.<\/li><\/ul>"},{"question":"How can the DNS NS record be used, and what problems may arise?","answer":"<p>Ways to use DNS NS record:<\/p><ol><li>Domain Registration: During registration, users specify the authoritative nameservers for the domain using NS records.<\/li><li>DNS Zone Management: NS records help administrators manage DNS zones and delegate subdomains to different nameservers.<\/li><li>Changing Hosting Providers: Updating NS records during a migration allows new providers' nameservers to handle DNS queries.<\/li><\/ol><p>Potential problems and solutions:<\/p><ol><li>Propagation Delays: Changing NS records may cause propagation delays. Lowering TTL before the change reduces this time.<\/li><li>Misconfigured NS Records: Incorrect NS records can lead to resolution failures. Ensuring correct settings and valid IP addresses is vital.<\/li><li>DNS Cache Poisoning: Implementing DNSSEC protects against malicious attempts to poison DNS caches with incorrect NS records.<\/li><\/ol>"},{"question":"How does the DNS NS record compare to similar DNS record types?","answer":"<p>The DNS NS record serves a specific purpose - specifying authoritative nameservers. Other DNS record types include:<\/p><ul><li>DNS A Record: Maps a domain name to an IPv4 address.<\/li><li>DNS AAAA Record: Maps a domain name to an IPv6 address.<\/li><li>DNS CNAME Record: Creates an alias for another domain name (canonical name).<\/li><li>DNS MX Record: Identifies mail servers responsible for receiving email for a domain.<\/li><\/ul>"},{"question":"What does the future hold for DNS NS records?","answer":"<p>The DNS infrastructure continually evolves to address challenges and improve performance. Future developments may include improved IPv6 support and the potential integration of distributed ledgers or blockchain technology for enhanced decentralization and security.<\/p>"},{"question":"How are proxy servers associated with DNS NS records?","answer":"<p>While proxy servers are not directly related to DNS NS records, they can influence DNS resolution indirectly. Proxies can cache DNS responses, achieve load balancing, enhance security and privacy, all of which contribute to an improved browsing experience for users.<\/p>"}]},"_links":{"self":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/476906","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki"}],"about":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/types\/wiki"}],"version-history":[{"count":0,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/476906\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media\/476907"}],"wp:attachment":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media?parent=476906"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}