User Tools

Site Tools


microsoft_windows:dns

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

microsoft_windows:dns [2025/08/24 02:10] – created rodolicomicrosoft_windows:dns [2025/08/24 02:34] (current) rodolico
Line 94: Line 94:
   - Ensure you have the same Domain Name as the DNS Server (ie, the Windows Domain Name)   - Ensure you have the same Domain Name as the DNS Server (ie, the Windows Domain Name)
   - Save, then Apply   - Save, then Apply
 +
 +Note that opnSense says "ISC DHCP is end-of-life and no longer receives updates or security patches. It is strongly recommended to migrate to KEA or Dnsmasq.", however, I was unable to locate the information I needed to set up KEA. However, I'm putting my notes below just in case I want to revisit it.
  
 ==== Using KEA DHCP Server ==== ==== Using KEA DHCP Server ====
Line 147: Line 149:
 Restart KEA after this either via the webui, or with the command <code bash>service kea reload</code> Restart KEA after this either via the webui, or with the command <code bash>service kea reload</code>
  
-Again, this is something I found with duck.io, and it did not give attributions, so I don't know. I did find that others said that KEA will only put staticly defined leases, and will not send notification for dynamic.+Again, this is something I found with duck.io, and it did not give attributions, so I don't know. I did find that others said that KEA will only put staticly defined leases, and will not send notification for dynamic. I did some additional research and it appears the kea-dkcp-ddns service is meant to communicate with Bind9, so that may be something to pursue.
  
 ===== Testing ===== ===== Testing =====
  
 +All you need here is to find a workstation and renew the dhcp lease, then see if it updates the DNS. The following commands do that for you (command line)
 +<code bash>
 +# Windows
 +ipconfig /renew
 +# Unix (just about any of them, including BSD, as root)
 +dhclient -r
 +# Linux using ifconfig, as root
 +ifconfig eth0 down && ifconfig eth0 up
 +# Linux, with systemctl
 +sudo systemctl restart NetworkManager
 +# Linux, with Network Manager, where eth0 is your interface
 +nmcli device reapply eth0
 +# MacOS (where en0 is your interface, use ifconfig to find the name)
 +ipconfig set en0 DHCP
 +</code>
 +
 +Now, simply check the DNS server to see if it has the dhcp lease in it. If not, check your DHCP and DNS logs to see what went wrong.
 +
 +===== Links =====
 +
 +Sorry, I did not keep good track of where I went. I spent a lot of time on [[duck.ai]], but like most AI searches, it gave a lot of bogus information. Here is my 'sorta' list
 +  * https://kb.isc.org/docs/kea-administrator-reference-manual
 +  * https://docs.opnsense.org/manual/isc.html
  
 +  * Unordered List Item
microsoft_windows/dns.txt · Last modified: 2025/08/24 02:34 by rodolico