Repository navigation
bind external DNS zone config #86
Copy link
Copy link
Closed
Description
Activity
I don't think this is the right repository for this issue?
- added a commit that references this issue
on Apr 28, 2021 - added 2 commits that reference this issue
on May 27, 2021 - added a commit that references this issue
on Sep 8, 2021 - added a commit that references this issue
on Nov 29, 2021 - added 2 commits that reference this issue
on Feb 12, 2022 - added a commit that references this issue
on Apr 20, 2022 - added a commit that references this issue
on Aug 1, 2022 - added a commit that references this issue
on Aug 11, 2022 - added a commit that references this issue
on Nov 14, 2022 - added a commit that references this issue
on Jan 3, 2023 - added a commit that references this issue
on Jan 18, 2023 131 remaining items
- added 4 commits that reference this issue
on May 15, 2026 - added 2 commits that reference this issue
on May 21, 2026 - added a commit that references this issue
on Jun 10, 2026 - added a commit that references this issue
on Jun 24, 2026 - added a commit that references this issue
on Jul 14, 2026 - added 3 commits that reference this issue
on Jul 26, 2026 - added a commit that references this issue
on Sep 12, 2026 - added a commit that references this issue
on Sep 22, 2026 - added a commit that references this issue
on Oct 2, 2026
Metadata
Metadata
Assignees
Labels
No labels
Hi, i am a pfsense user. I have the last stable version of this magnificent Firewall(and more), but i'm dealing with an issue about BindDNS package and the name.conf file. The thing is that i have a WAN subnet with /29 and when i define my reverse zone, everything goes well, but when i restart de service using the pfsense interface something goes wrong with the name.conf file because for some reason this file has an error in the line 48, the /240 doesn't have to be there:
the correct way will be:
and because of that i have to fixit manually every time the service restart. All of this is happening on Unix/linux, and for Unix/linux the / symbol is a delimiter for files path, and that is the reason why the reference to the area is lost, because with that description, it tries to find the area in the / 240 directory which does not exist
Can you helpme ?
thanks in advance