RE: djbdns

From: Wolfpaw - Dale Corse (admin-lists_at_wolfpaw.net)
Date: 12/12/03

  • Next message: Jason Fesler: "RE: djbdns" 
    To: <freebsd-isp@freebsd.org>
Date: Thu, 11 Dec 2003 22:23:16 -0700

    How does djbdns measure up to bind anyway? Bind works wonderfully
    for us.. any reasons someone can come up with (other then the beaten
    to deal security arguments) why a person should change over?

    Thanks in advance :)
    D.
    --------------------------------
    Dale Corse
    System Administrator
    Wolfpaw Services Inc.
    http://www.wolfpaw.net
    (780) 474-4095

    > -----Original Message-----
    > From: owner-freebsd-isp@freebsd.org
    > [mailto:owner-freebsd-isp@freebsd.org]On Behalf Of Greg
    > Cirino - Cirelle
    > Enterprises
    > Sent: Thursday, December 11, 2003 5:18 PM
    > To: ::::Carlos:::Ariel:::Canta::::::::
    > Cc: freebsd-isp@freebsd.org
    > Subject: Re: djbdns
    >
    >
    > | > But my clients use de same ip for cache(dnscahe=my
    > actully public ip) and
    >
    > The basic logic for djbdns
    >
    > tinydns - authorative IP
    > axfrdns - authorative IP
    >
    > dnscache - alternate IP
    >
    > tinydns used for resolving domains you own on UDP
    > axfrdns used for accepting requests from TCP (larger than 512)
    >
    > dnscache used for resolving the internet (and your
    > authorative domains)
    >
    > Let's say your authorative domain server is registered with
    > the internic as
    > NS.YOURDOMAIN.COM at IP 1.2.3.4 (this only contains domains
    > you host)
    >
    > tinydns should listen to 1.2.3.4
    > axfrdns should listen to 1.2.3.4
    >
    > dnscache needs to be on a different IP (i.e. 1.2.3.5)
    >
    > If you want your internal servers/workstations to be able
    > to resolve the internet
    > you will need to change all primary dns entries in
    > resolv.conf (or network on
    > windows machines) to the IP of dnscache (in this case 1.2.3.5).
    >
    > A good reference can be found at:
    > http://lifewithdjbdns.org/
    >
    > HTH
    > Greg
    >
    > _______________________________________________
    > freebsd-isp@freebsd.org mailing list
    > http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    > To unsubscribe, send any mail to
    > "freebsd-isp-unsubscribe@freebsd.org"
    >
    _______________________________________________
    freebsd-isp@freebsd.org mailing list
    http://lists.freebsd.org/mailman/listinfo/freebsd-isp
    To unsubscribe, send any mail to "freebsd-isp-unsubscribe@freebsd.org"

  • Next message: Jason Fesler: "RE: djbdns"

    Relevant Pages

    • Re: Two DNS servers with one IP address
      ... >> Is it possible to have two DNS servers with only one public IP address? ... Serve one set of data to the Internet ... I believe BIND can do this, but I haven't used it for this. ... using the "djbdns" suite which has this built in. ...
      (freebsd-questions)
    • Re: BIND split dns
      ... > I've been trying to make bind split dns work, and i'd been reading a lot ... > whereas if the same site is accessed from the internet my public ip ... > internal and external DNS traffic. ... I am assuming you're running bind 9. ...
      (RedHat)
    • Re: Bind reagiert nicht auf reverse IPv6 Zonen?
      ... funktionieren. ... Im Internet hab ich auch nix dazu gefunden, dass Bind (9.3.4, Debian ...
      (de.comp.os.unix.networking.misc)
    • CERT Advisory CA-2002-15 Denial-of-Service Vulnerability in ISC BIND 9
      ... ISC BIND versions 8 and 4 are not affected. ... vulnerability will cause the BIND server to shut down. ... A vulnerability exists in version 9 of BIND ... The CERT Coordination Center thanks the Internet Software Consortium ...
      (Cert)
    • CERT Advisory CA-2002-15 Denial-of-Service Vulnerability in ISC BIND 9
      ... ISC BIND versions 8 and 4 are not affected. ... vulnerability will cause the BIND server to shut down. ... A vulnerability exists in version 9 of BIND ... The CERT Coordination Center thanks the Internet Software Consortium ...
      (Cert)