Bug 218790 - [PATCH] dns/bind99 errors in sample named.conf
Summary: [PATCH] dns/bind99 errors in sample named.conf
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: Any Any
: --- Affects Many People
Assignee: Mathieu Arnold
URL:
Keywords: patch
Depends on:
Blocks:
 
Reported: 2017-04-21 10:13 UTC by Helge Oldach
Modified: 2018-01-30 13:17 UTC (History)
2 users (show)

See Also:
bugzilla: maintainer-feedback? (mat)

Attachments
patch (516 bytes, patch)
2017-04-21 10:14 UTC, Helge Oldach 		no flags Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Helge Oldach 2017-04-21 10:13:54 UTC 
There are syntax errors in the sample named.conf files for the bind99 port (perhaps also for the other BIND ports, didn't check). Trivial patch attached.
Comment 1 Helge Oldach 2017-04-21 10:14:26 UTC 
Created attachment 181971 [details]
patch
Comment 2 Mathieu Arnold freebsd_committer freebsd_triage 2017-04-21 11:52:49 UTC 
I fail to see how it could be a syntax error, it is a commented out section ;-)
Comment 3 Helge Oldach 2017-04-21 12:17:39 UTC 
(In reply to Mathieu Arnold from comment #2)
Sure it is commented out in the template, but if you uncomment that section (which is why it is left in the template after all), named just won't start. Arguing on that line, I would suggest to remove the commented-out section...
Comment 4 Mathieu Arnold freebsd_committer freebsd_triage 2017-04-21 13:22:36 UTC 
No, I agree that it should be fixed, I'll try to not forget it next time I update the BIND9 ports.
Comment 5 Walter Schwarzenfeld freebsd_triage 2018-01-10 03:15:20 UTC 
named.conf.in shows
 131         };
    132         notify no;
    133 };
    134 zone "ip6.arpa" {
    135         type slave;
    136         file "%%ETCDIR%%/slave/ip6.arpa.slave";
    137         masters {
    138                 192.0.32.132;           // lax.xfr.dns.icann.org
    139                 2620:0:2d0:202::132;    // lax.xfr.dns.icann.org
    140                 192.0.47.132;           // iad.xfr.dns.icann.org
    141                 2620:0:2830:202::132;   // iad.xfr.dns.icann.org
    142         };
    143         notify no;
    144 };

It is done, could be closed.
Comment 6 Mathieu Arnold freebsd_committer freebsd_triage 2018-01-30 13:17:18 UTC 
This was fixed in ports r443607.