# Changelog

## 1.2.0

Zero-parameter bootstrap and install directory hardening.

- `bootstrap.ps1` reads `DnsServer` and `Domain` from `bootstrap.json` — no required parameters
- Install directory (`C:\Program Files\Nebula`) locked down to SYSTEM and Administrators only — standard users cannot read `host.key`, certs, or config

## 1.1.0

DNS persistence and domain authentication at the login screen.

- `install-nebula.ps1` now requires `-DnsServer` and `-Domain` parameters (passed automatically by bootstrap)
- Nebula service changed from `delayed-auto` to `auto` start — NlaSvc dependency already ensures the physical network is up
- Creates a `NebulaDNS` scheduled task that runs at startup to re-apply DNS on the `nebula1` adapter after Nebula recreates it, wait for the DC to become reachable, and force Netlogon DC rediscovery via `nltest`
- Idempotency check now also verifies the scheduled task and startup script exist
- Removed `ExpectedDialupDelay` — the active `nltest /dsgetdc /force` in the scheduled task makes it unnecessary

## 1.0.0

Initial release.

- `bootstrap.ps1` — Single-command onboarding: installs Nebula, configures DNS, joins Active Directory domain
- `install-nebula.ps1` — Installs Nebula as a Windows service with delayed-auto start and NlaSvc dependency
- `set-dns.ps1` — Configures DNS on the Nebula tunnel adapter only, preserving physical adapter DNS
- `join-domain.ps1` — Joins the domain under the machine's current name with optional computer name validation
- Idempotent: all scripts are safe to re-run without side effects
- Each script can be run independently for fine-grained control
- Pre-staged AD object support: machines renamed before bootstrap auto-match existing computer objects
- Nebula 1.10.3 and WinTun driver downloaded from GitHub at install time (no bundled binaries)