liveBook · Manning

Subdomain

A subdomain is a bounded subdivision or subordinate namespace within a broader domain, such as a business area or a domain-name hierarchy.

How 3 Manning books explain it

Architecture Modernization: Socio-technical alignment of software, strategy, and structure

A business subdomain is a distinct subdivision of a broader business domain with its own related knowledge, activities, and bounded scope.

How it is used
Structures business areas into candidate value streams, team responsibilities, software boundaries, and modernization investments.
How deep it goes
Works through boundary heuristics, EventStorming, cohesion checks, and trade-offs; avoids prescribing one universally correct decomposition.
Examples
Uses loyalty levels, fulfillment capabilities, and alternative onboarding arrangements to test where related concepts belong.
What you can do after
Practice/perform collaborative subdomain mapping, assess candidate boundaries, and revisit them as business needs change.

Read how Architecture Modernization: Socio-technical alignment of software, strategy, and structure explains subdomain →

Acing the CCNA Exam: Volume 2 Advanced Networking and Security

A subdomain is a domain located beneath another domain in the DNS hierarchy.

How it is used
Organizes DNS names into nested administrative and navigational levels.
How deep it goes
Explains hierarchy, naming terminology, and FQDN notation, but does not cover subdomain configuration.
Examples
Uses com, google.com, www.google.com, and the trailing root-domain dot to illustrate nesting and notation.
What you can do after
Evaluate DNS names by identifying their hierarchy level, parent domain, subdomain relationships, and FQDN notation.

Read how Acing the CCNA Exam: Volume 2 Advanced Networking and Security explains subdomain →

Building Web APIs with ASP.NET Core

A subdomain is a subordinate domain name created within a parent domain's namespace.

How it is used
Deploys a public endpoint for a web API through a parent domain and DNS provider.
How deep it goes
Explains naming and A-record configuration, but stops short of broader DNS and TCP/IP fundamentals.
Examples
Uses win-01.mybglist.com and mybglist-win-01.westeurope.cloudapp.azure.com as deployment addresses.
What you can do after
Operate/configure a custom Cloudflare subdomain that points to an Azure VM’s public IP address.

Read how Building Web APIs with ASP.NET Core explains subdomain →

Related concepts

These guides are generated from the text of Manning books by Manning's knowledge graph and link to the sections they draw on. The full books are available on liveBook and at manning.com.