Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]
Groups > linux.debian.user > #185915
| From | Greg Wooledge <wooledg@eeg.ccf.org> |
|---|---|
| Newsgroups | linux.debian.user |
| Subject | Re: DHCP server that itself gets an IP address by DHCP |
| Date | 2017-08-25 16:00 +0200 |
| Message-ID | <uinjr-4Jl-15@gated-at.bofh.it> (permalink) |
| References | (1 earlier) <ui6Vj-2MH-3@gated-at.bofh.it> <ui750-2Q6-11@gated-at.bofh.it> <ui8X7-4cx-1@gated-at.bofh.it> <uilKF-3VD-9@gated-at.bofh.it> <uimGK-4wF-19@gated-at.bofh.it> |
| Organization | linux.* mail to news gateway |
On Fri, Aug 25, 2017 at 10:12:07PM +0900, Mark Fletcher wrote: > However, now, based on your response I am thinking the AirStation is > just forwarding the DNS queries on to the nameservers it is given in > response to its DHCP query, and not actually caching anything... Very likely, yes. > would a nameserver need a lot of memory / disk space? The > machine has a 32GB SSD, of which about 15GB is free, and 4GB of RAM, of > which according to top about 1.8GB is free... That is plenty of memory for a caching resolver. Luxury! As a real-world example, <https://cr.yp.to/djbdns/dnscache.html> (which is what I use) uses about 2 MB of RAM in a small-network configuration. It doesn't say so on that page, but the default value of CACHESIZE is 1000000 (a million bytes). So, figure about 1 MB plus however high you set the CACHESIZE variable. I can't speak for other DNS resolvers. BIND in particular may be quite bloated, and would not be my choice for a new setup.
Back to linux.debian.user | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread
Re: DHCP server that itself gets an IP address by DHCP Reco <recoverym4n@gmail.com> - 2017-08-24 11:40 +0200
threading, was Re: DHCP server that itself gets an IP address by DHCP David Wright <deblis@lionunicorn.co.uk> - 2017-08-24 15:30 +0200
Re: threading, was Re: DHCP server that itself gets an IP address by DHCP Reco <recoverym4n@gmail.com> - 2017-08-24 17:10 +0200
Re: DHCP server that itself gets an IP address by DHCP Pascal Hambourg <pascal@plouf.fr.eu.org> - 2017-08-24 22:30 +0200
Re: DHCP server that itself gets an IP address by DHCP Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-24 22:40 +0200
Re: DHCP server that itself gets an IP address by DHCP Mark Fletcher <mark27q1@gmail.com> - 2017-08-25 00:40 +0200
Re: DHCP server that itself gets an IP address by DHCP Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-25 14:20 +0200
Re: DHCP server that itself gets an IP address by DHCP Mark Fletcher <mark27q1@gmail.com> - 2017-08-25 15:20 +0200
Re: DHCP server that itself gets an IP address by DHCP Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-25 16:00 +0200
Re: DHCP server that itself gets an IP address by DHCP Reco <recoverym4n@gmail.com> - 2017-08-24 22:40 +0200
Re: DHCP server that itself gets an IP address by DHCP Mark Fletcher <mark27q1@gmail.com> - 2017-08-25 00:30 +0200
Re: DHCP server that itself gets an IP address by DHCP Reco <recoverym4n@gmail.com> - 2017-08-25 10:20 +0200
Re: DHCP server that itself gets an IP address by DHCP Greg Wooledge <wooledg@eeg.ccf.org> - 2017-08-25 14:20 +0200
csiph-web