{"id":476927,"date":"2023-08-09T09:05:02","date_gmt":"2023-08-09T09:05:02","guid":{"rendered":""},"modified":"2023-09-05T11:13:40","modified_gmt":"2023-09-05T11:13:40","slug":"dns-redundancy","status":"publish","type":"wiki","link":"https:\/\/oneproxy.pro\/tr\/wiki\/dns-redundancy\/","title":{"rendered":"DNS yedeklili\u011fi"},"content":{"rendered":"<h2>girii\u015f<\/h2>\n<p>DNS yedeklili\u011fi, istikrarl\u0131 ve g\u00fcvenilir bir internet altyap\u0131s\u0131 sa\u011flaman\u0131n \u00f6nemli bir unsurudur. Etki alan\u0131 ad\u0131 \u00e7\u00f6z\u00fcmlemesi i\u00e7in y\u00fcksek kullan\u0131labilirlik, hata tolerans\u0131 ve y\u00fck da\u011f\u0131t\u0131m\u0131 sa\u011flamak \u00fczere yedek DNS sunucular\u0131n\u0131n uygulanmas\u0131n\u0131 i\u00e7erir. DNS yedeklili\u011fi, y\u00fck\u00fc birden fazla sunucuya da\u011f\u0131tarak, donan\u0131m ar\u0131zalar\u0131 veya DDoS sald\u0131r\u0131lar\u0131 kar\u015f\u0131s\u0131nda bile kullan\u0131c\u0131lar\u0131n web sitelerine ve \u00e7evrimi\u00e7i hizmetlere kesintisiz olarak eri\u015febilmesini sa\u011flar. Bu makalede, proxy sunucu sa\u011flay\u0131c\u0131s\u0131 OneProxy ile ilgisine \u00f6zel olarak odaklanarak DNS yedeklili\u011finin tarihini, i\u015fleyi\u015fini, t\u00fcrlerini ve gelecekteki beklentilerini inceleyece\u011fiz.<\/p>\n<h2>DNS Yedeklili\u011finin K\u00f6keni ve Erken Bahsi<\/h2>\n<p>DNS yedeklili\u011fi kavram\u0131, 1980&#039;lerde Alan Ad\u0131 Sisteminin (DNS) geli\u015ftirilmesiyle birlikte ortaya \u00e7\u0131kt\u0131. Ba\u015flang\u0131\u00e7ta DNS tek bir sunucuya dayan\u0131yordu ve bu da g\u00fcvenilirlik ve performans a\u00e7\u0131s\u0131ndan \u00f6nemli dezavantajlar sunuyordu. DNS&#039;de yedeklilik ihtiyac\u0131n\u0131n ilk s\u00f6z\u00fc, Kas\u0131m 1983&#039;te yay\u0131nlanan ve tekli ar\u0131za noktalar\u0131n\u0131 azaltmak i\u00e7in da\u011f\u0131t\u0131lm\u0131\u015f bir DNS sisteminin \u00f6nemini vurgulayan ufuk a\u00e7\u0131c\u0131 RFC 882&#039;ye kadar uzanabilir.<\/p>\n<h2>DNS Art\u0131kl\u0131\u011f\u0131n\u0131 Anlamak<\/h2>\n<p>DNS yedeklili\u011fi, genellikle hiyerar\u015fik veya da\u011f\u0131t\u0131lm\u0131\u015f bir mimaride d\u00fczenlenen birden fazla DNS sunucusunun da\u011f\u0131t\u0131lmas\u0131yla sa\u011flan\u0131r. Her DNS sunucusu, alan adlar\u0131n\u0131n IP adresleriyle e\u015flenmesini i\u00e7eren DNS b\u00f6lgesi verilerinin bir kopyas\u0131n\u0131 tutar. Bir kullan\u0131c\u0131n\u0131n cihaz\u0131 bir DNS sorgusu ba\u015flatt\u0131\u011f\u0131nda, yedek DNS sunucular\u0131ndan herhangi birine y\u00f6nlendirilebilir ve bu sunucular daha sonra istenen etki alan\u0131 i\u00e7in uygun IP adresiyle yan\u0131t verir.<\/p>\n<h2>DNS Yedeklili\u011finin \u0130\u00e7 Yap\u0131s\u0131 ve \u00c7al\u0131\u015fmas\u0131<\/h2>\n<p>DNS yedeklili\u011finin i\u00e7 yap\u0131s\u0131, s\u0131ras\u0131yla ana ve ba\u011f\u0131ml\u0131 sunucular olarak da bilinen birincil ve ikincil DNS sunucular\u0131n\u0131n kurulumunu i\u00e7erir. Birincil DNS sunucusu, belirli bir DNS b\u00f6lgesi i\u00e7in yetkilidir ve b\u00f6lge verilerinin ana kopyas\u0131n\u0131 tutar. \u0130kincil DNS sunucular\u0131, b\u00f6lge verilerine ili\u015fkin g\u00fcncellemeleri almak i\u00e7in d\u00fczenli olarak birincil sunucuyla senkronize olur. B\u00f6lge aktar\u0131m\u0131 olarak bilinen bu senkronizasyon i\u015flemi, t\u00fcm ikincil sunucular\u0131n tutarl\u0131 ve g\u00fcncel bilgilere sahip olmas\u0131n\u0131 sa\u011flar.<\/p>\n<p>Bir DNS sorgusu al\u0131nd\u0131\u011f\u0131nda, yedekli DNS sunucular\u0131ndan herhangi biri yak\u0131nl\u0131k, mevcut y\u00fck veya \u00f6nceden belirlenmi\u015f bir rotasyon algoritmas\u0131 gibi fakt\u00f6rlere ba\u011fl\u0131 olarak yan\u0131t verebilir. Bu y\u00fck da\u011f\u0131t\u0131m\u0131 yaln\u0131zca DNS \u00e7\u00f6z\u00fcmleme performans\u0131n\u0131 art\u0131rmakla kalmaz, ayn\u0131 zamanda hata tolerans\u0131 da sa\u011flar. Bir sunucuya eri\u015filemez hale gelirse veya sorunlar ya\u015fan\u0131rsa di\u011fer sunucular yine de gelen DNS sorgular\u0131n\u0131 i\u015fleyebilir.<\/p>\n<h2>DNS Art\u0131kl\u0131\u011f\u0131n\u0131n Temel \u00d6zellikleri<\/h2>\n<p>DNS yedeklili\u011finin temel \u00f6zellikleri a\u015fa\u011f\u0131daki gibi \u00f6zetlenebilir:<\/p>\n<ol>\n<li>\n<p><strong>Y\u00fcksek kullan\u0131labilirlik:<\/strong> DNS yedeklili\u011fi, baz\u0131 sunucular ar\u0131zalansa veya kesintiler ya\u015fansa bile DNS hizmetlerinin eri\u015filebilir kalmas\u0131n\u0131 sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Y\u00fck da\u011f\u0131l\u0131m\u0131:<\/strong> DNS sorgular\u0131n\u0131n birden \u00e7ok sunucuya da\u011f\u0131t\u0131lmas\u0131, tek tek sunucular\u0131n a\u015f\u0131r\u0131 y\u00fcklenmesini \u00f6nleyerek genel performans\u0131n daha iyi olmas\u0131n\u0131 sa\u011flar.<\/p>\n<\/li>\n<li>\n<p><strong>Hata Tolerans\u0131:<\/strong> Yedekli sunucular, y\u00fck devretme yetenekleri sa\u011flayarak donan\u0131m veya yaz\u0131l\u0131m ar\u0131zalar\u0131ndan kaynaklanan hizmet kesintisi riskini azalt\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Co\u011frafi Yedeklilik:<\/strong> DNS yedeklili\u011finin baz\u0131 uygulamalar\u0131 birden fazla co\u011frafi konumu kapsayarak b\u00f6lgesel kesintilere veya a\u011f sorunlar\u0131na kar\u015f\u0131 dayan\u0131kl\u0131l\u0131\u011f\u0131 art\u0131r\u0131r.<\/p>\n<\/li>\n<li>\n<p><strong>Dinamik G\u00fcncellemeler:<\/strong> DNS yedeklili\u011fi, DNS kay\u0131tlar\u0131nda dinamik g\u00fcncellemeleri destekleyerek DNS e\u015flemelerinde ger\u00e7ek zamanl\u0131 de\u011fi\u015fiklikler yap\u0131lmas\u0131na olanak tan\u0131r.<\/p>\n<\/li>\n<\/ol>\n<h2>DNS Art\u0131kl\u0131\u011f\u0131 T\u00fcrleri<\/h2>\n<p>Her biri benzersiz avantajlar sunan \u00e7e\u015fitli DNS yedeklili\u011fi t\u00fcrleri vard\u0131r. A\u015fa\u011f\u0131da yayg\u0131n DNS yedeklili\u011fi t\u00fcrlerinin bir listesi bulunmaktad\u0131r:<\/p>\n<table>\n<thead>\n<tr>\n<th>DNS Yedekleme T\u00fcr\u00fc<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Birincil ikincil<\/td>\n<td>Bu kurulumda, bir birincil DNS sunucusu b\u00f6lge verilerinin ana kopyas\u0131n\u0131 tutarken, birden \u00e7ok ikincil sunucu birincil sunucuyla e\u015fitlenir.<\/td>\n<\/tr>\n<tr>\n<td>Gizli Usta<\/td>\n<td>Gizli ana sunucu, genel olarak eri\u015filemeyen bir birincil DNS sunucusudur ve birincil sunucuya do\u011frudan sald\u0131r\u0131 riskini azalt\u0131r. Verileri halka a\u00e7\u0131k ikincil sunuculara kopyalar.<\/td>\n<\/tr>\n<tr>\n<td>Usta-Usta<\/td>\n<td>Master-Master yedeklili\u011fi birden fazla birincil sunucu kullan\u0131r ve her sunucu b\u00f6lge verilerine y\u00f6nelik g\u00fcncellemeleri kabul edebilir, bu da DNS kay\u0131tlar\u0131n\u0131n y\u00f6netilmesinde daha fazla esneklik sa\u011flar.<\/td>\n<\/tr>\n<tr>\n<td>Her noktaya yay\u0131n<\/td>\n<td>Anycast yedeklili\u011fi, ayn\u0131 DNS sunucular\u0131n\u0131n \u00e7e\u015fitli konumlara da\u011f\u0131t\u0131lmas\u0131n\u0131 i\u00e7erir. DNS sorgular\u0131 m\u00fcmk\u00fcn olan en yak\u0131n sunucuya y\u00f6nlendirilerek yan\u0131t s\u00fcreleri optimize edilir ve DDoS sald\u0131r\u0131lar\u0131 azalt\u0131l\u0131r.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>DNS Yedeklili\u011fini Kullanma: Zorluklar ve \u00c7\u00f6z\u00fcmler<\/h2>\n<p>DNS yedeklili\u011fi bir dizi avantaj sunar, ancak uygulanmas\u0131nda zorluklar da vard\u0131r. Baz\u0131 yayg\u0131n zorluklar \u015funlard\u0131r:<\/p>\n<ol>\n<li>\n<p><strong>Senkronizasyon Gecikmeleri:<\/strong> \u0130kincil sunucular\u0131 birincil sunucuyla senkronize tutmak, g\u00fcncellemelerin yay\u0131lmas\u0131nda gecikmelere neden olabilir.<\/p>\n<\/li>\n<li>\n<p><strong>DNS \u00d6nbellek Tutarl\u0131l\u0131\u011f\u0131:<\/strong> \u0130stemci cihazlar\u0131nda ve ara \u00e7\u00f6z\u00fcmleyicilerde \u00f6nbelle\u011fe al\u0131nm\u0131\u015f DNS verileri, DNS kay\u0131tlar\u0131 de\u011fi\u015fti\u011finde tutars\u0131zl\u0131klara neden olabilir.<\/p>\n<\/li>\n<li>\n<p><strong>Artan Karma\u015f\u0131kl\u0131k:<\/strong> Birden fazla DNS sunucusunu y\u00f6netmek dikkatli planlama ve y\u00f6netim gerektirir.<\/p>\n<\/li>\n<\/ol>\n<p>Bu zorluklar\u0131n \u00fcstesinden gelmek i\u00e7in \u00e7\u00f6z\u00fcmler aras\u0131nda, \u00f6nbelle\u011fe alma sorunlar\u0131n\u0131 en aza indirmek amac\u0131yla DNS kay\u0131tlar\u0131 i\u00e7in daha k\u0131sa TTL (Ya\u015fam S\u00fcresi) de\u011ferlerinin uygulanmas\u0131, DNS yap\u0131land\u0131rmas\u0131n\u0131 y\u00f6netmek i\u00e7in otomasyon ara\u00e7lar\u0131n\u0131n kullan\u0131lmas\u0131 ve DNS sunucular\u0131n\u0131n sa\u011fl\u0131\u011f\u0131n\u0131n ve performans\u0131n\u0131n dikkatli bir \u015fekilde izlenmesi yer al\u0131r.<\/p>\n<h2>Ana \u00d6zellikler ve Kar\u015f\u0131la\u015ft\u0131rmalar<\/h2>\n<p>DNS yedeklili\u011finin benzer kavramlarla kar\u015f\u0131la\u015ft\u0131r\u0131lmas\u0131:<\/p>\n<table>\n<thead>\n<tr>\n<th>Konsept<\/th>\n<th>Tan\u0131m<\/th>\n<\/tr>\n<\/thead>\n<tbody>\n<tr>\n<td>Y\u00fck dengeleme<\/td>\n<td>Y\u00fck dengeleme, kaynak kullan\u0131m\u0131n\u0131 optimize etmek ve a\u015f\u0131r\u0131 y\u00fcklemeyi \u00f6nlemek i\u00e7in a\u011f trafi\u011fini birden fazla sunucuya da\u011f\u0131tmay\u0131 i\u00e7erir. DNS yedeklili\u011fi, sorgular\u0131 farkl\u0131 sunuculara y\u00f6nlendirerek y\u00fck dengelemeyi destekleyebilir.<\/td>\n<\/tr>\n<tr>\n<td>Y\u00fck devretme<\/td>\n<td>Failover, birincil sistemin ar\u0131zalanmas\u0131 durumunda yedekli sistemlere ge\u00e7i\u015f i\u015flemidir. DNS yedeklili\u011fi, birincil sunucular kullan\u0131lamaz hale geldi\u011finde alternatif DNS sunucular\u0131n\u0131n istekleri i\u015fleyebilmesini sa\u011flayarak y\u00fck devretmeyi kolayla\u015ft\u0131rabilir.<\/td>\n<\/tr>\n<tr>\n<td>Y\u00fcksek kullan\u0131labilirlik<\/td>\n<td>Y\u00fcksek kullan\u0131labilirlik, s\u00fcrekli hizmet \u00e7al\u0131\u015fma s\u00fcresinin korunmas\u0131na odaklan\u0131r. DNS yedeklili\u011fi, DNS hizmetlerini yedekli sunuculara da\u011f\u0131tarak tek ar\u0131za noktalar\u0131n\u0131 \u00f6nleyerek y\u00fcksek kullan\u0131labilirli\u011fe katk\u0131da bulunur.<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<h2>Perspektifler ve Gelece\u011fin Teknolojileri<\/h2>\n<p>\u0130leriye bakt\u0131\u011f\u0131m\u0131zda, DNS teknolojilerindeki geli\u015fmelerin DNS yedeklili\u011fini daha da art\u0131rmas\u0131 muhtemeldir. Gelecekteki potansiyel geli\u015fmelerden baz\u0131lar\u0131 \u015funlard\u0131r:<\/p>\n<ol>\n<li>\n<p><strong>HTTPS \u00fczerinden DNS (DoH) ve TLS \u00fczerinden DNS (DoT):<\/strong> \u015eifrelenmi\u015f DNS protokolleri, DNS ileti\u015fimlerinde g\u00fcvenli\u011fi ve gizlili\u011fi iyile\u015ftirerek bu g\u00fcvenli kanallar \u00fczerindeki DNS yedeklili\u011fini daha sa\u011flam hale getirebilir.<\/p>\n<\/li>\n<li>\n<p><strong>IPv6&#039;n\u0131n Kabul\u00fc:<\/strong> D\u00fcnya IPv6&#039;ya ge\u00e7erken, DNS yedeklili\u011finin IPv6 kay\u0131tlar\u0131n\u0131 ve adres \u00e7\u00f6z\u00fcmlemesini desteklemesi gerekecektir.<\/p>\n<\/li>\n<li>\n<p><strong>Blockchain tabanl\u0131 DNS:<\/strong> Blockchain tabanl\u0131 DNS sistemleriyle yap\u0131lan deneyler, merkezi olmayan, y\u00fcksek oranda yedekli DNS mimarilerine yol a\u00e7abilir.<\/p>\n<\/li>\n<\/ol>\n<h2>DNS Yedeklili\u011fi ve Proxy Sunucular\u0131<\/h2>\n<p>Proxy sunucular\u0131 a\u011f g\u00fcvenli\u011fi, performans ve anonimlik a\u00e7\u0131s\u0131ndan \u00e7ok \u00f6nemli bir rol oynar. Proxy sunucular, DNS yedeklili\u011fiyle birlikte kullan\u0131ld\u0131\u011f\u0131nda g\u00fcvenilirliklerini ve hata toleranslar\u0131n\u0131 daha da art\u0131rabilir. DNS sorgular\u0131n\u0131n proxy sunucuya ula\u015fmadan \u00f6nce birden fazla yedekli DNS sunucusu \u00fczerinden y\u00f6nlendirilmesiyle, DNS ile ilgili olas\u0131 sorunlar en aza indirilir. Ek olarak proxy sunucular, sorunsuz \u00e7al\u0131\u015fmay\u0131 sa\u011flamak i\u00e7in y\u00fck dengeleme ve y\u00fck devretme gibi kendi yedeklilik mekanizmalar\u0131n\u0131 uygulayabilir.<\/p>\n<h2>\u0130lgili Ba\u011flant\u0131lar<\/h2>\n<p>DNS yedeklili\u011fi hakk\u0131nda daha fazla bilgi i\u00e7in a\u015fa\u011f\u0131daki kaynaklar\u0131 incelemeyi d\u00fc\u015f\u00fcn\u00fcn:<\/p>\n<ul>\n<li><a href=\"https:\/\/www.cloudflare.com\/learning\/dns\/glossary\/dns-redundancy\/\" target=\"_new\" rel=\"noopener nofollow\">DNS Yedeklili\u011fine Giri\u015f<\/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.apnic.net\/community\/security\/dnssec\/dns-resilience-and-redundancy\/\" target=\"_new\" rel=\"noopener nofollow\">DNS Dayan\u0131kl\u0131l\u0131\u011f\u0131 ve Art\u0131kl\u0131k<\/a><\/li>\n<\/ul>\n<p>Sonu\u00e7 olarak DNS yedeklili\u011fi, modern internet altyap\u0131s\u0131n\u0131n kritik bir y\u00f6n\u00fc olup g\u00fcvenilirlik, hata tolerans\u0131 ve geli\u015fmi\u015f performans sa\u011flar. OneProxy, ge\u00e7mi\u015fini, \u00e7al\u0131\u015fma prensiplerini, t\u00fcrlerini ve gelecekteki potansiyel geli\u015fmelerini anlayarak kullan\u0131c\u0131lar\u0131na sa\u011flam ve g\u00fcvenilir bir hizmet sunarak deneyimlerini ve memnuniyetlerini art\u0131rabilir.<\/p>","protected":false},"featured_media":476928,"menu_order":0,"template":"","meta":{"_acf_changed":false,"content-type":"","inline_featured_image":false,"footnotes":""},"class_list":["post-476927","wiki","type-wiki","status-publish","has-post-thumbnail","hentry"],"acf":{"faq_title":"Frequently Asked Questions about <mark>DNS Redundancy: Ensuring Resilience and Reliability<\/mark>","faq_items":[{"question":"What is DNS redundancy?","answer":"<p>DNS redundancy is a crucial aspect of internet infrastructure that involves deploying multiple redundant DNS servers. It ensures high availability and fault tolerance by distributing domain name resolution queries across these servers. This redundancy prevents service disruptions and improves overall performance.<\/p>"},{"question":"How did DNS redundancy originate?","answer":"<p>The concept of DNS redundancy emerged alongside the development of the Domain Name System (DNS) in the 1980s. It was first mentioned in RFC 882 in November 1983, highlighting the need for a distributed DNS system to mitigate single points of failure.<\/p>"},{"question":"How does DNS redundancy work?","answer":"<p>DNS redundancy works by setting up primary and secondary DNS servers. The primary server holds the master copy of the DNS zone data, while secondary servers regularly synchronize with it to stay up-to-date. When a DNS query is received, any of the redundant servers can respond, distributing the load and providing fault tolerance.<\/p>"},{"question":"What are the key features of DNS redundancy?","answer":"<p>The key features of DNS redundancy include high availability, load distribution, fault tolerance, geo-redundancy, and support for dynamic updates. These features ensure a stable and resilient DNS service.<\/p>"},{"question":"What types of DNS redundancy exist?","answer":"<p>There are several types of DNS redundancy, including:<\/p><ul><li>Primary-Secondary: One primary server with multiple secondary servers syncing with it.<\/li><li>Hidden Master: A non-public primary server replicating data to public-facing secondary servers.<\/li><li>Master-Master: Multiple primary servers with the ability to accept updates.<\/li><li>Anycast: Deploying identical DNS servers in different locations, directing queries to the nearest available server.<\/li><\/ul>"},{"question":"How is DNS redundancy used, and what challenges does it face?","answer":"<p>DNS redundancy is used to ensure continuous service availability. However, challenges such as synchronization delays and DNS cache consistency may arise. To address these, shorter TTL values and automation tools can be employed.<\/p>"},{"question":"How does DNS redundancy compare to load balancing and failover?","answer":"<p>DNS redundancy complements load balancing and failover mechanisms. While load balancing distributes network traffic across servers, DNS redundancy ensures redundancy in DNS resolution. Failover switches to redundant systems when the primary fails, and DNS redundancy supports this by providing alternate servers to handle queries.<\/p>"},{"question":"What are the future technologies related to DNS redundancy?","answer":"<p>Future technologies may include DNS over HTTPS (DoH) and DNS over TLS (DoT) for encrypted DNS communications, IPv6 support, and exploration of blockchain-based DNS systems for decentralized redundancy.<\/p>"},{"question":"How can proxy servers benefit from DNS redundancy?","answer":"<p>Proxy servers can enhance their reliability and performance by leveraging DNS redundancy. Integrating redundant DNS servers before reaching the proxy ensures minimized DNS-related issues, while proxy servers themselves can implement load balancing and failover mechanisms for added reliability.<\/p>"},{"question":"Where can I find more information about DNS redundancy?","answer":"<p>For more in-depth information about DNS redundancy, you can explore the following resources:<\/p><ul><li><a href=\"https:\/\/www.cloudflare.com\/learning\/dns\/glossary\/dns-redundancy\/\" target=\"_new\">Introduction to DNS Redundancy<\/a><\/li><li><a href=\"https:\/\/tools.ietf.org\/html\/rfc1035\" target=\"_new\">RFC 1035 - Domain Names - Implementation and Specification<\/a><\/li><li><a href=\"https:\/\/www.apnic.net\/community\/security\/dnssec\/dns-resilience-and-redundancy\/\" target=\"_new\">DNS Resilience and Redundancy<\/a><\/li><\/ul>"}]},"_links":{"self":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/wiki\/476927","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\/476927\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media\/476928"}],"wp:attachment":[{"href":"https:\/\/oneproxy.pro\/tr\/wp-json\/wp\/v2\/media?parent=476927"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}