[{"data":1,"prerenderedAt":380},["ShallowReactive",2],{"blog-dns-fqdn-routing":3},{"id":4,"title":5,"body":6,"description":359,"extension":360,"meta":361,"navigation":375,"path":376,"seo":377,"stem":378,"__hash__":379},"blog/blog/dns-fqdn-routing.md","Was sind DNS, FQDN und Routing im Internet?",{"type":7,"value":8,"toc":343},"minimark",[9,14,23,28,39,44,156,160,163,167,174,177,199,203,223,227,230,245,248,252,270,274,311,315,336,340],[10,11,13],"h1",{"id":12},"dns-fqdn-und-routing-wie-domains-wirklich-funktionieren","DNS, FQDN und Routing – wie Domains wirklich funktionieren",[15,16,17,18,22],"p",{},"Wenn Sie eine Domain wie ",[19,20,21],"code",{},"innfinit.com"," in den Browser eingeben, passiert in Millisekunden sehr viel im Hintergrund. Dieser Artikel erklärt verständlich, wie DNS und Routing arbeiten, was ein FQDN ist – und warum das für Erreichbarkeit, E‑Mail‑Zustellung, Sicherheit und SEO wichtig ist.",[24,25,27],"h2",{"id":26},"was-ist-dns","Was ist DNS?",[15,29,30,31,34,35,38],{},"Das Domain Name System (DNS) ist das „Telefonbuch des Internets“. Es übersetzt leicht merkbare Namen (Domains) in IP‑Adressen, die Computer verstehen (z. B. ",[19,32,33],{},"93.184.216.34"," oder ",[19,36,37],{},"2606:2800:220:1:248:1893:25c8:1946",").",[40,41,43],"h3",{"id":42},"wichtige-dnsressourceneinträge-records","Wichtige DNS‑Ressourceneinträge (Records)",[45,46,47,63],"table",{},[48,49,50],"thead",{},[51,52,53,57,60],"tr",{},[54,55,56],"th",{},"Record",[54,58,59],{},"Zweck",[54,61,62],{},"Beispiel",[64,65,66,80,93,106,119,132,145],"tbody",{},[51,67,68,72,75],{},[69,70,71],"td",{},"A",[69,73,74],{},"Verweist auf IPv4‑Adresse",[69,76,77],{},[19,78,79],{},"example.com → 203.0.113.10",[51,81,82,85,88],{},[69,83,84],{},"AAAA",[69,86,87],{},"Verweist auf IPv6‑Adresse",[69,89,90],{},[19,91,92],{},"example.com → 2001:db8::10",[51,94,95,98,101],{},[69,96,97],{},"CNAME",[69,99,100],{},"Alias auf anderen Namen",[69,102,103],{},[19,104,105],{},"www.example.com → example.com",[51,107,108,111,114],{},[69,109,110],{},"MX",[69,112,113],{},"E‑Mail‑Zustellung",[69,115,116],{},[19,117,118],{},"example.com → aspmx.l.google.com.",[51,120,121,124,127],{},[69,122,123],{},"TXT",[69,125,126],{},"Freier Text (z. B. SPF, DKIM, Verifikationen)",[69,128,129],{},[19,130,131],{},"v=spf1 include:_spf.google.com ~all",[51,133,134,137,140],{},[69,135,136],{},"NS",[69,138,139],{},"Autoritative Nameserver der Zone",[69,141,142],{},[19,143,144],{},"ns1.provider.net., ns2.provider.net.",[51,146,147,150,153],{},[69,148,149],{},"SOA",[69,151,152],{},"Zonen‑Stammdatensatz",[69,154,155],{},"Primärer NS, Seriennummer, Kontakt",[40,157,159],{"id":158},"ttl-und-caching","TTL und Caching",[15,161,162],{},"Jeder Record hat eine Time‑to‑Live (TTL). Sie bestimmt, wie lange Resolver Antworten zwischenspeichern. Kurze TTLs beschleunigen Umstellungen (z. B. Cutover), längere TTLs verbessern Performance und reduzieren Last.",[24,164,166],{"id":165},"was-ist-ein-fqdn","Was ist ein FQDN?",[15,168,169,170,173],{},"Ein Fully Qualified Domain Name (FQDN) ist der vollständig qualifizierte Name inklusive aller Labels bis zur Root‑Zone: z. B. ",[19,171,172],{},"app.eu.example.com."," – der abschließende Punkt kennzeichnet die Root.",[15,175,176],{},"Typische FQDNs:",[178,179,180,187,193],"ul",{},[181,182,183,186],"li",{},[19,184,185],{},"www.example.com."," (Website)",[181,188,189,192],{},[19,190,191],{},"mail.example.com."," (Mailserver)",[181,194,195,198],{},[19,196,197],{},"api.example.com."," (Backend/API)",[24,200,202],{"id":201},"nameserver-autoritativ-vs-rekursiv","Nameserver – autoritativ vs. rekursiv",[178,204,205,216],{},[181,206,207,208,211,212,215],{},"Rekursive Resolver (z. B. ",[19,209,210],{},"1.1.1.1",", ",[19,213,214],{},"8.8.8.8",") fragen im Auftrag der Nutzer die Kette der autoritativen Server ab und cachen die Ergebnisse.",[181,217,218,219,222],{},"Autoritative Nameserver sind die „Quelle der Wahrheit“ für deine Zone (z. B. ",[19,220,221],{},"example.com","). Dort pflegst du Records.",[24,224,226],{"id":225},"routing-im-internet-vereinfacht","Routing im Internet (vereinfacht)",[15,228,229],{},"Damit Pakete überhaupt ihren Weg finden, tauschen Netze (Autonome Systeme) via BGP Routen aus. Vereinfacht:",[178,231,232,239,242],{},[181,233,234,235,238],{},"Dein Browser löst ",[19,236,237],{},"www.example.com"," auf eine IP auf (DNS)",[181,240,241],{},"Dein Gerät sendet Pakete an das Zielnetz",[181,243,244],{},"Router entlang des Pfads entscheiden per BGP, wohin das Paket als Nächstes geht",[15,246,247],{},"Wichtig für Unternehmen: stabile Netzwege (Upstreams), Anycast für DNS, DDoS‑Schutz und IPv6‑Unterstützung.",[24,249,251],{"id":250},"warum-ist-das-wichtig","Warum ist das wichtig?",[178,253,254,257,260,263],{},[181,255,256],{},"Erreichbarkeit: Falsche DNS‑Einträge ⇒ Website/Services offline",[181,258,259],{},"E‑Mail‑Zustellung: Ohne korrekte SPF/DKIM/DMARC sinkt die Zustellrate",[181,261,262],{},"Sicherheit: DNSSEC, HSTS/HTTPS, saubere Zonenverwaltung",[181,264,265,266,269],{},"SEO und Performance: saubere Hostnamen, konsistente Canonicals (",[19,267,268],{},"www"," vs. Root), schnelle Antworten (geringe TTL sinnvoll beim Umzug)",[24,271,273],{"id":272},"praxis-minimale-dnscheckliste","Praxis: Minimale DNS‑Checkliste",[275,276,277,283,286,289,302,305,308],"ol",{},[181,278,279,280,282],{},"A/AAAA für Root‑Domain und ",[19,281,268],{}," korrekt gesetzt (Redirect‑Strategie festlegen)",[181,284,285],{},"CNAME für Subdomains statt duplizierter A‑Records (wo sinnvoll)",[181,287,288],{},"MX + SPF + DKIM + DMARC für E‑Mails",[181,290,291,292,211,295,211,298,301],{},"Eigene Subdomains pro Service (z. B. ",[19,293,294],{},"api.",[19,296,297],{},"cdn.",[19,299,300],{},"status.",")",[181,303,304],{},"Sinnvolle TTL‑Werte (Deployment/Umzug vs. Stabilität)",[181,306,307],{},"Autoritative NS redundant (mind. zwei, unterschiedliche Netze/Regionen)",[181,309,310],{},"Optional: DNSSEC aktivieren",[24,312,314],{"id":313},"häufige-fehler","Häufige Fehler",[178,316,317,323,326,329],{},[181,318,319,320,322],{},"Mixed Content/Inkonsistenter Host (mal ",[19,321,268],{},", mal nicht)",[181,324,325],{},"Zu lange TTL kurz vor Relaunch – Änderungen dauern Stunden",[181,327,328],{},"CNAME auf Root‑Domain (funktioniert je nach Provider nicht)",[181,330,331,332,335],{},"SPF zu strikt (hartes ",[19,333,334],{},"-all",") – legitime Absender ausgesperrt",[24,337,339],{"id":338},"fazit","Fazit",[15,341,342],{},"DNS wirkt unsichtbar – ist aber geschäftskritisch. Mit sauberem Setup vermeidest du Ausfälle, erhöhst Zustellraten und schaffst die Basis für schnelle, sichere Web‑Erlebnisse.",{"title":344,"searchDepth":345,"depth":345,"links":346},"",2,[347,352,353,354,355,356,357,358],{"id":26,"depth":345,"text":27,"children":348},[349,351],{"id":42,"depth":350,"text":43},3,{"id":158,"depth":350,"text":159},{"id":165,"depth":345,"text":166},{"id":201,"depth":345,"text":202},{"id":225,"depth":345,"text":226},{"id":250,"depth":345,"text":251},{"id":272,"depth":345,"text":273},{"id":313,"depth":345,"text":314},{"id":338,"depth":345,"text":339},"Eine leicht verständliche Erklärung von Domains, DNS, FQDN und Routing – und warum das für Ihr Business wichtig ist.","md",{"date":362,"author":363,"category":364,"tags":365,"image":374},"2025-10-28","Maximilian Borrmann","Infrastruktur",[366,367,368,369,370,371,110,97,372,373],"DNS","Domain","FQDN","Nameserver","Routing","BGP","TTL","Sicherheit","/assets/img/hosting.webp",true,"/blog/dns-fqdn-routing",{"title":5,"description":359},"blog/dns-fqdn-routing","G7nouXrBGNBFXfB4gZAVP3cd58AvyUhKDpTKerRrzUE",1774112250429]