Some years ago, I wrote a BLog article on this in German language:Can anyone point me to an article about setting up unbound() on a LAN?
I'm wanting to designate a particular host on the LAN as the nameserver for the LAN and am not sure whether unbound needs to be run on each host or how unbound integrates with my DHCP server...
Install and configure unbound on that host. Make sure unbound is listening on the LAN, not only on 127.0.0.1 (localhost). Then configure your DHCP service and set it to serve the correct IP address for your unbound server, DHCP is typically configured to provide, besides an IP address and gateway, one or two DNS servers. That's all. There is no "integration" in this respect.I'm wanting to designate a particular host on the LAN as the nameserver for the LAN and am not sure whether unbound needs to be run on each host or how unbound integrates with my DHCP server...
Can't even read the manual on their website without being forced to login. I think I'll pass.a Huawei HG8245Q2
Seems like a worthless non-configurable thingy.Can't even read the manual on their website without being forced to login. I think I'll pass.
Might be something similar as that piece of cr^H^H wonderful technology Ziggo (Dutch cable internet provider) supplies. Can't do anything with it. Luckily it does have a "modem" mode so I can just bypass all that builtin router stuff. DNS, DHCP, firewalling, NAT, etc, is done on a relatively small FreeBSD host. Much better.Seems like a worthless non-configurable thingy.
If his provider is anything like mine, not going to work. I can't even buy an alternate modem/router, they simply refuse to support anything but their own crappy boxes. Don't even think of just hooking up something yourself, if they find out they'll just turn off the signal. And you can forget about phoning support, Oh, no, that's not ours. Sorry, we don't support that *click*. Oh, you want to report an issue with an upstream router (somewhere on their bloody network, nowhere near my home). No, we have to plan an engineer to come to your house and do some measurements. You don't want that? What do you mean it's not necessary, the issue is not with your connection? Then we won't register your issue, good day sir.So the used Fritzboxen get thrown away in lots, and sold on ebay for a few euros.
Reminds me of the times when telecom here was still state monopoly.Don't even think of just hooking up something yourself, if they find out they'll just turn off the signal.
The web page https://support.huawei.com/enterprise/en/access-network/echolife-hg8245q2-pid-21989531 may say if it is possible to switch to modem mode. I looked but there are so.. many options. Didn't know where to look. I'd register to download a manual but don't even know which might provide the info about modem mode.Can't even read the manual on their website without being forced to login. I think I'll pass.
Probably not. See post #8 for a link to the manual you can read without registering.if it is possible to switch to modem mode.
A two year contract means that I have to pay for the remainder of my contract even if I change ISP...balanga, pull the plug & switch your ISP. Period. That's the only feedback they understand. If you're not too busy, encourage other to do so as well, and write them an e-mail explaining the reason(s) of your withdrawal.
Dunno where you're at, but in the US that's what Small Claims Court is for. I love hauling giants to my local courthouse. They don't like it so much.A two year contract means that I have to pay for the remainder of my contract even if I change ISP...
Going back to the ARPANET. Old school!I'm beginning to think it might be easier to maintain the same /etc/hosts on all the systems on my LAN...
Make sure it's a router and not a bridge, with at least two separate physical interfaces. You will experience DHCP sadness otherwise.The only other technical option I see is to insert a host (with DHCP server for your LAN) between your LAN and that crappy modem/router and filter it's DHCP traffic.
Don't we have filtering bridges?Make sure it's a router and not a bridge, with at least two separate physical interfaces. You will experience DHCP sadness otherwise.
Bridges work at layer 2 so they'll forward DHCP broadcasts. You'll have two DHCP servers in the same broadcast domain. I've tried this (not on purpose) and can tell you that hilarity will ensue.Don't we have filtering bridges?
Can anyone point me to an article about setting up unbound() on a LAN?
I'm wanting to designate a particular host on the LAN as the nameserver for the LAN and am not sure whether unbound needs to be run on each host or how unbound integrates with my DHCP server...
dig
or nslookup
on the machine, then setup Unbound to act as the recursive/caching nameserver for your network on the same machine. In Unbound's config, you'll add a stub-zone statement to teach it to talk to the local NSD instance on loopback:53 for your LAN's local zone:# forward zone for *.local
stub-zone:
name: "local"
stub-addr: 127.0.0.1@53
# reverse IPv4 zone for 10.0.0.0/8.
stub-zone:
name: "10.in-addr.arpa"
stub-addr: 127.0.0.1@53