ERROR -> Only PTR records should use in-addr domains! Why???
quijada
15-07-2009 04:15:04
Hi, I need to add NS records to the reverse zones, in the DNS Server of my organization is done like that.
An example can be:
19.172.in-addr.arpa. NS unimur.um.es
However, everytime I want to add it, ONA says that Only PTR records should use in-addr domains
How can I solve this?
I have just migrated all my old database (for several weeks) to ONA and I think I cannot continue with this trouble
Thank you.
P.D.: I have tried this with dcm.pl but I get the same result.
An example can be:
19.172.in-addr.arpa. NS unimur.um.es
However, everytime I want to add it, ONA says that Only PTR records should use in-addr domains
How can I solve this?
I have just migrated all my old database (for several weeks) to ONA and I think I cannot continue with this trouble
Thank you.
P.D.: I have tried this with dcm.pl but I get the same result.
Matt
15-07-2009 07:42:06
Yes an NS record is required for pretty much every zone that is created. It is not exactly obvious within ONA that the NS records are handled automatically by assigning a DNS server host to a domain.
There are three ways to do this. Navigate to your unimur.um.es host in ONA and then click on the DNS line of "managed services on this host". On the next screen you will assign all of the domains that this server is either a master or secondary for. When you do this, an NS record will automatically be created for the domain.
The second way is to navigate to the 19.172.in-addr.arpa domain and then click the "assign to server" button in the DNS servers box.
The last way is via DCM using the "domain_server_XXX" commands.
Hope that helps.
There are three ways to do this. Navigate to your unimur.um.es host in ONA and then click on the DNS line of "managed services on this host". On the next screen you will assign all of the domains that this server is either a master or secondary for. When you do this, an NS record will automatically be created for the domain.
The second way is to navigate to the 19.172.in-addr.arpa domain and then click the "assign to server" button in the DNS servers box.
The last way is via DCM using the "domain_server_XXX" commands.
Hope that helps.
quijada
16-07-2009 05:00:39
Hi Matt, if you remember, we was talking about this last night. Now, I am at work and I have just tried all ways you told me (even adding an NS server for a reverse zone in-addr... with dcm.pl) but I get the same result, only PTR records bla bla bla...
As I told you last conversation, I have been looking for some IF condition about this issue, founding it easily. This is the change I have made in the file '/opt/ona/www/modules/ona/dns_record.inc.php', at line 173:
if (strpos($domain['fqdn'], "in-addr.arpa") and $options['type'] != 'PTR' and $options['type'] != 'NS') {
printmsg("ERROR => Only PTR records should use in-addr.arpa domains!", 3);
...
...
}
Of course, the new code is the bold portion.
At the moment, this is the solution for me. I think (as you told me) that the next release will patch this.
I hope this helps somebody too.
Thank you for your help, Matt.
As I told you last conversation, I have been looking for some IF condition about this issue, founding it easily. This is the change I have made in the file '/opt/ona/www/modules/ona/dns_record.inc.php', at line 173:
if (strpos($domain['fqdn'], "in-addr.arpa") and $options['type'] != 'PTR' and $options['type'] != 'NS') {
printmsg("ERROR => Only PTR records should use in-addr.arpa domains!", 3);
...
...
}
Of course, the new code is the bold portion.
At the moment, this is the solution for me. I think (as you told me) that the next release will patch this.
I hope this helps somebody too.
Thank you for your help, Matt.
Matt
16-07-2009 07:45:48
Yep, that is pretty much the fix that needed to happen.. I released the new version last night however so you might want to go ahead and upgrade to it as well since it fixes that and many other things.. Thanks.