#46 RevDNS - Export to pad unspecified reverse DNS entries

open
nobody
None
5
2007-11-20
2007-11-20
Larry Low
No

For example range 5.5.5.0 - 5.5.5.255

5.5.5.5 is only host defined

rest of range reverse dns will be 5.5.5.#.ip.tnltd.net

I have attached a patch prototype. Will need to implement this by adding parameters.

Discussion

  • Richard Ellerbrock

    Logged In: YES
    user_id=230197
    Originator: NO

    This will be bind specific? What about other DNS types. This should be handled in the XSL transformation and not hardcoded in the XML generation.

     
  • Nobody/Anonymous

    Logged In: NO

    This is not bind specific. It uses the XML generation to create default entries where no DNS name has been specified in the database. There is no way to iterate through numbers in XSL anyways.

    This would need to be an optional parameter part of the DNS entry. I will also look into having it auto-generate the forward entries as well.

     
  • Richard Ellerbrock

    Logged In: YES
    user_id=230197
    Originator: NO

    You can iterate using XSL - xsl:for-each. You should rather place a parameter in the XML output that the XSL can check for to generate the below notation. I don't want extra hardcoded config.php parameters or buttons on the screens if they are no absolutely necessary. You can then test for the parameter using xsl:if

     
  • Larry Low

    Larry Low - 2007-11-27

    Logged In: YES
    user_id=562270
    Originator: YES

    The problem still is that if no reverse DNS is defined in ipplan then no entry is created in the XML and there is noting to iterate over.

    The only way to do this effectively with the least amount of modification of IPplan is to rewrite the code to just create empty host entries in this case. Then the xsl:if can be used to check if the host tag contains any data.

    The current contrib XSLs will have to be modified to check for this.

    Having default PTR records and their A counterparts can greatly reduce delays caused by reverse/forward lookups many applications perform on client connects.

    I will supply a new patch, updated default XSLs, and a proof of concept XSL when I have a moment. I'll include a perl script that can be used to auto generate the default forwards too.

     
  • Richard Ellerbrock

    Logged In: YES
    user_id=230197
    Originator: NO

    Excellent. I understand the problem - I just have a slight issue with the implementation. Implementation needs to be as portable as possible and not break any existing behavior.

     

Log in to post a comment.

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:





No, thanks