Saucepan

User Tools

Site Tools

Trace: • bash • dhcp • install_tigervnc • install_apex_ssl • ping • wireshark • deploy_reporting_vm
infoblox_nios:ddns

Differences

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

Link to this comparison view

Both sides previous revisionPrevious revision
Next revision		Previous revision
infoblox_nios:ddns [2024/06/21 13:21] – bstaffordinfoblox_nios:ddns [2025/03/05 11:43] (current) – [Dynamic DNS] bstafford
Line 1: Line 1:
 ======= Dynamic DNS ====== ======= Dynamic DNS ======
 +
 +NIOS DDNS Updates are processed by the primary member, synced to GM, GM then pushes to secondaries. If GM is offline, secondaries don't get data. If Secondary if offline, GM will queue until it is back online. For NIOS-X, members proxy DDNS update to cloud, cloud processes change, cloud pushes to all NIOS-X members. Cloud only queues for a few seconds. If NIOS-X host is offline, it won't get the updates.
  
 DHCP can be impacted by separate DNS appliances. DHCP pauses lease issuing until a DDNS update is completed. DHCP can be impacted by separate DNS appliances. DHCP pauses lease issuing until a DDNS update is completed.
Line 18: Line 20:
  
 For NIOS DHCP updating a NIOS zone, TSIG is used for the updates, and there is a zone {} statement at the bottom of dhcpd.conf that explicitly says where to send updates.  If you're using multiple primaries for a zone, you can specify which primary will get the updates.  See [[https://docs.infoblox.com/space/nios90/280762554/Configuring+DHCP+for+DDNS#Defining-the-Default-Primary-for-DDNS-Updates-to-Zones-with-Multiple-Primaries|Defining the Default Primary for DDNS Updates to Zones with Multiple Primaries]]. For NIOS DHCP updating a NIOS zone, TSIG is used for the updates, and there is a zone {} statement at the bottom of dhcpd.conf that explicitly says where to send updates.  If you're using multiple primaries for a zone, you can specify which primary will get the updates.  See [[https://docs.infoblox.com/space/nios90/280762554/Configuring+DHCP+for+DDNS#Defining-the-Default-Primary-for-DDNS-Updates-to-Zones-with-Multiple-Primaries|Defining the Default Primary for DDNS Updates to Zones with Multiple Primaries]].
 +
 +===== TXT Record Handling =====
 +  * **Standard ISC (Strictest)**. Only create record if no A record exists already or, if one does exist, only update the existing record if the new TXT matches existing TXT.
 +  * **Check-Only (Less Strict)**. Only create record if no A record exists already or, if one does exist, only update the existing record if there is a TXT record for it as well (regardless of whether the TXT records match).
 +  * **ISC Transitional (Temporary)**. No checks in place. Should only be used during a migration. Then change to ISC or Check-Only.
 +  * **No TXT Record**. This method should be used with caution because anyone can send DDNS updates and overwrite records. This method is useful when both ISC and non-ISC-based DHCP servers and clients are updating the same zone.
  
 ===== Hosts ===== ===== Hosts =====
Line 25: Line 33:
  
 Note: The DDNS update will use the hostname provided by the client (not the name typed into the Host record) Note: The DDNS update will use the hostname provided by the client (not the name typed into the Host record)
 +===== Protect Records from DDNS =====
 +Under Data Management > DNS Grid DNS Properties > Updates > Advanced.
 +  * Prevent dynamic updates to RRsets containing static records
 +  * Prevent dynamic updates to RRsets containing protected records
 +
  
  
Line 35: Line 48:
  
 If the SOA MNAME records points to a hidden server, NIOS may choose one of the NS servers instead. This was seen once in a multi-master configuration. If the SOA MNAME records points to a hidden server, NIOS may choose one of the NS servers instead. This was seen once in a multi-master configuration.
 +
 +===== Domain Controllers =====
 +If you add a domain controller to a Microsoft Active Directory domain and find that the new domain controller cannot update records in DNS (e.g. NIOS DNS), make sure you enable the 'register in DNS' setting in the TCP/IP settings of the domain controller's network interface. If you do not, you may see the following error in the NIOS logs.
 +<code>client @0xffffffffffff 192.168.11.22#58685: view 3: updating zone 'ad.domain.com./IN': update unsuccessful: ad.domain.com: 'name not in use' prerequisite not satisfied (YXDOMAIN)</code>
  
 ===== DDNS Update on DHCP Renew===== ===== DDNS Update on DHCP Renew=====
infoblox_nios/ddns.1718976079.txt.gz · Last modified: by bstafford