# domain Domain names are a distributed hierarchical naming system used to refer to Internet resources, including host addresses and mailbox data. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Microsoft patch gives domain-joined Windows PCs trust issues DevFeed: [Microsoft patch gives domain-joined Windows PCs trust issues]() Original publisher: [Read original article]() Author: Richard Speed Published: 2026-09-17T13:45:00Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Windows](), [domain](), [Microsoft](), [trust](), [Server]() Tags: [2025](), [controllers](), [credentials](), [domain](), [microsoft](), [os-platforms](), [server](), [trust](), [windows]() ### AI overview Microsoft patches are reported to have caused trust issues for domain-joined Windows PCs. Machine Identity Isolation policies may reject valid credentials when controllers do not meet the Server 2025 functional level. ### Source excerpt Machine Identity Isolation policies can reject valid credentials unless controllers meet the Server 2025 functional level ## CAA DNS Issuer-Critical Flags Are Confusing to Configure DevFeed: [CAA DNS Issuer-Critical Flags Are Confusing to Configure]() Original publisher: [Read original article]() Author: Remy Porter Published: 2026-09-10T06:30:00Z Content type: opinion Language: en Sources: [The Daily WTF]() Topics: [certificates](), [domain]() Tags: [bits](), [boolean](), [certificates](), [documentation](), [feature-articles](), [flag](), [https](), [readability]() ### AI overview The article examines confusion around the issuer-critical flag in DNS CAA records. It explains that the flag is defined as a bitmask, while many users interpret the documentation as requiring the integer 1 instead of the value representing the specified bit, creating a dilemma for certificate issuers such as LetsEncrypt. ### Source excerpt I'm not a DNS person, in that I appreciate that it exists but am not up on the inner workings. It solves a lot of problems with dark magic I don't fully understand, and fortunately don't need to. But Lucio noticed something that I do think is interesting, within the scope of the CAA record type. The CAA record started with RFC6844, which was obsoleted by RFC8659. Both RFCs lay out the same core idea: you can add a CAA record to your DNS entries to say, "hey, this domain over here is allowed to issue certificates for me". That's the sort of thing that enables LetsEncrypt to hand out certs, and is an important part of why we can run HTTPS everywhere these days. Now, RFC6844 has this in it: Issuer Critical: If set to '1', indicates that the corresponding property tag MUST be understood if the semantics of the CAA record are to be correctly interpreted by an issuer. Issuers MUST NOT issue certificates for a domain if the relevant CAA Resource Record set contains unknown property tags that have the Critical bit set. The issuer critical flag means that the certificate issuer needs to validate your CAA record before it issues a certificate for you. There's more in the RFC about what exactly that means, but we don't care about those details for right now. The rule here is "set a flag to 1". A little later in the RFC, the flag is described in more detail- as a bitmask. Specifically, bit 0 is the issuer critical flag. Bits 1-7 are reserved for future use. Now, here's where we get into trouble, because programmers don't understand bits, and because the CAA record expects you to put an integer in this field. So, if you want issuer critical enabled, what value to you put in this field? 128, obviously. That's 10000000. Except, if you don't understand bits, that's not obvious. A lot of people read this and decided that the documentation meant they needed to put 1 in the field- aka 00000001. This is wrong. The updated RFC tries to explain it a bit more clearly: Bit 0, Issuer Critic ## Autistici / Inventati et la censure sur leur nom de domaine DevFeed: [Autistici / Inventati et la censure sur leur nom de domaine]() Original publisher: [Read original article]() Published: 2026-08-29T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [Internet](), [Website]() Tags: [2026](), [article](), [dns](), [domain](), [internet](), [web]() ### AI overview This French article explains the technical effects of the censorship of the autistici.org domain. It discusses DNS publication being disabled at the registry, the resulting NXDOMAIN response, verification through RDAP, and a temporary workaround using the website's IP address. ### Source excerpt Le 28 août 2026, le nom de domaine "autistici.org" a cessé de fonctionner. Que se passe-t-il techniquement ? ## A Model for Understanding AI Success in Organizations DevFeed: [A Model for Understanding AI Success in Organizations]() Original publisher: [Read original article]() Author: John Cutler Published: 2026-07-19T15:21:27Z Content type: opinion Language: en Sources: [The Beautiful Mess]() Topics: [Artificial Intelligence](), [context](), [domain](), [iteration](), [Risk]() Tags: [ai](), [context](), [domain](), [iteration](), [risk]() ### AI overview The article presents a multiplicative model for AI success based on technology understanding, problem understanding, practice evolution, and an organizational social contract. It argues that missing any essential factor can undermine the outcome, while resistance to AI mandates may reflect rational self-preservation and insufficient evidence. ### Source excerpt Here's a simple model for thinking about AI success in organizations. ## Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry DevFeed: [Telegram's Short-Link Domain Was Temporarily Suspended by Montenegro's .me Registry]() Original publisher: [Read original article]() Published: 2026-07-14T00:00:00Z Content type: article Language: fr Sources: [Blog de Stéphane Bortzmeyer]() Topics: [domain](), [client](), [service]() Tags: [article](), [client](), [dns](), [domain](), [telegram]() ### AI overview Telegram's short-link domain became unavailable after Montenegro's .me registry stopped publishing it in DNS. The article examines the resulting NXDOMAIN responses, resolver caching, and the domain's later reactivation. ### Source excerpt Si vous utilisez le service de messagerie instantanée Telegram, vous avez sans doute vu aujourd'hui 14 juillet 2026, que des services ne marchaient pas, notamment les liens vers des ressources diverses (images, etc). C'est parce que le registre de noms de domaine du Monténégro l'avait décidé. Voyons les détails. ## 20 Networking Concepts Explained in 15 Minutes DevFeed: [20 Networking Concepts Explained in 15 Minutes]() Original publisher: [Read original article]() Author: Ashish Pratap Singh Published: 2026-06-02T05:28:43Z Content type: tutorial Language: en Sources: [AlgoMaster Newsletter]() Topics: [networking](), [Networks](), [domain](), [Internet](), [browser](), [HTTP]() Tags: [browser](), [concepts](), [dns](), [domain](), [http](), [https](), [ipv4](), [ipv6](), [mac-address](), [network](), [networking](), [postgresql](), [recursive-resolver](), [redis](), [ssh](), [wi-fi]() ### AI overview A tutorial introducing core networking concepts, including IP addressing, DNS resolution, ports, MAC addresses, and ARP, with examples involving browsers, routers, servers, SSH, HTTP, PostgreSQL, and Redis. ### Source excerpt Networking can feel overwhelming, but a small set of concepts carries most of the weight in interviews and real-world systems. ## One GitHub Account, Many Domains: Deploying Family Sites with GitHub Pages DevFeed: [One GitHub Account, Many Domains: Deploying Family Sites with GitHub Pages]() Original publisher: [Read original article]() Published: 2026-03-23T00:00:00Z Content type: tutorial Language: en Sources: [Alex Korbonits]() Topics: [GitHub](), [GitHub Pages](), [GitHub Actions](), [domain](), [Astro](), [hosting]() Tags: [astro](), [domain](), [github](), [github-actions](), [github-pages](), [hosting]() ### AI overview A practical guide to hosting multiple family-domain placeholder sites from one GitHub account using separate repositories, GitHub Pages custom domains, Astro, GitHub Actions, and DNS configuration. ### Source excerpt How I spun up four placeholder sites for family domains in under an hour using GitHub Pages, Astro, and GitHub Actions -- all from a single account. ## Setting up a Wireguard VPN in UniFi DevFeed: [Setting up a Wireguard VPN in UniFi]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2024-08-31T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Virtual Private Network](), [configuration](), [Routing (disambiguation)](), [domain](), [networking]() Tags: [configuration](), [dns](), [go](), [how-to](), [route](), [vpn]() ### AI overview A quick tutorial explains how to configure a WireGuard VPN client on a UniFi Dream Machine using a Mullvad configuration file, then route selected domains or traffic through the VPN. It also discusses static routes for accessing the network from outside. ### Source excerpt This is a quick post showing how to set up a Wireguard VPN in an UniFi Dream Machine. ## Homographic Spoofing: a new Ruby toolkit DevFeed: [Homographic Spoofing: a new Ruby toolkit]() Original publisher: [Read original article]() Author: Jacopo Beschi Published: 2024-06-25T17:00:00Z Content type: tutorial Language: en Sources: [37signals Dev]() Topics: [spoofing](), [Ruby](), [Security](), [Open Source](), [email](), [domain](), [ASCII]() Tags: [ascii](), [domain](), [email](), [open-source](), [phishing](), [ruby](), [security](), [spoofing]() ### AI overview This article explains homograph attacks, in which visually similar Unicode characters are used to spoof identities in domains or email. It describes browser and email-client protections using Punycode and UTS #39, then introduces an open-source Ruby gem implementing those guidelines for IDNs and email addresses. ### Source excerpt What is a homograph attack and how to protect from it with a new gem. ## Use of HTTPS Resource Records DevFeed: [Use of HTTPS Resource Records]() Original publisher: [Read original article]() Published: 2023-11-14T01:35:15Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [domain]() Tags: [analysis](), [dns](), [domain](), [https]() ### AI overview An analysis of more than 225 million domain names examines current use of the new HTTPS DNS Resource Records. ### Source excerpt An analysis of over 225 million domain names to determine the current use of the new HTTPS DNS Resource Records. ## TLD Domain Count Stats DevFeed: [TLD Domain Count Stats]() Original publisher: [Read original article]() Published: 2023-08-11T22:05:34Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [domain]() Tags: [domain](), [number]() ### AI overview The article presents counts of domain names grouped by top-level domain (TLD). ### Source excerpt I got tired of not finding a good source of domain name stats, so I put together counts of all TLDs by number of domain names in them myself. ## Announcing Custom Domains on Fermyon Cloud DevFeed: [Announcing Custom Domains on Fermyon Cloud]() Original publisher: [Read original article]() Author: MacKenzie Olson Published: 2023-07-26T16:00:00Z Content type: release Language: en Sources: [Fermyon - Experience the next wave of cloud computing.]() Topics: [Cloud](), [domain]() Tags: [announce](), [cloud](), [custom](), [domain]() ### AI overview Fermyon Cloud now supports custom domains, allowing users to bring their own domain while Fermyon manages the rest. ### Source excerpt Today, we are excited to announce support for custom domains on Fermyon Cloud - bring your domain, and we'll handle the rest. ## Kotlin Coroutines use cases for Domain Layer DevFeed: [Kotlin Coroutines use cases for Domain Layer]() Original publisher: [Read original article]() Published: 2022-11-24T00:00:00Z Content type: tutorial Language: en Sources: [Kt. Academy]() Topics: [Kotlin](), [Coroutines](), [kotlin-coroutines](), [domain](), [Development](), [Programming]() Tags: [coroutines](), [domain](), [kotlin](), [kotlin-coroutines](), [programming](), [programming-language](), [workshop-learning-programming]() ### AI overview This tutorial explains how Kotlin Coroutines are used in the Domain Layer. ### Source excerpt How do we use Kotlin Coroutines in the Domain Layer. ## Getting Partial AWS Account IDs for any Cloudfront Website DevFeed: [Getting Partial AWS Account IDs for any Cloudfront Website]() Original publisher: [Read original article]() Published: 2021-07-09T07:00:00Z Content type: article Language: en Sources: [Arkadiy Tetelman]() Topics: [Amazon Web Services](), [AWS Certificate Manager](), [bug](), [TLS (Transport Layer Security)](), [private key](), [public key](), [domain]() Tags: [aws](), [bug](), [certificates](), [domain](), [private-key](), [public-key](), [ssl](), [tls](), [website]() ### AI overview This article explains how a bug in AWS Certificate Manager could bypass CloudFront's TLS-certificate requirement for looking up partial AWS account and distribution IDs associated with a domain. It describes manipulating RSA private-key parameters to match a public certificate. ### Source excerpt Yesterday Amazon released a new Cloudfront API that returns partial AWS account ids and Cloudfront distribution ids associated with some given domain name, to help you determine which of your own AWS accounts serves traffic for that domain. In Cloudfront, a domain alias can only be associated with a single distribution globally across all AWS accounts, and for companies that have a lot of assets it can be difficult to track down which account owns a given domain - this API helps solve that problem. Of course it would be problematic if we could lookup account ids (even partial ones) for arbitrary websites, so to help protect against this information leakage Amazon requires you to have a valid TLS certificate for the domain name you want to query. This is called out in their documentation: To list conflicting aliases, you provide the alias to search and the ID of a distribution in your account that has an attached SSL/TLS certificate that includes the provided alias. As it turns out it's possible to completely bypass this restriction, because ACM has a bug that lets you import certificates without a valid private key. Most people are aware that RSA consists of a public and private keypair which correspond to each other, with the public key completely derived from the private key. That is - if you give me only a private key, I can easily give you the public key that matches the private one. However what some people find surprising is that even though the public key is derived, the private key contains a full copy of the public key (the N and e parameters, in RSA parlance) in order to save on computation time. So if we want to find the partial AWS account id for some domain, we can fetch the real public certificate for that domain, generate a random private key, and update the precomputed public key parameters on our private key to be the same as the public key on the certificate we want to impersonate. ACM has a bug in that it does not validate the private key truly co ## Email Address Validation Must Account for Both Domain and Local Parts DevFeed: [Email Address Validation Must Account for Both Domain and Local Parts]() Original publisher: [Read original article]() Published: 2021-04-03T01:29:16Z Content type: article Language: en Sources: [Signs of Triviality]() Topics: [email](), [domain]() Tags: [domain](), [email](), [local](), [validation]() ### AI overview The article argues that email address validation is difficult because both the domain and local parts require careful handling. ### Source excerpt Nope, you don't know how to validate an email address. Even if you think you'd get the domain part right, fuggeddabout the local part. Seriously. ## History of PowerDNS: 2013-2020 (Technology) DevFeed: [History of PowerDNS: 2013-2020 (Technology)]() Original publisher: [Read original article]() Published: 2020-12-21T19:32:58Z Content type: article Language: en Sources: [Bert Hubert's writings]() Topics: [Software](), [Software Engineering](), [domain](), [DNSSEC](), [ASCII](), [Protocol (disambiguation)]() Tags: [ascii](), [bugs](), [business](), [cleanup](), [cognitive-load](), [complexity](), [dns](), [dnssec](), [domain](), [history](), [powerdns](), [protocol](), [software](), [standards](), [technology]() ### AI overview This article covers the technical development of PowerDNS from 2013 to 2020, including an extensive internal cleanup of mature code. It explains how the cleanup addressed accumulated complexity, bugs, and incorrect treatment of DNS names as ASCII strings, including ordering, case, escaping, and spaces. ### Source excerpt In this part of the history of PowerDNS, I talk about the technical developments from 2013 to 2020. Over these years many fascinating business & hiring developments also happened, but these are described in a separate post, part 3B of the PowerDNS History. Here are the earlier parts: Part 1, Part 2 For context, the 2013-2020 era is what I would describe as "PowerDNS 3.0" - how we grew from a one (or two) person company to a healthy and thriving department of Open-Xchange. ## Finding a Domain for Your Side Project DevFeed: [Finding a Domain for Your Side Project]() Original publisher: [Read original article]() Author: Fuzzygroup Published: 2020-05-17T00:00:00Z Content type: opinion Language: en Sources: [Scott Johnson]() Topics: [domain](), [Amazon Web Services]() Tags: [aws](), [domain](), [marketing](), [project](), [side-project](), [sideproject](), [startup]() ### AI overview The article argues that choosing a domain remains important for a side project but need not be perfect. It recommends generating keyword combinations and checking availability with Octopoly, while cautioning that Octopoly's domain registration prices are higher than AWS prices. ### Source excerpt I would argue that even in the age of the app, a domain for your side project is still absolutely important. Now, despite that, one of the truths of side projects is that your domain is important but you aren't going to be dogmatic about it in the way that a funded company approaches their naming. What I like to do for this is figure out possible options and then run with a multiple domain search service. I'm playing around with a project which has a couple of possible related keywords in the domain: chat sober talk safe text This gave me a bunch of combinations: safechat.com safechat.io safetalk.com safetalk.io soberchat.com soberchat.io sobertalk.com sobertalk.io safetexts.com safetexts.io sobertexts.com sobertexts.io safetexting.com safetexts.io A quick trip to octopoly and their search engine: https://my.octopoly.nz/das/search/ let me put in a bunch of these and find out which are available domains. I didn't end up with exactly what I wanted but I did end up with a good enough domain which was sufficient to move forward - and that's generally enough for a side project. Octopoly. Absolutely recommended. Note 1: I'm sure there are other options out there and ones that do automatic suggestions, etc. But the ones that I've seem are paid and none seem to work quite as well as Octopoly. Note 2: Do not register your domains thru Octopoly, their costs are insane. A .io domain is normally $39 when bought through AWS but it is $79 through Octopoly. Grumble. ## One million npm downloads DevFeed: [One million npm downloads]() Original publisher: [Read original article]() Author: Stanko Published: 2018-12-04T00:00:00Z Content type: opinion Language: en Sources: [Stanko Tadić]() Topics: [npm](), [npm packages](), [domain]() Tags: [domain](), [npm](), [npm-packages](), [personal](), [projects](), [side-projects]() ### AI overview The author says their npm packages have surpassed one million downloads this year, based on npm-stat.com. They also announce having a real domain and mention upcoming small side projects. ### Source excerpt I want to brag a little - my npm packages have been downloaded more than 1 million timesStats are coming from npm-stat.com. this year! And I finally got a real domain: https://muffinman.io/ I've been quiet for the last couple of months. Mostly because I was busy with other things, both work and personal. But I do have a few small side projects I will be sharing soon. Stay tuned! ## The death of a TLD DevFeed: [The death of a TLD]() Original publisher: [Read original article]() Author: ben@benjojo.co.uk Published: 2018-07-26T21:35:23Z Content type: article Language: en Sources: [benjojo blog]() Topics: [domain](), [Certificate Transparency](), [certificates](), [SSL](), [Web](), [email]() Tags: [certificate-transparency](), [certificates](), [domain](), [mail](), [ssl](), [web]() ### AI overview The article examines Sony's termination of a generic top-level domain and places it in the broader trend of abandoned gTLDs. It uses Certificate Transparency logs to investigate whether revoked domains had issued SSL certificates and notes possible effects on landing pages and email addresses. ### Source excerpt The death of a TLD Another one bites the dust. The gTLD gold rush is now seeing a steady flow of TLD's that clearly just didnt work out. In the last week, ICANN removed the documentation ## Making your website multi-regional using top-level domains DevFeed: [Making your website multi-regional using top-level domains]() Original publisher: [Read original article]() Author: Nicolas Mondollot Published: 2015-04-15T12:19:08Z Content type: article Language: en Sources: [eFounders]() Topics: [Website](), [Search engine optimization (SEO)](), [Rails](), [domain](), [Development]() Tags: [article](), [development](), [dns](), [domain](), [rails](), [search-engine-optimization](), [seo](), [startup](), [tech](), [website]() ### AI overview This article explains how to localize a website for multiple languages and regions, compare URL strategies for international SEO, and use country-specific top-level domains with Rails. It describes Drivy's choice of ccTLDs and notes limitations in a simple domain-based locale implementation. ### Source excerpt illustration: Adrien Griveau Hi there. My name is Nicolas Mondollot, I am the CTO of Drivy -- an awesome peer-to-peer car rental service. We launched our german website in early 2015. Here are some things we learned along the way. When you start a website you usually start small: one website, hosted on one domain, targeting one country and one language. Simple, right? Then, one day you decide to go international (exciting!). One problem, though: people don't all speak/read the same language everywhere. You must localize you content in multiple languages. The standardized way to do so is to use a locale for each language and geographical region you are targeting. For instance if you want to make your website available in the US, France and Canada you'll need 4 locales: en : English (US) fr : French (France) fr-CA : French (Canada) en-CA : English (Canada) side note: this is a 'pragmatic' approach to locale naming, where we drop the regional part when it is not needed (more information here). Great. Now, how do you make your website available in all these locales? Locales and URLs The first rule of Search Engine Optimization when you go international is: the locale must appear in the URL. Google suggests choosing among several options: URL parameters: example.com?locale=fr Subdirectories with a generic top-level domain (gTLD): example.com/fr/ Subdomains with a generic top-level domain (gTLD): fr.example.com Country-specific top-level domains (ccTLD): example.fr There is no one-size-fits-all approach. The best solution really depends on your specific requirements (this article from Moz may give you some pointers). At Drivy we decided to use ccTLDs because it was the best solution SEO-wise to target different countries. Plus it's prettier. First implementation In Rails this is pretty straightforward. You just need to point your new domain DNS to your application server and drop this code in your ApplicationController (inspired by the official Rails guide): class Applicat ## AutoMapper And Incompleteness DevFeed: [AutoMapper And Incompleteness]() Original publisher: [Read original article]() Published: 2011-09-15T00:00:00Z Content type: opinion Language: en Sources: [Tim Kellogg]() Topics: [Code](), [implementation](), [domain](), [unit tests]() Tags: [code](), [compiler](), [domain](), [implementation](), [unit-tests]() ### AI overview The article critiques AutoMapper for limiting mappings between view models and models, preventing view models from extending models, and encouraging duplicated properties and validation attributes. It proposes extending models with view models to reduce duplication and let the compiler catch certain mismatches, while acknowledging that this approach has other issues. ### Source excerpt This is part 2 of a series. Read part 1Earlier I talked about the Law of Demeter and how view models help us better adhere to the Law of Demeter. I also briefly outlined how AutoMapper makes view models practical. While AutoMapper is a great tool, it isn't completely fulfilling. Let me explainAs I pointed out previously, some of the behaviors in AutoMapper make it feel incomplete. The first is that you can't map two view models to the same model and back.A much bigger problem with AutoMapper is that view models can't extend models. I'm not sure why they decided to disallow this usage, but it causes a cascade of code duplication (very un-DRY). Take a look at these classes:There are a few things wrong here. Age is a nullable int on the model but the view model has just an int. If a null slips through this could cause a crashing error. While AutoMapper has an AssertConfigurationIsValid method, it doesn't test for this sort of case. You'll have to make unit tests for this, luckily you can use NetLint to easily test for these sorts of flukes.Another issue is the validation attributes. The facts that account codes look like CO11582 and that all accounts must have a name are descriptors of the domain (which the model is modelling). They aren't facts about the view (although they have to be expressed in the view), they are part of the model. Every time you create another AccountViewModelX derivative AutoMapper requires you to copy these attributes. This is a massive failure in the attempt to keep code DRY.Another issue I have is when I'm creating a view model I'm not sure what properties need to be created. I usually have to split the window and copy properties from model to view model (this screams obscenities at the idea of DRY code).One solution that I keep coming back to is to have view models extend models. For instance, see this implementation:Here, you don't have to type out all those properties a second (or third) time. They're just available. You also won't make th