Traditional quality means quality is often checked after most of the development work is already completed.
It follows a pattern like:
Plan → Build → Test → Fix → Release
Your Week 7 quality slide contrasts this with Agile quality, where testing and quality practices are moved earlier and shared by the whole team.
1. Quality gates near the end
A quality gate is a formal checkpoint where the project is reviewed before it can move forward.
Example:
The team finishes development, then the product must pass a final testing phase before release.
Problem:
If major defects are found at the end, fixing them may delay the release.
2. Dedicated QA after development
In traditional quality, developers may build first, then hand the product to a separate QA/testing team.
Example:
Developers complete the checkout feature. Then QA tests it later.
Problem:
Developers may already have moved on to other work, so fixing defects becomes slower.
3. Heavy documentation
Traditional quality often depends on detailed quality plans, test plans, sign-off forms, and formal review documents.
This can be useful for control and compliance, but it may slow feedback.
Example:
Before testing begins, the team prepares long test documents and approval forms.
4. Defects discovered late
Because testing happens near the end, defects may be found after many features are already built.
Example:
The team discovers late that the checkout process crashes on mobile.
Problem:
The defect may affect design, code, database, payment integration, and user experience.
5. Rework can be expensive
Late defects are usually more expensive because the team may need to redo completed work.
Example:
If password reset was built incorrectly, the team may need to change requirements, code, tests, documentation, and training materials.
Simple teaching line
Traditional quality often checks quality at the end. Agile tries to build quality throughout the work.
A good classroom example:
“If students write the whole assignment first and only check grammar at the end, fixing problems may be difficult. But if they check each section while writing, quality is built in earlier.”
How is the team doing right now, and what should we act on today or this sprint?
1. Sprint progress
This shows whether the team is on track to complete the sprint goal.
Question
Example metric
Are we on track?
Sprint burndown
How much work is left?
Remaining story points / tasks
Are stories moving to Done?
Completed vs remaining work
Is the sprint goal at risk?
Sprint goal status
Teaching line:
Sprint progress tells the team whether the current sprint is moving toward completion.
Example:
Burndown line is above ideal → more work remains than expected → team may be behind.
2. Quality
This shows whether the team is delivering good work, not just fast work.
Question
Example metric
Are defects increasing?
Open bugs / escaped defects
Are tests passing?
Test pass rate
Is code maintainable?
Code quality / static analysis
Is work truly Done?
DoD compliance
Teaching line:
Quality tells the team whether completed work is reliable, usable, and maintainable.
Example:
Velocity is high, but escaped defects are also high → team may be moving fast but not building quality in.
3. Blockers
This shows what is preventing the team from finishing work.
Question
Example metric
What is stuck?
Blocked items
Where is work waiting?
WIP by column
Who needs help?
Blocker owner
What needs escalation?
Blocker age
Teaching line:
Blockers show where the team needs to swarm, help each other, or escalate.
Example:
Three stories are waiting for API access from another team → dependency blocker.
4. Team health
This shows how sustainable and healthy the team is.
Question
Example metric
Is workload reasonable?
Capacity vs commitment
Is morale okay?
Team satisfaction survey
Is the team overloaded?
WIP, overtime, unfinished work
Is collaboration working?
Retrospective feedback
Teaching line:
Team health shows whether the team can continue delivering sustainably.
Example:
Team completed the sprint, but everyone worked overtime and satisfaction dropped → delivery may not be sustainable.
Simple classroom explanation
“A team dashboard is not mainly for executives. It helps the Agile team inspect and adapt during the sprint. It shows sprint progress, quality, blockers, and team health so the team knows what to fix next.”
Best short explanation
Team dashboard = daily/sprint-level decision dashboard. It helps the team see whether work is progressing, quality is good, blockers need attention, and the team is healthy enough to keep delivering.
This is usually a program manager / product manager / ART-level dashboard idea.
It answers:
Are features moving forward, are cross-team dependencies under control, and can we predict delivery with confidence?
1. Feature progress
This shows how much work has been completed for major features.
Example questions:
Question
Example dashboard metric
Which features are started?
Feature status: Not started / In progress / Done
How much is complete?
% complete or completed stories
Are features on track?
Planned vs actual completion
Which features are at risk?
Red/yellow/green status
Example:
Feature
Progress
Status
Search songs
80%
Green
Playlist sharing
45%
Yellow
Offline download
20%
Red
Teaching line:
Feature progress tells us whether important product capabilities are moving toward completion.
2. Dependencies
This shows whether one team is waiting for another team, system, vendor, or decision.
Example questions:
Question
Example dashboard metric
Which team is blocked?
Blocked dependency count
Who owns the dependency?
Dependency owner
When is it needed?
Needed-by date / sprint
Is the dependency late?
On track / delayed / escalated
Example:
Dependency
Needed by
Owner
Status
Search API from Platform Team
Sprint 2
Team 4
Yellow
Payment gateway approval
Sprint 3
Vendor
Red
UX design for sharing screen
Sprint 2
UX Team
Green
Teaching line:
Dependencies show where work may get stuck because one team needs something from another team.
3. Predictability
This shows whether the team or program usually delivers what it planned.
Example questions:
Question
Example dashboard metric
Do teams finish what they commit to?
Planned vs completed work
Is velocity stable?
Velocity trend
Are delivery dates reliable?
Forecast accuracy
Are sprint/PI objectives achieved?
Objective completion rate
Example:
Sprint
Planned
Completed
Predictability
Sprint 1
30 pts
28 pts
93%
Sprint 2
32 pts
30 pts
94%
Sprint 3
35 pts
20 pts
57%
Teaching line:
Predictability tells us how confidently we can trust the plan.
Simple classroom explanation
“Feature progress tells us what is being delivered. Dependencies tell us what might block delivery. Predictability tells us whether the plan is realistic based on past delivery.”
Best short explanation
This dashboard helps managers see whether features are progressing, whether dependencies need attention, and whether delivery forecasts are reliable.
Executive dashboard means a high-level dashboard for senior leaders, not for daily team work.
It should answer:
Are our major initiatives healthy, delivering outcomes, within risk tolerance, and within budget?
1. Portfolio health
This shows whether the organization’s major projects/programs are generally on track.
Examples:
Portfolio health question
Example metric
Are major projects on track?
% of initiatives green/yellow/red
Are key milestones being met?
Milestone completion status
Are teams overloaded?
Capacity vs demand
Are dependencies blocking progress?
Critical dependency count
Teaching line:
Portfolio health tells executives whether the overall project portfolio is healthy or at risk.
2. Outcomes
This shows whether the work is producing business/customer value, not just activity.
Examples:
Outcome question
Example metric
Are customers happier?
CSAT, NPS
Are users adopting the feature?
Feature adoption rate
Are we improving delivery?
Lead time reduction
Are we meeting strategic goals?
OKR progress
Teaching line:
Outcomes show whether the work is creating value, not just completing tasks.
3. Risk
This shows major threats that could affect delivery, quality, compliance, security, or business results.
Examples:
Risk question
Example metric
What could delay delivery?
High-risk dependencies
What could affect quality?
Escaped defects, critical bugs
What could affect compliance/security?
Open security issues
What needs executive attention?
Top 5 risks with owners
Teaching line:
Risk tells executives where attention or escalation may be needed.
4. Budget
This shows whether spending is aligned with the plan and expected value.
Examples:
Budget question
Example metric
Are we within budget?
Actual cost vs planned cost
Are we overspending?
Budget variance
Are funds going to the right priorities?
Spend by strategic theme/value stream
Are we getting value for money?
Cost vs outcome
Teaching line:
Budget shows whether investment is controlled and aligned with business value.
Simple classroom explanation
“A team dashboard asks: What should the team do today? An executive dashboard asks: Are we investing in the right work, getting value, managing risk, and staying within budget?”
Example executive dashboard
Area
Example status
Portfolio health
7 projects green, 2 yellow, 1 red
Outcomes
Customer satisfaction improved from 4.0 to 4.4
Risk
Payment integration is high risk and needs escalation
Budget
Portfolio is 6% over budget
Best short explanation:
Executive dashboard = big-picture decision dashboard. It focuses on portfolio health, business outcomes, major risks, and budget so leaders can decide where to invest, intervene, or adjust strategy.
Code quality metrics help the team judge whether the code is easy to understand, safe to change, reliable, efficient, and not creating future problems. Your Agile metrics slides describe code quality as how well-written, maintainable, and defect-free the codebase is, including readability, consistency, efficiency, standards, and technical debt reduction.
Code quality area
Meaning
Example
Maintainability
How easy it is to modify, fix, or extend the code later.
A new developer can add a payment option without rewriting the whole checkout module.
Readability
How easy the code is to read and understand.
Clear variable names, simple functions, comments where needed.
Reliability
How consistently the code works without defects or failures.
Login works every time and does not randomly fail under normal use.
Performance
How efficiently the code runs in terms of speed, memory, and resource use.
Search results load in 1 second instead of 10 seconds.
Standards / consistency
Whether the code follows coding guidelines, architecture rules, security rules, and team conventions.
All API responses follow the same structure; code passes linting/static analysis.
Reduced technical debt
Avoiding shortcuts that make future work harder or more expensive.
Instead of copy-pasting the same logic in five places, the team creates one reusable function.
Simple teaching line
Good code quality means the code works today and remains easy to change tomorrow.
Example for students
A feature may “work,” but if the code is messy, slow, hard to test, and full of shortcuts, then quality is still low. Good Agile teams do not only ask:
“Does it work?”
They also ask:
“Is it understandable, testable, reliable, efficient, and safe to maintain?”
For a customer, the most useful number is usually:
Lead Time
Because lead time measures the customer’s waiting time.
Simple comparison
Metric
Who cares most?
Why
Lead Time
Customer
“How long from my request until I get the result?”
Cycle Time
Team / manager
“How long did the team actively work on it?”
Throughput
Team / manager / planning
“How many items can we finish per week/sprint?”
Example
A customer requests a new feature on Monday.
The team starts working on it on Thursday.
The feature is delivered on Friday.
Metric
Value
Lead Time
Monday to Friday = 5 days
Cycle Time
Thursday to Friday = 2 days
Throughput
Example: team completed 12 items this week
From the customer’s view, the answer is:
“I waited 5 days.”
So lead time is most customer-focused.
Teaching line
Customers usually care about lead time because it tells them how long they wait for value. Teams care about cycle time and throughput because those help improve the system that produces that value.
A good short answer:
Lead time is most useful for customers. Cycle time and throughput are more useful for the team to manage and improve delivery.
Ref: Oracle VirtualBox User Guide: VirtualBox supports configurable virtual network cards per VM, host-only networking connects VMs with each other and the host while keeping them away from the outside network, and VirtualBox includes a DHCP server for host-only/internal networks. (VirtualBox) (VirtualBox)
Introduction
Oracle VirtualBox provides several networking modes for virtual machines. Each mode answers a different question:
Should the virtual machine access the Internet?
Should the virtual machine appear on the same network as the physical host?
Should virtual machines communicate only with each other?
Should the host computer be able to communicate with the virtual machines?
Should the virtual network use static IP addresses or DHCP?
One of the most useful modes for learning, testing, development, cybersecurity labs, server labs, and isolated multi-VM environments is Host-Only Networking.
A host-only network creates a private virtual network between the host computer and one or more virtual machines. It behaves like a small private LAN inside the physical computer.
1. What Is Host-Only Networking?
Host-only networking is a VirtualBox networking mode where:
The host computer can communicate with the virtual machine.
Virtual machines connected to the same host-only network can communicate with each other.
The virtual machines normally cannot access the outside physical network or the Internet through the host-only adapter alone.
A separate virtual network interface is created on the host system.
In simple terms, host-only networking creates a private network inside your computer.
Image 1: Basic Host-Only Network
flowchart LR
H[Host Computer<br>Host-Only Adapter<br>192.168.56.1]
S[Server VM<br>192.168.56.10]
C[Client VM<br>192.168.56.20]
H --- S
H --- C
S --- C
In this diagram, the host computer and both virtual machines are connected to the same private virtual network.
2. Why Use Host-Only Networking?
Host-only networking is useful when you want a controlled and isolated environment.
Common use cases include:
Server administration labs
You can create a Windows Server VM and a client VM, then test services such as DNS, DHCP, Active Directory, file sharing, remote administration, and web hosting.
Software development
A developer can run a web server, database server, or API server inside a VM and access it from the host machine without exposing it to the outside network.
Cybersecurity practice
Host-only networking is useful when testing security tools because the traffic stays inside the host-only environment. This reduces the risk of accidentally exposing services to the real LAN.
Multi-VM application testing
A web server VM, database VM, and client VM can communicate privately, just like machines in a small internal data center.
Training and teaching
Instructors can use host-only networks to build repeatable lab environments without depending on school, office, or home network settings.
3. Main Components of Host-Only Networking
Host-only networking depends on several VirtualBox components.
3.1 VirtualBox Host-Only Network
This is the virtual network segment. It is similar to a private LAN.
Example network:
Network: 192.168.56.0/24
Subnet mask: 255.255.255.0
Usable range: 192.168.56.1 to 192.168.56.254
The exact network range can be changed.
3.2 Host-Only Adapter on the Host
VirtualBox creates a virtual network adapter on the host operating system.
On Windows, it may appear as something like:
VirtualBox Host-Only Ethernet Adapter
On Linux or macOS, the name may be different.
This adapter receives an IP address on the host-only network, such as:
192.168.56.1
That IP belongs to the host computer, not to the VM.
3.3 VM Virtual Network Adapter
Each virtual machine has one or more virtual network adapters.
Inside VirtualBox:
VM Settings → Network → Adapter 1
Attached to: Host-only Adapter
Name: VirtualBox Host-Only Ethernet Adapter
This connects the VM to the host-only network.
3.4 VirtualBox DHCP Server
VirtualBox can run a built-in DHCP server for host-only networks. If enabled, it automatically gives IP addresses to VMs on that network.
This is convenient when you want quick automatic IP addressing.
However, if you are testing your own DHCP server inside a VM, you may want to disable VirtualBox DHCP so that your VM-based DHCP server is the only DHCP server on the private network.
3.5 VBoxManage
VBoxManage is the VirtualBox command-line management tool.
It can create, modify, list, and control networks and VM network adapters.
Example uses:
VBoxManage list hostonlyifs
VBoxManage list hostonlynets
VBoxManage list dhcpservers
VBoxManage modifyvm "VM Name" --nic1 hostonly
VBoxManage dhcpserver add ...
VBoxManage dhcpserver remove ...
The GUI is easier for beginners, but VBoxManage is powerful for automation.
4. How Host-Only Networking Works
A host-only network behaves like a virtual Ethernet switch.
The host computer and VMs connect to the same private switch.
When VM1 pings VM2, traffic stays inside the virtual network.
When the host pings VM1, traffic goes through the host-only adapter.
When VM1 tries to access the Internet through only the host-only adapter, it normally fails because host-only networking is not designed to route traffic to the outside network by default.
5. How IP Address Assignment Works
A VM on a host-only network needs an IP address.
There are three common ways to assign IP addresses:
Static IP address
VirtualBox built-in DHCP
A DHCP server running inside one of the VMs
5.1 Static IP Addressing
With static IP addressing, you manually configure the IP address inside the guest operating system.
VirtualBox can automatically assign IP addresses to VMs on host-only networks.
Example:
VirtualBox DHCP range: 192.168.56.100 - 192.168.56.200
Client VM receives: 192.168.56.101
Advantages
Quick setup
No need to configure IPs manually
Useful for simple testing
Disadvantages
Less control
May conflict with another DHCP server
Not ideal when learning or testing DHCP server configuration
5.3 DHCP Server Running Inside a VM
You can install a DHCP server inside a VM, such as:
Windows Server DHCP
Linux ISC DHCP Server
Kea DHCP
dnsmasq
pfSense DHCP
OPNsense DHCP
In this design, one VM becomes the DHCP server.
Example:
Host adapter: 192.168.56.1
DHCP Server VM: 192.168.56.10
DHCP scope/range: 192.168.56.100 - 192.168.56.150
Client VM receives: 192.168.56.100
Image 3: VM-Based DHCP Server
sequenceDiagram
participant Client as Client VM
participant Network as Host-Only Network
participant DHCP as DHCP Server VM
Client->>Network: DHCP Discover
Network->>DHCP: Broadcast reaches DHCP server
DHCP->>Client: DHCP Offer
Client->>DHCP: DHCP Request
DHCP->>Client: DHCP Acknowledge
This process is commonly called DORA:
D = Discover
O = Offer
R = Request
A = Acknowledge
Advantages
Realistic server practice
Good for Windows Server or Linux networking labs
Full control over scope, lease duration, DNS options, reservations, and exclusions
Disadvantages
More setup required
VirtualBox DHCP should usually be disabled to avoid conflict
Troubleshooting requires more networking knowledge
6. Static IP vs DHCP: Which Should You Use?
Scenario
Better Choice
One or two fixed servers
Static IP
Quick VM testing
VirtualBox DHCP
Learning DHCP service configuration
VM-based DHCP
Active Directory domain controller
Static IP
Temporary client VM
DHCP
Firewall/router appliance lab
Static IP on router/firewall, DHCP for clients
Multi-VM enterprise simulation
Mix of static and DHCP
A common design is:
Infrastructure servers: Static IP
Client machines: DHCP
For example:
DNS Server: 192.168.56.10 static
DHCP Server: 192.168.56.11 static
Web Server: 192.168.56.20 static
Client PCs: 192.168.56.100 - 192.168.56.200 via DHCP
7. Host-Only vs NAT vs Bridged vs Internal Network
VirtualBox provides multiple networking modes. Host-only is only one of them.
7.1 NAT
NAT is often the default networking mode.
The VM can access the Internet through the host, but other computers usually cannot directly access the VM unless port forwarding is configured.
Best for:
Internet access from VM
Simple browsing
Software updates
Basic VM use
7.2 Bridged Adapter
Bridged networking connects the VM directly to the physical network.
The VM behaves like another computer on the same LAN.
Best for:
Making the VM visible to other physical computers
Server testing on the real LAN
Network services that must be reachable by other devices
Risk:
The VM is exposed to the physical network.
DHCP may come from the real router or real network DHCP server.
Some Wi-Fi networks or corporate networks may restrict bridged VMs.
7.3 Internal Network
Internal networking allows VMs to communicate only with other VMs on the same internal network. The host is not part of the network.
Best for:
Very isolated VM-to-VM testing
Security labs
Private backend networks
7.4 Host-Only Network
Host-only networking allows communication between the host and VMs, and between VMs on the same host-only network.
Best for:
Labs
Development
Server testing
Private VM networks where the host still needs access
Image 4: Networking Mode Comparison
flowchart TD
A[VirtualBox Networking Modes]
A --> NAT[NAT<br>VM to Internet through host]
A --> BR[Bridged<br>VM joins physical LAN]
A --> INT[Internal Network<br>VM-to-VM only]
A --> HO[Host-Only<br>Host-to-VM and VM-to-VM]
NAT --> N1[Good for Internet access]
BR --> B1[Good for real LAN visibility]
INT --> I1[Good for isolated VM networks]
HO --> H1[Good for private labs and development]
8. When to Use Multiple Network Adapters
A VM can have more than one network adapter.
For example:
Adapter 1: NAT
Adapter 2: Host-only
This gives the VM:
Internet access through NAT
Private communication with the host and other VMs through host-only
Example design
Web Server VM
Adapter 1: NAT → Internet updates
Adapter 2: Host-only → Private lab network
Image 5: Dual-Adapter VM
flowchart LR
Internet[Internet]
Host[Host Computer]
VM[Virtual Machine<br>Adapter 1: NAT<br>Adapter 2: Host-only]
Private[Host-Only Network<br>Private Lab LAN]
VM --> Internet
Host --- Private
Private --- VM
This setup is useful when you need Internet access but also want an isolated lab network.
9. Creating a Host-Only Network in the VirtualBox GUI
The exact menu names can vary slightly by version and operating system, but the general process is:
Open VirtualBox Manager.
Go to Tools or File → Tools.
Open Network Manager.
Find the Host-Only Networks section.
Create a new host-only network.
Configure the IPv4 address and subnet mask.
Decide whether to enable or disable the VirtualBox DHCP server.
Open the VM settings.
Go to Network.
Enable a network adapter.
Set “Attached to” as Host-only Adapter or Host-only Network.
Select the host-only network name.
Start the VM and configure IP settings inside the guest OS.
Example host-only network configuration:
IPv4 address: 192.168.56.1
IPv4 mask: 255.255.255.0
DHCP: enabled or disabled depending on your purpose
10. Creating or Managing Host-Only Networks with VBoxManage
VBoxManage can be used instead of the GUI.
Useful commands include:
VBoxManage list hostonlyifs
VBoxManage list hostonlynets
VBoxManage list dhcpservers
To configure a VM adapter:
VBoxManage modifyvm "MyVM" --nic1 hostonly
Depending on the VirtualBox version and host platform, host-only networks and host-only interfaces may be managed with commands such as:
The GUI is usually easier for beginners. The command line is better for repeatable lab setup and automation.
11. Should VirtualBox DHCP Be Enabled or Disabled?
It depends on what you want to achieve.
Enable VirtualBox DHCP when:
You want quick automatic IP addresses.
You do not care which DHCP server gives the address.
You are not testing DHCP server configuration.
You want a simple private network with minimal setup.
Disable VirtualBox DHCP when:
You are testing your own DHCP server.
You want to manually assign static IP addresses.
You want to avoid DHCP conflicts.
You need predictable IP addressing.
You are simulating enterprise DHCP behavior.
A good rule:
If the purpose is convenience, VirtualBox DHCP is fine.
If the purpose is learning or testing DHCP, disable VirtualBox DHCP and use your own DHCP server.
12. How to Verify IP Addressing
Inside a Windows guest:
ipconfig /all
Inside a Linux guest:
ip addr
ip route
cat /etc/resolv.conf
From one VM to another:
ping 192.168.56.10
From Windows PowerShell:
Test-Connection 192.168.56.10
Things to check:
IP address
Subnet mask
Default gateway
DNS server
DHCP enabled or disabled
DHCP server address
MAC address
13. Common Host-Only Network Problems
Problem 1: VM gets 169.254.x.x address
A 169.254.x.x address usually means the VM tried to use DHCP but did not receive a response.
Possible causes:
DHCP server is disabled.
DHCP server is not reachable.
VM is connected to the wrong adapter.
Network cable option is unchecked.
Firewall is blocking traffic.
DHCP scope is misconfigured.
Problem 2: VM cannot ping another VM
Check:
Are both VMs on the same host-only network?
Are both VMs in the same IP subnet?
Is the firewall blocking ping?
Is the VM network adapter enabled?
Is the virtual cable connected?
Problem 3: VM gets IP from wrong DHCP server
This can happen if multiple DHCP servers exist on the same network.
Check the DHCP server line:
ipconfig /all
If the DHCP server is not the one you expected, disable the unwanted DHCP server or move the VM to a different virtual network.
Problem 4: Host cannot reach VM
Check:
Host-only adapter exists on the host.
Host-only adapter has the correct IP address.
VM is connected to the same host-only network.
Guest firewall allows the required traffic.
VM IP address is in the same subnet as the host-only adapter.
14. Practical Design Examples
Example 1: Simple Host-to-VM Development
Host: 192.168.56.1
Web VM: 192.168.56.10
Database: 192.168.56.20
The host browser can open:
http://192.168.56.10
The web VM can connect to the database VM privately.
Example 2: Server and Client Lab
Server VM: 192.168.56.10 static
Client VM: 192.168.56.20 static or DHCP
Host: 192.168.56.1
This is useful for practicing DNS, DHCP, file sharing, remote management, and web services.
Example 3: Dual-Network Server
Adapter 1: NAT
Adapter 2: Host-only
The VM uses NAT for updates and host-only networking for private lab communication.
Example 4: Firewall/Router Lab
Firewall VM
Adapter 1: NAT or Bridged
Adapter 2: Host-only
Client VM
Adapter 1: Host-only
The firewall VM can act as a router between the private host-only network and another network.
15. Security Considerations
Host-only networking is safer than bridged networking for many lab situations because the VM is not automatically exposed to the physical LAN.
However, it is not the same as perfect security.
Remember:
The host can communicate with the VMs.
VMs on the same host-only network can communicate with each other.
Services inside VMs may still be reachable from the host.
A dual-adapter VM may connect the private network to another network if routing is enabled.
Firewalls inside the guest operating system still matter.
For sensitive testing, use snapshots and isolated networks carefully.
16. Best Practices
Use static IP addresses for infrastructure machines:
DNS servers
DHCP servers
Domain controllers
Routers
Firewalls
Database servers
Use DHCP for client machines:
Desktop clients
Test clients
Temporary VMs
Use separate host-only networks for separate labs:
Avoid running multiple DHCP servers on the same virtual network unless you are intentionally testing that scenario.
Document your network:
Network name
Subnet
Host adapter IP
DHCP range
Static server IPs
Gateway
DNS server
VM adapter mode
Conclusion
Host-only networking in Oracle VirtualBox is one of the most useful networking modes for building private virtual labs. It gives the host and virtual machines a shared private network while keeping the VMs isolated from the outside network by default.
IP addressing can be handled manually with static addresses, automatically through VirtualBox DHCP, or through a DHCP server running inside a virtual machine. The best choice depends on the purpose of the environment.
For quick testing, VirtualBox DHCP is convenient. For server administration, networking, and enterprise simulation, static IP addresses and a VM-based DHCP server provide more control and realism.
A good host-only network design is simple, documented, and intentional. Decide which machines need static IPs, which machines should use DHCP, whether Internet access is needed, and whether the host should be able to access the services inside the VMs.