Project

General

Profile

Actions

Feature #10274

closed

Add option to avoid sending server statement to nsupdate

Added by Lukas Zapletal over 9 years ago. Updated over 9 years ago.

Status:
Duplicate
Priority:
Normal
Assignee:
-
Category:
DNS
Target version:
-
Difficulty:
easy
Triaged:
Fixed in Releases:
Found in Releases:

Description

There are deployments with primary zones on multiple DNS servers. It is possible to achieve this configuration but foreman-proxy prevents the updates because it has "server @server" hardcoded in the codebase. The feature is all about adding extra nsupdate option "dns_nsupdate_send_server" or similar allowing users to turn off this behavior. From the manpage:

server {servername} [port]

Sends all dynamic update requests to the name server servername. When no server statement is provided, nsupdate will send updates to the master server of the correct zone. The MNAME field of that zone's SOA record will identify the master server for that zone. port is the port number on servername where the dynamic update requests get sent. If no port number is specified, the default DNS port number of 53 is used.


Related issues 1 (0 open1 closed)

Is duplicate of Smart Proxy - Bug #2720: smart-proxy DNS doesn't work with multiple DNS servers because of default value for 'dns_server' optionRejectedActions
Actions #1

Updated by Dominic Cleal over 9 years ago

  • Is duplicate of Bug #2720: smart-proxy DNS doesn't work with multiple DNS servers because of default value for 'dns_server' option added
Actions #2

Updated by Dominic Cleal over 9 years ago

  • Status changed from New to Duplicate
Actions

Also available in: Atom PDF