Project

General

Profile

Feature #8234

DHCP server should be able to advertise interface IP automatically even with alternative DNS service

Added by Alfred Barnat over 2 years ago. Updated 10 months ago.

Status:
Rejected
Priority:
Normal
Assignee:
-
Category:
DHCP Server
Target version:
-
Start date:
12/22/2017
Due date:
% Done:

0%

Estimated time:

Description

The text below the "DNS servers" fields on the DHCP server configuration reads "Leave blank to use the system default DNS servers: this interface's IP if DNS Forwarder or Resolver is enabled, otherwise the servers configured on the System / General Setup page.".

This is limiting, when using an alternative DNS service (such as the BIND package), especially for IPv6 where IPs are likely not to be static. There should be a way to access the later part of this functionality, advertising the interface IP as the DNS server, even without the DNS forwarder or resolver packages enabled.

History

#1 Updated by Jim Pingle 10 months ago

  • Status changed from New to Rejected

There is no way for a the base system to know such a service is available from a package, and since you can just type in the IP address manually in these cases, it seems like adding in some kind of hook/plugin here would be a lot of work for very little benefit.

#2 Updated by Alfred Barnat 10 months ago

Apologies, but I'm going to file this issue again. The request is for a checkbox to tell the DHCP server to advertise an interface's IP address as the DNS server rather than defaulting to the servers configured on the System / General Setup page, as the servers used by the router for DNS resolution may well not be what you want to advertise to clients. This does not require any knowledge of the fact that a DNS server is or is not running on the interface; if one isn't, then DNS resolution will be broken on DHCP clients and that's an issue the admin can deal with.

Also available in: Atom PDF