Project

General

Profile

Actions
Copy link

Bug #11101

closed

Bind DNS Server won't start

Added by Danilo Zrenjanin over 3 years ago. Updated over 3 years ago.

Status:
Resolved
Priority:
Low
Assignee:
Viktor Gurov
Category:
BIND
Target version:
-
Start date:
11/25/2020
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Affected Version:
Affected Plus Version:
Affected Architecture:

Description

If the "Enable Forwarding" checkbox is enabled, and a Forwarder IP is defined, and there is no semicolon at the end, the service will fail to start.

There is a comment at the bottom of the screen referencing that semicolon is necessary at the end; it still can easily be overseen.

I would recommend adding an input test for that field.

Actions
Copy link
 #1

Updated by Viktor Gurov over 3 years ago

  • Target version deleted (2.5.0)
Actions
Copy link
 #3

Updated by Renato Botelho over 3 years ago

  • Assignee set to Viktor Gurov

PR has been merged. Thanks!

Actions
Copy link
 #4

Updated by Renato Botelho over 3 years ago

  • Status changed from New to Feedback
Actions
Copy link
 #5

Updated by Azamat Khakimyanov over 3 years ago

  • Status changed from Feedback to Resolved

Tested on 2.4.5_p1 and on 2.5-DEVELOPMENT (built on Mon Jan 11 11:12:41 EST 2021).

On 2.4.5_p1 (Bind package version: 9.14_11) and on 2.5-DEV (Bind package version: 9.16_8) there is no difference if you add semicolon at the end of 'Forwarder IPs' field or not, named service starts anyway.

This bug can be marked resolved.

Actions
Copy link

Also available in: Atom PDF