# DNS Configuration

## Windows DNS Server (AD-Integrated)
- Server: SERVER (10.0.0.5)
- Role: Primary DNS for kittle.lan domain
- DNS Client: 127.0.0.1 (correct — DC points to itself)

## DNS Forwarders
- Forwarder 1: 10.0.0.1 (ISP router — for external resolution)

## DNS Zones

| Zone | Type | AD-Integrated | Notes |
|------|------|---------------|-------|
| kittle.lan | Primary | Yes | Main AD zone |
| _msdcs.kittle.lan | Primary | Yes | AD metadata zone (SRV records) |

**No reverse lookup zone exists for 10.0.0.x** — PTR lookups will fail for all internal hosts.

## DNS Architecture
- **Windows DNS** (10.0.0.5): Authoritative for kittle.lan. Handles AD SRV records, Kerberos, LDAP lookups.
- **ISP Router** (10.0.0.1): Acts as forwarder for external (internet) DNS resolution.
- Workstations should use 10.0.0.5 as primary DNS (the DC) so AD name resolution works correctly.
- If workstations are getting DNS from DHCP on the ISP router, they may be pointed at the ISP's DNS instead of the DC — needs verification.

## External DNS
- Registrar: Unknown
- Primary Domain: kittlearizona.com
- Management URL: Unknown

## Issues
1. **No reverse DNS zone** — Create 0.0.10.in-addr.arpa for PTR lookups on 10.0.0.0/24
2. **DHCP DNS settings unknown** — ISP router handles DHCP; unclear if it hands out 10.0.0.5 as DNS or the ISP's own DNS servers. If clients don't use the DC for DNS, AD name resolution and domain joins may have issues.
3. **Single forwarder** — Only forwarding to 10.0.0.1. Consider adding a secondary forwarder (8.8.8.8 or 1.1.1.1) for redundancy if the ISP router's DNS fails.

## TODO
- [ ] Create reverse lookup zone: 0.0.10.in-addr.arpa
- [ ] Verify what DNS server DHCP clients receive from the ISP router
- [ ] Consider adding secondary DNS forwarder for redundancy
- [ ] Enable DNS scavenging to prevent stale records
- [ ] Document external DNS (registrar, MX records, SPF/DKIM/DMARC for kittlearizona.com)
