Re: Thoughts on a large-scale DNS server...

From: Jon Simola (jsimola_at_gmail.com)
Date: 06/29/05

  • Next message: Matthew D. Fuller: "Re: Thoughts on a large-scale DNS server..." 
    Date: Tue, 28 Jun 2005 21:37:00 -0700
To: freebsd-isp@freebsd.org

    On 6/28/05, Matthew D. Fuller <fullermd@over-yonder.net> wrote:

    > CPU? Sure. Memory? Quite probably. Even if you assume each zone
    > will eat 64k of memory (which I think it a terribly high guess; at
    > least double what you'd really expect), 11,000 zones will burn less
    > than 700 meg. I'd probably be tempted to double the memory, just
    > because memory is cheap&easy, but I doubt you'll be hitting a wall on
    > it.

    I'd recommend, if you have the time, to look into djbdns's tinydns. It
    uses a compiled DB file for speed and size. On the djbdns mailing
    lists there has been a few posts from some large-scale admins who use
    it to serve 500,000 zones, using about 300MB of ram on some mid-grade
    P4 machines handling 500 queries a second. One of the main reasons I
    remember they had switched was BIND's startup delay.

    Myself, I've only got 500 zones and it only uses 800K of memory. It's
    certainly nothing like BIND, here's all the raw source for a single
    domain, 2 nameservers, a webserver and an MX.
    (The . record generates an SOA, an NS at a.ns.mecha.ca, and an A for
    a.ns.mecha.ca -> 207.194.110.192. The & generates the second NS and A
    record, @ is the MX a.mx.mecha.ca and the A for a.mx.mecha.ca ->
    207.194.110.192, and the + is an A)

    .mecha.ca:207.194.110.192:a
    &mecha.ca:207.194.110.196:b
    @mecha.ca:207.194.110.192:a
    +www.mecha.ca:207.194.110.192 

    -- 
Jon Simola
Systems Administrator
ABC Communications
_______________________________________________
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: Matthew D. Fuller: "Re: Thoughts on a large-scale DNS server..."

    Relevant Pages

    • Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
      ... If your and other kernel developer's kernel ... Ingo Molnar says that zones work for him. ... and memory associated with still others. ... allocating and freeing large or small blocks of memory or it could be ...
      (Linux-Kernel)
    • Re: Blocking undesirable domains using BIND
      ... So hosts seemed easier, but apparently Bind never looks at hosts. ... server is now consuming 208 MB of ram. ... to the exact same thing it seems to be needlessly wasting memory. ... My experience, albeit with a smaller number of zones, is a bit different. ...
      (freebsd-questions)
    • Re: Blocking undesirable domains using BIND
      ... server is now consuming 208 MB of ram. ... to the exact same thing it seems to be needlessly wasting memory. ... My experience, albeit with a smaller number of zones, is a bit different. ... zone file 244B in size on disk: ...
      (freebsd-questions)
    • Re: [PATCH 0/5] make slab gfp fair
      ... The purpose of the cpuset is to limit memory for an application. ... There are 4 zones DMA DMA32 NORMAL and HIGHMEM and we have ... ZONE_NORMAL allocation you have 3 to pick from. ...
      (Linux-Kernel)
    • Re: [Lhms-devel] [PATCH 0/7] Fragmentation Avoidance V19
      ... > I am not enough of a kernel level person or sysadmin to know for certain, ... And when you don't use it, we'd be able to use those zones for at least ... Now, for many loads, that's fine. ... are often a big part of the memory use. ...
      (Linux-Kernel)
    • Quantcast