Project

General

Profile

Actions
Copy link

Bug #4675

closed

DHCPv6 DDNS doesn't work properly

Added by Robert Nelson over 9 years ago. Updated almost 9 years ago.

Status:
Resolved
Priority:
High
Assignee:
Renato Botelho
Category:
DHCP (IPv6)
Target version:
2.3
Start date:
05/05/2015
Due date:
% Done:

100%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
All
Affected Architecture:
All

Description

There are three issues:
- The wrong domain was being used, domain instead of ddnsdomain.
- The option "deny client-updates" wasn't being set so forward entries weren't being added.
- No zone information was provided for reverse DNS.

I've submitted PR # 1634 with fixes.

Actions
Copy link
 #1

Updated by Robert Nelson over 9 years ago

For the second issue I updated my PR to allow it to be configured between allow, deny and ignore.

Actions
Copy link
 #2

Updated by Chris Buechler over 9 years ago

  • Target version set to 2.2.3
  • Affected Version changed from 2.2.3 to All
Actions
Copy link
 #3

Updated by Chris Buechler over 9 years ago

  • Status changed from New to Confirmed
  • Priority changed from Normal to High
  • Target version changed from 2.2.3 to 2.3
  • % Done changed from 100 to 80

Thanks Robert, we'll get that reviewed, tested and merged soon for 2.3.

Actions
Copy link
 #4

Updated by Jim Thompson about 9 years ago

  • Assignee set to Renato Botelho
Actions
Copy link
 #5

Updated by Chris Buechler almost 9 years ago

  • Assignee changed from Renato Botelho to Chris Buechler

looking at this as part of PR 1638

Actions
Copy link
 #6

Updated by Jim Thompson almost 9 years ago

  • Assignee changed from Chris Buechler to Renato Botelho
Actions
Copy link
 #7

Updated by Renato Botelho almost 9 years ago

  • Status changed from Confirmed to Feedback
  • % Done changed from 80 to 100
Actions
Copy link
 #8

Updated by Chris Buechler almost 9 years ago

  • Status changed from Feedback to Resolved

works

Actions
Copy link

Also available in: Atom PDF