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

[BUG] import tool : importation of NS record for hosts fail if no TTL is set in reverse zone #378

5 tasks done
cahluor opened this issue Jun 12, 2017 · 2 comments
5 tasks done


Copy link

@cahluor cahluor commented Jun 12, 2017

fM Version : 2.3.3
fmDNS Version : 2.2.6

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:

Import correct records with no explicit TTL

(BUG | ISSUE) Actual Behavior:

Import incorrect records with false TTL

(BUG | ISSUE) Steps to reproduce:

import a file in a reverse zone with delegated NS entry without explicit TTL

When importing a bind reverse zone file with NS records which are not for the zone but for a specific host, if there is no explicit TTL on the entry, the import tool take the last imported entry as new entry name and current entry as TTL.
Well the sentence is not clear so here is an example :

records in imported files :
100 IN PRT
101 IN NS
102 IN NS

records as interpretted by the import tool :
Record TTL CLASS Type Value
100 IN PTR
100 101 IN NS
100 102 IN NS

Copy link

@WillyXJ WillyXJ commented Jun 21, 2017

Thanks for the report. I'm not sure how to fix this so the import tool can automatically (and accurately) detect the record. You can always edit the entry in the confirmation box before importing. I'm also open to other ideas.

Copy link

@WillyXJ WillyXJ commented Mar 17, 2019

This is now fixed in fmDNS 3.3 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
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants