Project

General

Profile

Bug #10882

DHCPv6 Static Mappings requires applying changes on DNS resolver setup

Added by Danilo Zrenjanin about 2 months ago. Updated about 16 hours ago.

Status:
Resolved
Priority:
Normal
Category:
DHCP (IPv6)
Target version:
Start date:
09/09/2020
Due date:
% Done:

100%

Estimated time:
Affected Version:
All
Affected Architecture:

Description

I noticed that the hostname entered into DHCPv6 Static Mappings have not been resolvable until I applied changes at the DNS resolver setup. (It's the same situation with DNS Forwarder)

Every time I add an entry (or make any changes to an existing one) into DHCPv6 Static Mappings, the apply button automatically appears at the DNS resolver setup(Services/DNS Resolver/General Settings). The host becomes resolvable only after apply.

I used Static IPv6 Configuration on the LAN interface.

*Options enabled at the DNS Resolver: *

  • Static DHCP
  • DNS Query Forwarding

Associated revisions

Revision 916fa8f9 (diff)
Added by Viktor Gurov about 2 months ago

DHCPv6 Static Mapping fix. Issue #10882

History

#2 Updated by Jim Pingle about 2 months ago

  • Status changed from New to Pull Request Review

#3 Updated by Renato Botelho about 1 month ago

  • Status changed from Pull Request Review to Feedback
  • Assignee set to Renato Botelho
  • % Done changed from 0 to 100

PR has been merged. Thanks!

#4 Updated by Danilo Zrenjanin about 1 month ago

  • Status changed from Feedback to Resolved

Added the patch on the:

2.4.5-RELEASE-p1 (arm)
built on Tue Jun 02 17:45:24 EDT 2020
FreeBSD 11.3-STABLE

Issue fixed. Ticket resolved.

#5 Updated by Jim Pingle about 16 hours ago

  • Category changed from DNS Resolver to DHCP (IPv6)

Also available in: Atom PDF