{"id":12390,"date":"2025-09-09T08:43:20","date_gmt":"2025-09-09T06:43:20","guid":{"rendered":"https:\/\/webhosting.de\/hetzner-dns-konfiguration-leitfaden-setup-power\/"},"modified":"2025-09-09T08:43:20","modified_gmt":"2025-09-09T06:43:20","slug":"hetzner-dns-configuration-guide-setup-power","status":"publish","type":"post","link":"https:\/\/webhosting.de\/en\/hetzner-dns-konfiguration-leitfaden-setup-power\/","title":{"rendered":"Set Hetzner DNS settings correctly - example configuration with hetzner dns configuration"},"content":{"rendered":"<p><strong>Hetzner DNS configuration<\/strong> so that your website, subdomains and mail work without detours and changes take effect quickly. In this guide, I show you the necessary settings in the Hetzner DNS, a tried-and-tested example configuration and practical test methods so that you can avoid errors early on and keep your zone clean.<\/p>\n\n<h2>Key points<\/h2>\n<p>The following key points will give you a quick overview of what is important for a reliable DNS zone.<\/p>\n<ul>\n  <li><strong>Nameserver<\/strong> enter correctly with the registrar<\/li>\n  <li><strong>A\/AAAA<\/strong> for Web, <strong>MX\/TXT<\/strong> for mail<\/li>\n  <li><strong>TTL<\/strong> Select appropriately and wait for propagation<\/li>\n  <li><strong>SPF\/DKIM<\/strong> against spam and spoofing<\/li>\n  <li><strong>Monitoring<\/strong> and tests after changes<\/li>\n<\/ul>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img fetchpriority=\"high\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetzner-dns-konfiguration-8271.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>DNS in a nutshell: what you really need<\/h2>\n\n<p>I assign a domain via <strong>Records<\/strong> specific destinations so that browsers and mail servers can find my services. A <strong>A-Record<\/strong> points to an IPv4 address, an AAAA to IPv6, and an MX defines the delivery of emails. A CNAME forms an alias that points to a different name, while TXT contains information for <strong>SPF<\/strong> or verifications. A clean baseline consists of A\/AAAA for the main domain, CNAME for www, MX for mail and an SPF-TXT. This way I keep the zone clear, quickly maintainable and open for later extensions.<\/p>\n\n<h2>Add domain to the Hetzner DNS console<\/h2>\n\n<p>In the DNS console, I first create a new <strong>Zone<\/strong> and check that the spelling of the domain is exactly right. I then activate the manual maintenance of <strong>Records<\/strong>so that I can create and change specific entries. Tip: I make a note of IP addresses and mail destinations in advance so that I can enter everything without interruption. This way I avoid typing errors and set the entries in a calm order. As soon as the zone is ready, I plan the change of name servers and the subsequent checks.<\/p>\n\n<h2>Enter the name server correctly with the registrar<\/h2>\n\n<p>After creating the zone, I enter the <strong>Nameserver<\/strong> from Hetzner so that the administration runs centrally in the DNS console. The usual entries are <strong>ns1.first-ns.de<\/strong>, <em>robotns2.second-ns.de<\/em> and <em>robotns3.second-ns.com<\/em>. For .de or .at domains, I set up my own name servers with <strong>Glue-Records<\/strong>so that the references and IPs are stored. If you have never done this before, you can find the individual steps in the guide to <a href=\"https:\/\/webhosting.de\/en\/set-up-your-own-nameserver-dns-zones-domain-glue-records-guide-power\/\">Set up glue records<\/a>. I then take some time for the changeover, because the update can arrive at different speeds around the world.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetznerdnsmeeting4821.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Example configuration: Making the website and e-mail executable<\/h2>\n\n<p>For a typical web presence I use a <strong>A-Record<\/strong> for the root domain, a CNAME for www and suitable mail records. An SPF-TXT prevents external servers from sending e-mails in the name of the domain. Optionally, I add an AAAA record if the web server <strong>IPv6<\/strong> provides. For external mail services such as ForwardMX, I adapt the MX and store their specifications. The following table shows a solid starting point for many setups.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th><strong>Name<\/strong><\/th>\n      <th><strong>Type<\/strong><\/th>\n      <th><strong>Value<\/strong><\/th>\n      <th><strong>Note<\/strong><\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>@<\/td>\n      <td>A<\/td>\n      <td>195.201.210.43<\/td>\n      <td>Web server IPv4<\/td>\n    <\/tr>\n    <tr>\n      <td>@<\/td>\n      <td>AAAA<\/td>\n      <td>Optional: 2a01:4f8:xxxx:xxxx::1<\/td>\n      <td>Web server IPv6<\/td>\n    <\/tr>\n    <tr>\n      <td>www<\/td>\n      <td>CNAME<\/td>\n      <td>@<\/td>\n      <td>Alias on root<\/td>\n    <\/tr>\n    <tr>\n      <td>@<\/td>\n      <td>MX<\/td>\n      <td>mx1.forwardmx.net<\/td>\n      <td>Priority 10<\/td>\n    <\/tr>\n    <tr>\n      <td>@<\/td>\n      <td>TXT<\/td>\n      <td>\"v=spf1 include:_spf.forwardmx.net -all\"<\/td>\n      <td>SPF against spoofing<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<h2>Activate DNSSEC and set DS record<\/h2>\n<p>If manipulation security is important to me, I activate <strong>DNSSEC<\/strong> for the zone. In the Hetzner console, I generate signature keys for this and then receive the necessary <strong>DS data<\/strong>which I deposit with the registrar. I check that the algorithm and digest have been transferred correctly. Then I wait until the chain from the registrar to the zone validates properly. Before larger key rotations, I lower the TTL and plan a time window so that resolvers see new signatures in good time. Important: If an error occurs during the change, validations fail for recipients - I therefore have a rollback ready (do not delete old keys too early) and test with validation resolvers.<\/p>\n\n<h2>Set TTL correctly and understand propagation<\/h2>\n\n<p>The <strong>TTL<\/strong> determines how long resolvers cache an entry. For conversions, I choose a short <strong>TTL<\/strong> (e.g. 300 seconds) so that changes become visible quickly. After the final setup, I increase the values again in order to save requests and achieve uniform resolution. Those who deploy frequently like to stick with 600-1200 seconds, those who rarely change use 3600-14400. A practical overview of the decision is provided by my look at the <a href=\"https:\/\/webhosting.de\/en\/dns-ttl-performance-comparison-optimal-flux\/\">Optimal TTL selection<\/a>.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetzner-dns-einstellungen-guide-4829.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Apex domain, CAA and certificates under control<\/h2>\n<p>For SaaS targets on <strong>Apex zone<\/strong> I remember that <em>CNAME<\/em> is not allowed on @. I therefore use the provider's A\/AAAA or set a redirect to www at web server level. For the certificate assignment I control with <strong>CAA Records<\/strong>which CAs are allowed to issue certificates. For example, I only maintain the CA that I actually use and optionally add a mail address for reports. If I change the CA, I briefly increase the TTL and update CAA before issuing. For wildcards via ACME DNS-01, I make sure that TXT records under <em>_acme-challenge<\/em> are quickly set and automatically cleaned up so that no old challenges are left behind.<\/p>\n\n<h2>Create subdomains and services cleanly<\/h2>\n\n<p>For each subdomain I create a suitable <strong>A<\/strong>- or <strong>CNAME<\/strong>-record, depending on whether the subdomain points directly to an IP or to a name. Example: blog.example.de as A-record to the blog VM, cdn.example.de as CNAME to a CDN name. For APIs, I make a strict distinction between internal and public names to avoid risks. Standardized names such as api, app, img help with maintenance and monitoring. This way, I keep the zone structured and can clearly assign changes.<\/p>\n\n<h2>Wildcards, SRV and special record types<\/h2>\n<p>I use <strong>Wildcard records<\/strong> (*.example.de), for example for multi-client capable setups. I make sure that exact entries always take precedence over wildcards. For services such as SIP, Matrix or Autodiscover, I create <strong>SRV-Records<\/strong> and check the format and priorities. <strong>TXT records<\/strong> with long content (e.g. 2048-bit DKIM) I split into several quote segments so that parsers can merge them correctly. I avoid multiple SPF records and combine entries into a valid SPF to avoid breaking the lookup limit.<\/p>\n\n<h2>Reliable e-mail delivery: SPF, DKIM and DMARC<\/h2>\n\n<p>For trustworthy e-mail, I use the <strong>MX<\/strong> a clean SPF-TXT that covers my sending systems. I also activate <strong>DKIM<\/strong> at the mail service used and publish the DKIM selector as TXT under selector._domainkey. I use DMARC to define how recipients handle mails that do not pass SPF\/DKIM. I often start with \"p=none\", evaluate reports and later switch to \"quarantine\" or \"reject\". This sequence reduces risks and gradually increases delivery quality.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetzner_dns_config_8452.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Deepening SPF\/DKIM\/DMARC in practice<\/h2>\n<p>I keep SPF as lean as possible: only necessary <em>include<\/em>-mechanisms and never more than one SPF per hostname. To comply with the 10 DNS lookups limit, I reduce chains or use IP4\/IP6 mechanisms if they are stable. For <strong>DKIM rotation<\/strong> I run two active selectors (old\/new), publish the new key, switch the mail service and only delete the old one after a few days. With <strong>DMARC<\/strong> I initially set reporting addresses (rua\/ruf) and check alignment (aspf\/adkim). For subdomains I can use <em>sp=<\/em> define a separate policy if they send separately. This way I react to real traffic data instead of assumptions.<\/p>\n\n<h2>Reverse DNS (PTR) for clean mail delivery<\/h2>\n<p>In addition to MX, SPF and DKIM, I set up <strong>Reverse DNS<\/strong> (PTR) for outgoing mail servers. The PTR of the IP points to a host name, which in turn resolves correctly to the same IP via A\/AAAA (<em>Forward\/reverse match<\/em>). I set PTR per IP directly with the IP owner (e.g. in the server interface) - not in the zone management of the domain. For IPv6 I use the nibble format. A suitable PTR reduces spam classifications and helps with reputation. If mail runs via an external service, I leave its PTR as it is and avoid mixed sender sources without SPF customization.<\/p>\n\n<h2>Typical errors and quick solutions<\/h2>\n\n<p>If a domain does not resolve, I check first <strong>TTL<\/strong>name server entries and the correct spelling of the records. The second look goes to the <strong>Propagation<\/strong>Some resolvers cache longer, especially after TTL increases. I compare the resolution using different DNS checkers to identify regional differences. In the event of local problems, I temporarily switch to public resolvers such as 1.1.1.1 or 8.8.8.8. If the error only occurs in internal networks, I check internal resolvers and rules in containers, Kubernetes or CoreDNS configurations.<\/p>\n\n<h2>Test methods: dig, nslookup and end-to-end<\/h2>\n<p>I don't just test records, but the entire path:<\/p>\n<ul>\n  <li><strong>dig<\/strong> A\/AAAA\/CNAME\/MX\/TXT: Check responses, TTL and authority<\/li>\n  <li><strong>dig +trace<\/strong>See delegation chain and name server behavior<\/li>\n  <li><strong>SMTP tests<\/strong>Check HELO\/EHLO, TLS and banner<\/li>\n  <li><strong>HTTPS real<\/strong>Certificate chain, host name, redirects<\/li>\n<\/ul>\n<p>In this way, I also detect errors that are not visible in pure DNS responses, such as incorrect VirtualHost mappings or expiring certificates. After making changes, I wait at least one TTL before drawing final conclusions.<\/p>\n\n<h2>Work efficiently with the Hetzner console<\/h2>\n\n<p>I group together related <strong>Entries<\/strong> time, set a short TTL before making major changes and then publish everything in one go. Before saving, I check again <strong>MX<\/strong>-priorities, SPF syntax and the target IP of the A record. For server administration and processes, the compact instructions at <a href=\"https:\/\/webhosting.de\/en\/hetzner-robot-surface-server-administration-tips-guide-comparison-power\/\">Hetzner Robot tips<\/a>. After deployments, I test http, https and mail with real requests, not just via ping. This allows me to detect errors that pure DNS queries do not show.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetzner_dns_setup_arbeitsplatz_3842.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Automation: API, templates and ACME<\/h2>\n<p>I save time through automation. For regular deployments, I use the <strong>API<\/strong> of the DNS console to create, change or delete records. I work with templates for recurring patterns (e.g. Web + Mail + DMARC) and only insert project-specific values. For Let's Encrypt DNS-01, I include an automated TXT record writer and integrate it into the renewal workflow. Important: I treat API tokens like passwords, assign them to specific projects and revoke access when they are no longer needed.<\/p>\n\n<h2>Advanced setups: Split-Horizon, CDN and ACME<\/h2>\n\n<p>I separate internal and external users if required <strong>DNS<\/strong>-views so that the internal app points to private IPs and visitors to public destinations. If I use a <strong>CDN<\/strong>I refer subdomains to the CDN name via CNAME and activate TLS there. For automatic certificates via ACME\/Let's Encrypt, I optionally set DNS-01 challenges via TXT if HTTP-01 does not match. Automation is important here so that renewals are carried out in good time. Logs and notifications help to detect failures in good time.<\/p>\n\n<h2>Performance and availability patterns<\/h2>\n<p>I increase availability with simple means: Several <strong>A\/AAAA records<\/strong> (round robin) share load without additional services, provided that the backends are stateless or share sessions. During maintenance, I temporarily remove individual IPs and then raise the entry again. A TTL endurance run that is too short can put a strain on resolvers; I find a middle ground between response speed and cache hit rate. I set clear processes for failovers without health checks: In the event of a fault, I swap entries, actively monitor and reset them after recovery.<\/p>\n\n<h2>Safety and zone hygiene<\/h2>\n<p>I deactivate unnecessary <strong>Zone transfers<\/strong> (AXFR) and publish only the <strong>NS<\/strong>that are truly authoritative. I regularly delete old or orphaned subdomains so that no shadow surfaces are created. For IDNs, I check the <strong>Punycode<\/strong>-spelling to avoid typos and special character errors. Role-based access in the console ensures that only the right people change zones. And quite pragmatically: I briefly document changes in the team tool - this significantly reduces queries during operation.<\/p>\n\n\n<figure class=\"wp-block-image size-full is-resized\">\n  <img loading=\"lazy\" decoding=\"async\" src=\"https:\/\/webhosting.de\/wp-content\/uploads\/2025\/09\/hetzner-dns-setup-4837.webp\" alt=\"\" width=\"1536\" height=\"1024\"\/>\n<\/figure>\n\n\n<h2>Migration and rollback strategy<\/h2>\n<p>Before a move, I lower the TTL (24-48 hours beforehand), mirror all <strong>Records<\/strong> into the new zone and test resolution directly via the new name servers. Only when everything is correct do I set the <strong>Nameserver<\/strong> at the registrar. After delegation, I monitor traffic and errors. If something goes wrong, I roll back in a controlled manner or correct individual entries. For DNSSEC migrations, I plan particularly conservatively and leave the old signature chain in place until the new one is securely in place. Finally, I reset the TTL to production-ready values.<\/p>\n\n<h2>Brief provider comparison for performance and flexibility<\/h2>\n\n<p>Performance, functions and <strong>DNS freedom<\/strong> decide how flexibly I roll out projects. In practice, the large hosters deliver solid <strong>Response times<\/strong>but differ in terms of operation, features and support. I evaluate the selection according to performance, range of functions, help quality and DNS options. The following overview shows a condensed picture that I can use to make decisions. In the end, it's what my project really needs that counts, not the biggest feature list.<\/p>\n\n<table>\n  <thead>\n    <tr>\n      <th><strong>Provider<\/strong><\/th>\n      <th><strong>Performance<\/strong><\/th>\n      <th><strong>Scope of functions<\/strong><\/th>\n      <th><strong>Support<\/strong><\/th>\n      <th><strong>DNS flexibility<\/strong><\/th>\n      <th><strong>Ranking<\/strong><\/th>\n    <\/tr>\n  <\/thead>\n  <tbody>\n    <tr>\n      <td>webhoster.de<\/td>\n      <td>High<\/td>\n      <td>Very extensive<\/td>\n      <td>Top<\/td>\n      <td>Maximum<\/td>\n      <td>1<\/td>\n    <\/tr>\n    <tr>\n      <td>Hetzner<\/td>\n      <td>High<\/td>\n      <td>Extensive<\/td>\n      <td>Good<\/td>\n      <td>High<\/td>\n      <td>2<\/td>\n    <\/tr>\n    <tr>\n      <td>Contabo<\/td>\n      <td>Medium<\/td>\n      <td>Standard<\/td>\n      <td>O. K.<\/td>\n      <td>Medium<\/td>\n      <td>3<\/td>\n    <\/tr>\n  <\/tbody>\n<\/table>\n\n<h2>Briefly summarized<\/h2>\n\n<p>I set a <strong>Hetzner DNS<\/strong>-zone in a structured manner: Create zone, enter name server with registrar, set core records for web and mail, then test. With suitable <strong>TTL<\/strong> I shorten changeover times and increase again after completion for less load. SPF, DKIM and DMARC strengthen delivery and protect the domain against misuse. I keep subdomains consistent and separate internal from public destinations. With this sample configuration and the everyday checks, your hetzner dns configuration remains reliable, fast and easy to maintain.<\/p>","protected":false},"excerpt":{"rendered":"<p>Professional guide to hetzner dns configuration: How to set up DNS, name servers and MX records correctly.<\/p>","protected":false},"author":1,"featured_media":12383,"comment_status":"","ping_status":"","sticky":false,"template":"","format":"standard","meta":{"_acf_changed":false,"_crdt_document":"","inline_featured_image":false,"footnotes":""},"categories":[674],"tags":[],"class_list":["post-12390","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-web_hosting"],"acf":[],"_wp_attached_file":null,"_wp_attachment_metadata":null,"litespeed-optimize-size":null,"litespeed-optimize-set":null,"_elementor_source_image_hash":null,"_wp_attachment_image_alt":null,"stockpack_author_name":null,"stockpack_author_url":null,"stockpack_provider":null,"stockpack_image_url":null,"stockpack_license":null,"stockpack_license_url":null,"stockpack_modification":null,"color":null,"original_id":null,"original_url":null,"original_link":null,"unsplash_location":null,"unsplash_sponsor":null,"unsplash_exif":null,"unsplash_attachment_metadata":null,"_elementor_is_screenshot":null,"surfer_file_name":null,"surfer_file_original_url":null,"envato_tk_source_kit":null,"envato_tk_source_index":null,"envato_tk_manifest":null,"envato_tk_folder_name":null,"envato_tk_builder":null,"envato_elements_download_event":null,"_menu_item_type":null,"_menu_item_menu_item_parent":null,"_menu_item_object_id":null,"_menu_item_object":null,"_menu_item_target":null,"_menu_item_classes":null,"_menu_item_xfn":null,"_menu_item_url":null,"_trp_menu_languages":null,"rank_math_primary_category":null,"rank_math_title":null,"inline_featured_image":null,"_yoast_wpseo_primary_category":null,"rank_math_schema_blogposting":null,"rank_math_schema_videoobject":null,"_oembed_049c719bc4a9f89deaead66a7da9fddc":null,"_oembed_time_049c719bc4a9f89deaead66a7da9fddc":null,"_yoast_wpseo_focuskw":null,"_yoast_wpseo_linkdex":null,"_oembed_27e3473bf8bec795fbeb3a9d38489348":null,"_oembed_c3b0f6959478faf92a1f343d8f96b19e":null,"_trp_translated_slug_en_us":null,"_wp_desired_post_slug":null,"_yoast_wpseo_title":null,"tldname":null,"tldpreis":null,"tldrubrik":null,"tldpolicylink":null,"tldsize":null,"tldregistrierungsdauer":null,"tldtransfer":null,"tldwhoisprivacy":null,"tldregistrarchange":null,"tldregistrantchange":null,"tldwhoisupdate":null,"tldnameserverupdate":null,"tlddeletesofort":null,"tlddeleteexpire":null,"tldumlaute":null,"tldrestore":null,"tldsubcategory":null,"tldbildname":null,"tldbildurl":null,"tldclean":null,"tldcategory":null,"tldpolicy":null,"tldbesonderheiten":null,"tld_bedeutung":null,"_oembed_d167040d816d8f94c072940c8009f5f8":null,"_oembed_b0a0fa59ef14f8870da2c63f2027d064":null,"_oembed_4792fa4dfb2a8f09ab950a73b7f313ba":null,"_oembed_33ceb1fe54a8ab775d9410abf699878d":null,"_oembed_fd7014d14d919b45ec004937c0db9335":null,"_oembed_21a029d076783ec3e8042698c351bd7e":null,"_oembed_be5ea8a0c7b18e658f08cc571a909452":null,"_oembed_a9ca7a298b19f9b48ec5914e010294d2":null,"_oembed_f8db6b27d08a2bb1f920e7647808899a":null,"_oembed_168ebde5096e77d8a89326519af9e022":null,"_oembed_cdb76f1b345b42743edfe25481b6f98f":null,"_oembed_87b0613611ae54e86e8864265404b0a1":null,"_oembed_27aa0e5cf3f1bb4bc416a4641a5ac273":null,"_oembed_time_27aa0e5cf3f1bb4bc416a4641a5ac273":null,"_tldname":null,"_tldclean":null,"_tldpreis":null,"_tldcategory":null,"_tldsubcategory":null,"_tldpolicy":null,"_tldpolicylink":null,"_tldsize":null,"_tldregistrierungsdauer":null,"_tldtransfer":null,"_tldwhoisprivacy":null,"_tldregistrarchange":null,"_tldregistrantchange":null,"_tldwhoisupdate":null,"_tldnameserverupdate":null,"_tlddeletesofort":null,"_tlddeleteexpire":null,"_tldumlaute":null,"_tldrestore":null,"_tldbildname":null,"_tldbildurl":null,"_tld_bedeutung":null,"_tldbesonderheiten":null,"_oembed_ad96e4112edb9f8ffa35731d4098bc6b":null,"_oembed_8357e2b8a2575c74ed5978f262a10126":null,"_oembed_3d5fea5103dd0d22ec5d6a33eff7f863":null,"_eael_widget_elements":null,"_oembed_0d8a206f09633e3d62b95a15a4dd0487":null,"_oembed_time_0d8a206f09633e3d62b95a15a4dd0487":null,"_aioseo_description":null,"_eb_attr":null,"_eb_data_table":null,"_oembed_819a879e7da16dd629cfd15a97334c8a":null,"_oembed_time_819a879e7da16dd629cfd15a97334c8a":null,"_acf_changed":null,"_wpcode_auto_insert":null,"_edit_last":null,"_edit_lock":null,"_oembed_e7b913c6c84084ed9702cb4feb012ddd":null,"_oembed_bfde9e10f59a17b85fc8917fa7edf782":null,"_oembed_time_bfde9e10f59a17b85fc8917fa7edf782":null,"_oembed_03514b67990db061d7c4672de26dc514":null,"_oembed_time_03514b67990db061d7c4672de26dc514":null,"rank_math_news_sitemap_robots":null,"rank_math_robots":null,"_eael_post_view_count":"4039","_trp_automatically_translated_slug_ru_ru":null,"_trp_automatically_translated_slug_et":null,"_trp_automatically_translated_slug_lv":null,"_trp_automatically_translated_slug_fr_fr":null,"_trp_automatically_translated_slug_en_us":null,"_wp_old_slug":null,"_trp_automatically_translated_slug_da_dk":null,"_trp_automatically_translated_slug_pl_pl":null,"_trp_automatically_translated_slug_es_es":null,"_trp_automatically_translated_slug_hu_hu":null,"_trp_automatically_translated_slug_fi":null,"_trp_automatically_translated_slug_ja":null,"_trp_automatically_translated_slug_lt_lt":null,"_elementor_edit_mode":null,"_elementor_template_type":null,"_elementor_version":null,"_elementor_pro_version":null,"_wp_page_template":null,"_elementor_page_settings":null,"_elementor_data":null,"_elementor_css":null,"_elementor_conditions":null,"_happyaddons_elements_cache":null,"_oembed_75446120c39305f0da0ccd147f6de9cb":null,"_oembed_time_75446120c39305f0da0ccd147f6de9cb":null,"_oembed_3efb2c3e76a18143e7207993a2a6939a":null,"_oembed_time_3efb2c3e76a18143e7207993a2a6939a":null,"_oembed_59808117857ddf57e478a31d79f76e4d":null,"_oembed_time_59808117857ddf57e478a31d79f76e4d":null,"_oembed_965c5b49aa8d22ce37dfb3bde0268600":null,"_oembed_time_965c5b49aa8d22ce37dfb3bde0268600":null,"_oembed_81002f7ee3604f645db4ebcfd1912acf":null,"_oembed_time_81002f7ee3604f645db4ebcfd1912acf":null,"_elementor_screenshot":null,"_oembed_7ea3429961cf98fa85da9747683af827":null,"_oembed_time_7ea3429961cf98fa85da9747683af827":null,"_elementor_controls_usage":null,"_elementor_page_assets":null,"_elementor_screenshot_failed":null,"theplus_transient_widgets":null,"_eael_custom_js":null,"_wp_old_date":null,"_trp_automatically_translated_slug_it_it":null,"_trp_automatically_translated_slug_pt_pt":null,"_trp_automatically_translated_slug_zh_cn":null,"_trp_automatically_translated_slug_nl_nl":null,"_trp_automatically_translated_slug_pt_br":null,"_trp_automatically_translated_slug_sv_se":null,"rank_math_analytic_object_id":null,"rank_math_internal_links_processed":null,"_trp_automatically_translated_slug_ro_ro":null,"_trp_automatically_translated_slug_sk_sk":null,"_trp_automatically_translated_slug_bg_bg":null,"_trp_automatically_translated_slug_sl_si":null,"litespeed_vpi_list":["webhostinglogo.png"],"litespeed_vpi_list_mobile":["webhostinglogo.png"],"rank_math_seo_score":null,"rank_math_contentai_score":null,"ilj_limitincominglinks":null,"ilj_maxincominglinks":null,"ilj_limitoutgoinglinks":null,"ilj_maxoutgoinglinks":null,"ilj_limitlinksperparagraph":null,"ilj_linksperparagraph":null,"ilj_blacklistdefinition":null,"ilj_linkdefinition":null,"_eb_reusable_block_ids":null,"rank_math_focus_keyword":"hetzner dns konfiguration","rank_math_og_content_image":null,"_yoast_wpseo_metadesc":null,"_yoast_wpseo_content_score":null,"_yoast_wpseo_focuskeywords":null,"_yoast_wpseo_keywordsynonyms":null,"_yoast_wpseo_estimated-reading-time-minutes":null,"rank_math_description":null,"surfer_last_post_update":null,"surfer_last_post_update_direction":null,"surfer_keywords":null,"surfer_location":null,"surfer_draft_id":null,"surfer_permalink_hash":null,"surfer_scrape_ready":null,"_thumbnail_id":"12383","footnotes":null,"_links":{"self":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12390","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/comments?post=12390"}],"version-history":[{"count":0,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/posts\/12390\/revisions"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media\/12383"}],"wp:attachment":[{"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/media?parent=12390"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/categories?post=12390"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/webhosting.de\/en\/wp-json\/wp\/v2\/tags?post=12390"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}