Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[ISSUE] SOA record not created #435

torrycrass opened this Issue Mar 17, 2019 · 1 comment


None yet
2 participants
Copy link

torrycrass commented Mar 17, 2019

Please prefix your issue title with one of the following: [BUG], [ISSUE], [FEATURE REQUEST], [MODULE REQUEST], [OTHER].

Replace everything between stars with current version of your facileManager and module installations:
fM Version : 3.4
{DNS} Version : 3.3

In raising this issue, I confirm the following (please check boxes, eg [X]):

  • I have read and understood the contributors guide.
  • I have checked that the bug-fix I am reporting can be replicated, or that the feature I am suggesting isn't already present.
  • I have checked that the issue I'm posting isn't already reported.
  • I have checked that the issue I'm posting isn't already solved and no duplicates exist in closed issues and opened issues
  • I have checked the pull requests tab for existing solutions/implementations to my issue/suggestion.

(BUG | ISSUE) Expected Behavior:
When creating an SOA record via the web interface it shows the validate screen and then should save the record and display the SOA record if validation succeeded.


Creation of the SOA template should also save a template of the SOA record being worked on.

(BUG | ISSUE) Actual Behavior:
SOA record is filled out, validation screen is shown, but the record is not saved.


When performing the same function to create an SOA template no SOA entry is saved either.

(BUG | ISSUE) Steps to reproduce:
Log into web portal fm 3.4 / fmdns 3.3, open a forward zone file, it will state that an SOA record needs to be created. Fill in the requested data. Click on validate. Click on submit. Notice no record created.

The system appears to have a problem with SOA records. Attempting to use them in any way seems to fail out. I am using the SSH method of updating records (which was mentioned as a possible fix quite a while ago) but that does not appear to be helping. I can create A and NS records, import zone files as well but even on zone import the SOA record is not created.

Am I missing something that I would need to enable SOA to function properly? Thank you!


This comment has been minimized.

Copy link

WillyXJ commented Mar 17, 2019

This is now fixed in fmDNS 3.3.1 and later.

@WillyXJ WillyXJ closed this Mar 17, 2019

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
You can’t perform that action at this time.