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

Added new functionality to autogenerate forward (A) PowerDNS records #2705

Open
wants to merge 4 commits into
base: master
Choose a base branch
from

Conversation

AlejandroGlezPerez
Copy link
Contributor

[Enhancement] Add an option to auto-create A record for ipaddress (enhancement #724)

Allows to create forward ('A') records automatically as well as reverse ('PTR') records on PDNS. Regenerating records also regenerates forward records if option activated.

@bmonkey35
Copy link

+1

@lotosdenta
Copy link

Small question about logic:

So lets say we basically have the domain "example.com" with the ip address ranges 10.1.x.0/24, where x varies. If I add a new host, the PTR record will be created first. The domain in this case would be something like: x.1.10.in-addr.arpa (the reverse domain basically).

Now what you do is the following: After creating the PTR you put the A record also in x.1.10.in-addr.arpa which to my knowledge is incorrect. It should instead be placed in the domain "example.com" or am I totally wrong on this end? Because if I now want to resolve name.example.com I would get a REFUSED back from the server, because the entry wasn't found.

Cheers and thanks for the auto create forward button.

@qqmax7
Copy link

qqmax7 commented May 25, 2020

Small question about logic:

So lets say we basically have the domain "example.com" with the ip address ranges 10.1.x.0/24, where x varies. If I add a new host, the PTR record will be created first. The domain in this case would be something like: x.1.10.in-addr.arpa (the reverse domain basically).

Now what you do is the following: After creating the PTR you put the A record also in x.1.10.in-addr.arpa which to my knowledge is incorrect. It should instead be placed in the domain "example.com" or am I totally wrong on this end? Because if I now want to resolve name.example.com I would get a REFUSED back from the server, because the entry wasn't found.

Cheers and thanks for the auto create forward button.

This is a very good pull request, but
dns resolving do not work because

  • verification of the existing, and use of the main domain_ID of powerDNS is necessary.

I am add this future (autogeterate A record) in my project, and, because i'm bad in php, i hardcode in
./functions/classes/class.PowerDNS.php
my current main domain_id.

I think that

  • add field in API replay for forward record same as PTRrecord.
    is necessary.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

4 participants