Menu

#141 Export to DHCP/Bind/DNSmasq

Next_Release
open
nobody
None
1
2020-02-10
2013-07-05
No

Please add the ability to export to more tools such as the ones listed in the title.

I have attached some basic versions of an exporter but they are most likely buggy. They run from the basedir and don't require authentication, perfect for using wget or curl in a shell script that also restarts the service.

1 Attachments

Related

Feature Requests: #141

Discussion

  • Scott Peters

    Scott Peters - 2013-07-05

    bind and dnsmasq

     

    Last edit: Scott Peters 2013-07-05
  • Jay Allen

    Jay Allen - 2015-01-21

    I would certainly like to see exports to or integration with DNS and DHCP services.

     
  • Anonymous

    Anonymous - 2015-01-21

    why not use http://bind-dlz.sourceforge.net/ to interact with DB "directly" ?

     
  • Jay Allen

    Jay Allen - 2015-01-28

    I've attached a trivial example that makes ISC DHCP style configs too. Its logic is that it looks for subnets described as "DHCP range", as the default example data does for one subnet.

     
  • Miha Petkovsek

    Miha Petkovsek - 2015-01-28

    Hi, I plan to somehow include DNS/DHCP into phpipam, I am just not sure yet how to do it properly for all users and as simple as possible.

    DNS:
    Exporting is not a problem I guess, bind-dlz looks promising but kinda hard to implement.

    PowerDNS seems to be a really good solution, I know some sysadmins that use it happily, it has native MySQL support, I could also write a GUI to manage zones etc from phpipam directly, binding hostnames to IP addresses etc. Exporting to binds zone files from DB should be easy if bind is required.
    https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/

    DHCP:
    I guess for DHCP only exporting is an option, I would go this way:
    - enable/disable DHCP support globally under settings;
    - mark specific subnet as DHCP exportable;
    - gateway marking will be available soon so GW per subnet will be selected;
    - set default DHCP settings per subnet (lease-time,...), saved to DB as JSON key-vals;
    - new button that would popup with config file, with download button and cron script to generate configs in terminal.

    I am rewriting all functions at the moment, after that I will focus on those features.

    brm

     
    • Anonymous

      Anonymous - 2015-01-29

      For DNS exports/integraton I assumed targeting Bind9 made sense because its
      intended to be a reference implementation of the standard. Bind is also
      bundled with just about everything Unix like, but not all have DLZ builtin.
      That said, PowerDNS is already packaged with Ubuntu server. I see
      PowerDNS in the Fedora 20 default repos. Unfortunately its not in default
      Centos 7. Its very easy to compile from source and is distributed as
      DEBs/RPMs on the home web site. At a service provider I've seen PowerDNS
      take tens of megabits of steady queries... works great! If you like
      PowerDNS, go for it!

      DHCP, in my mind is the same story standards/reference wise. You might be
      interested in the new Kea project at ISC. Its a brand new implementation
      of DHCP services, with native database support. Its not ready for
      production yet. http://kea.isc.org/wiki

      I like you ideas about implementation. there are a million knobs on DNS
      and DHCP, but if you aim at a minimal feature complete example, it can
      evolve from there? Maybe a generic way to add arbitrary default config
      grammar?

      Regards,

      Jay Allen

      On Wed, Jan 28, 2015 at 11:10 AM, Miha Petkovsek myha@users.sf.net wrote:

      Hi, I plan to somehow include DNS/DHCP into phpipam, I am just not sure
      yet how to do it properly for all users and as simple as possible.

      DNS:
      Exporting is not a problem I guess, bind-dlz looks promising but kinda
      hard to implement.

      PowerDNS seems to be a really good solution, I know some sysadmins that
      use it happily, it has native MySQL support, I could also write a GUI to
      manage zones etc from phpipam directly, binding hostnames to IP addresses
      etc. Exporting to binds zone files from DB should be easy if bind is
      required.
      https://doc.powerdns.com/md/authoritative/backend-generic-mypgsql/

      DHCP:
      I guess for DHCP only exporting is an option, I would go this way:
      - enable/disable DHCP support globally under settings;
      - mark specific subnet as DHCP exportable;
      - gateway marking will be available soon so GW per subnet will be selected;
      - set default DHCP settings per subnet (lease-time,...), saved to DB as
      JSON key-vals;
      - new button that would popup with config file, with download button and
      cron script to generate configs in terminal.

      I am rewriting all functions at the moment, after that I will focus on
      those features.

      brm

      Status: open
      Group: Next_Release
      Created: Fri Jul 05, 2013 08:08 PM UTC by Scott Peters
      Last Updated: Wed Jan 28, 2015 06:46 AM UTC
      Owner: nobody

      Please add the ability to export to more tools such as the ones listed in
      the title.

      I have attached some basic versions of an exporter but they are most
      likely buggy. They run from the basedir and don't require authentication,
      perfect for using wget or curl in a shell script that also restarts the
      service.


      Sent from sourceforge.net because you indicated interest in
      https://sourceforge.net/p/phpipam/feature-requests/141/

      To unsubscribe from further messages, please visit
      https://sourceforge.net/auth/subscriptions/

       

      Related

      Feature Requests: #141

  • Anonymous

    Anonymous - 2016-01-13
    Post awaiting moderation.
  • Anonymous

    Anonymous - 2018-07-01
    Post awaiting moderation.

Anonymous
Anonymous

Add attachments
Cancel





Want the latest updates on software, tech news, and AI?
Get latest updates about software, tech news, and AI from SourceForge directly in your inbox once a month.