David Wright: > Quoting Jochen Spieker (m...@well-adjusted.de): >> >> Where's the problem in Apache using your router's DNS? Is it just that >> the router doesn't resolve unqualified names (supercrunch without the >> domain)? > > I didn't know bog-standard domestic routers ran a DNS server.
I think all of them do. They have simple caching-only DNS servers that just ask your ISP's DNS resolver for all but local hostnames. Your computers should request an IP address and at the same time register what they think is their local hostname on the router (all via DHCP). This way your router's DNS server should be able to resolve local hostnames for other clients, rendering your editing of hosts files unnecessary. Usually your router also tells the DHCP clients the name of the network they are in. My AVM Fritzbox (German manufacturer) hands out ".fritz.box" which I find so horrible that I run a separate DNS/DHCP server (dnsmasq) on another box. > I thought they just asked the external nameservers, either set up > automatically from the ISP or manually configured if using public ones. That plus resolution of local hostnames. >> Using an IP address as ServerName is odd. You have to use the hostname >> that you want to use in URLs here. > > The latter seems odd, seeing as the first thing you would normally do > with a hostname is look it up and turn it into an IP address. Yes, but most people are better at remembering names than IP addresses and the lookup is performed automatically whenever you use it. How often do you open http://173.194.116.166 in order to go to Google? Or, god forbid, http://[2a00:1450:4001:80e::1009] (in case you already have IPv6)? > I don't know how you have your LAN configured. I use DHCP from the > router, which assigns fixed IP#s by MAC address. That way, I can > list my own hosts in /etc/hosts and avoid needing a DNS server to > resolve their names: > > 127.0.0.1 localhost > 127.0.1.1 thishost > 192.168.1.1 router > 192.168.1.11 otherhosta > 192.168.1.12 otherhostb > 192.168.1.31 HP0C00E0 hp8000 … and you have to keep that file in sync on all hosts. I use DHCP as well and make sure my clients send their hostname when requesting an IP address vie DHCP. Debian does this automatically. Then all clients in the local network can resolve their names just fine and I don't need to edit hosts files. I do use fixed IPs for a few hosts as well, but mostly because I use port forwardings or local services that I want to bind to a specific address. But this is just a configuration on the DHCP server and nothing I have to repeat on all boxes in my network. If this sounds as if I had an awful lot of computers: no, I don't think so. It's just an awful lot of, well, _devices_ with wired/wireless networking capability: - two laptops (one for me, one for my wife) - one desktop (seldomly used) - one file/print/mail/whatever server in the basement - two Android phones - one iPad (1st gen, essentially a doorstop) - one Roku Soundbridge, a hardware streaming client hooked up to my hifi system - one network printer - one ChromeCast - one Raspberry Pi 2 - one manageable switch - one not-so-smart TV Not all of those need to talk with each other but I find it is easiest if everything is managed the same way. DNS coupled with DHCP works fine for that. If one of your machines provides a service for all of the others (like sending mail through your mail provider's relay), you may even want to set up alias hostnames (like "mail"). This enables you to easily move this service to another host later on without changing all of your clients. :) Yes, I may be guilty of overengineering a few things. But I now spend considerably less time with this than a few years ago and I think this is related to the way I have set things up. > I don't set any domainname. The only consequence I know of is exim > complaining at boot: > > Starting MTA:hostname --fqdn did not return a fully qualified name, > dc_minimaldns will not work. > Please fix your /etc/hosts setup. Well, Exim is written primarily as a "real" mail server (MTA). Your usage is supported (and common), but the authors just expect a "proper" environment. A network without a name (not even a fake name) isn't. Anyway, sorry that I am not really helping you with your redmine issue. If it persists it might help if you summarized what exactly you want to achieve ("I want to enter http://whatever into my browser and see redmine's login dialog"), how you try to do that ("here's my config again in case you forgot") and what actually happens ("when I open the address in my browser, I get this exact error message and see the following in my Apache logs"). Regards, J. -- Fashion is more important to me than war, famine, disease or art. [Agree] [Disagree] <http://www.slowlydownward.com/NODATA/data_enter2.html>
signature.asc
Description: Digital signature
