home.social

#ixfr — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #ixfr, aggregated by home.social.

  1. When building a library, it's not just about providing features but getting the ergonomics right so that developers can take maximum advantage of the functionality provided. After several approaches, we're finally happy with Zone Transfers for our `domain` crate for .
    github.com/NLnetLabs/domain/pu

  2. When building a library, it's not just about providing features but getting the ergonomics right so that developers can take maximum advantage of the functionality provided. After several approaches, we're finally happy with #DNS Zone Transfers for our #OpenSource `domain` crate for #rustlang. #CodingInTheOpen #IXFR #AXFR #TSIG
    github.com/NLnetLabs/domain/pu

  3. When building a library, it's not just about providing features but getting the ergonomics right so that developers can take maximum advantage of the functionality provided. After several approaches, we're finally happy with #DNS Zone Transfers for our #OpenSource `domain` crate for #rustlang. #CodingInTheOpen #IXFR #AXFR #TSIG
    github.com/NLnetLabs/domain/pu

  4. When building a library, it's not just about providing features but getting the ergonomics right so that developers can take maximum advantage of the functionality provided. After several approaches, we're finally happy with #DNS Zone Transfers for our #OpenSource `domain` crate for #rustlang. #CodingInTheOpen #IXFR #AXFR #TSIG
    github.com/NLnetLabs/domain/pu

  5. When building a library, it's not just about providing features but getting the ergonomics right so that developers can take maximum advantage of the functionality provided. After several approaches, we're finally happy with #DNS Zone Transfers for our #OpenSource `domain` crate for #rustlang. #CodingInTheOpen #IXFR #AXFR #TSIG
    github.com/NLnetLabs/domain/pu

  6. @pemensik @[email protected] @mypdns @Alonely0 @floppy_bv

    no, I mean #IXFR. That is incremental zone transfer.

    OK, then I misunderstood your intention. I do recalls it as unbound only support AXFR, but look it up to be sure, it have been some years ago I played with it, as I go with PowerDNS's 3 pkg's on all my instances. (I then have a running copy of my RPZ zones on the laptop when it's not at home 😃 )

    dnsdist is then setup to response from the server if available otherwise it is using the local resources.

  7. @pemensik @[email protected] @mypdns @Alonely0 @floppy_bv

    no, I mean #IXFR. That is incremental zone transfer.

    OK, then I misunderstood your intention. I do recalls it as unbound only support AXFR, but look it up to be sure, it have been some years ago I played with it, as I go with PowerDNS's 3 pkg's on all my instances. (I then have a running copy of my RPZ zones on the laptop when it's not at home 😃 )

    dnsdist is then setup to response from the server if available otherwise it is using the local resources.

  8. @pemensik @[email protected] @mypdns @Alonely0 @floppy_bv

    no, I mean #IXFR. That is incremental zone transfer.

    OK, then I misunderstood your intention. I do recalls it as unbound only support AXFR, but look it up to be sure, it have been some years ago I played with it, as I go with PowerDNS's 3 pkg's on all my instances. (I then have a running copy of my RPZ zones on the laptop when it's not at home 😃 )

    dnsdist is then setup to response from the server if available otherwise it is using the local resources.

  9. @pemensik @[email protected] @mypdns @Alonely0 @floppy_bv

    no, I mean #IXFR. That is incremental zone transfer.

    OK, then I misunderstood your intention. I do recalls it as unbound only support AXFR, but look it up to be sure, it have been some years ago I played with it, as I go with PowerDNS's 3 pkg's on all my instances. (I then have a running copy of my RPZ zones on the laptop when it's not at home 😃 )

    dnsdist is then setup to response from the server if available otherwise it is using the local resources.

  10. @[email protected] @[email protected] @mypdns @Alonely0 @floppy_bv no, I mean #IXFR. That is incremental zone transfer. #Bind9 can do it, not sure #Unbound has that too. Allows to just receiving changes compared to previous version, but need to store journal containing each change at primary and secondary server. Using AXFR is similar to downloading hosts file over http. I think PiHole uses own modified dnsmasq build, which provides webui integration.

  11. @[email protected] @[email protected] @mypdns @Alonely0 @floppy_bv no, I mean . That is incremental zone transfer. can do it, not sure has that too. Allows to just receiving changes compared to previous version, but need to store journal containing each change at primary and secondary server. Using AXFR is similar to downloading hosts file over http. I think PiHole uses own modified dnsmasq build, which provides webui integration.

  12. @[email protected] @[email protected] @mypdns @Alonely0 @floppy_bv no, I mean #IXFR. That is incremental zone transfer. #Bind9 can do it, not sure #Unbound has that too. Allows to just receiving changes compared to previous version, but need to store journal containing each change at primary and secondary server. Using AXFR is similar to downloading hosts file over http. I think PiHole uses own modified dnsmasq build, which provides webui integration.

  13. @[email protected] @[email protected] @mypdns @Alonely0 @floppy_bv no, I mean #IXFR. That is incremental zone transfer. #Bind9 can do it, not sure #Unbound has that too. Allows to just receiving changes compared to previous version, but need to store journal containing each change at primary and secondary server. Using AXFR is similar to downloading hosts file over http. I think PiHole uses own modified dnsmasq build, which provides webui integration.