European Survey of Information Society


Home   Structure of ESIS   Background to the ESIS Project   Project Management Contacts   Lead and local Contractors   History of ESIS
Network domain

A "Network domain" is an administrative grouping of multiple private computer networks or hosts within the same infrastructure. A domain controller is a server which automates the logins, user groups, and architecture of a domain, rather than manually coding this information on each host in the domain. It is common practice, but not required, to have the domain controller act as a DNS server. That is, it would assign names to hosts in the network based off of their IP addresses. Domains are accessed externally using a hierarchical system of public DNS servers.
Half of the staff of Building A uses Network 1, This network has the VLAN identifier of VLAN 10
The other half of the staff of Building A uses Network 2, This network has the VLAN identifier of VLAN 20
All of the staff of Building B uses Network 3, This has the VLAN identifier of VLAN 11.
The router R1 serves as the gateway for all three networks, and the whole infrastructure is connected physically via ethernet cable. Networks 2 and 3 are routed through R1 and each has full access to the other.
Network 1 is completely separate from the other two, and will not have access to either of them. Network 2 and 3 are therefore in the same network domain, while Network 1 is in its own network domain, albeit alone.
A network administrator can then suitably name these network domains to match the infrastructure terminology.
Use of the term "network domain" first appeared in 1965 and saw increasing usage beginning in 1985. It initially applied to the naming of radio stations based on broadcast frequency and geographic area. It entered its current usage by network theorists to describe solutions to the problems of subdividing a single homogeneous LAN and joining multiple networks, possibly constituted of different network architectures.