Short description
I brought this up with ThomasWaldmann on the IRC channel the other day. Basically if you're on a LAN managed by a router that doesn't provide reverse DNS lookups, editing pages on the LAN is really slow because it waits to timeout on these lookups when searching for a textual name to put in the edit log. Either there should be an option to exclude IPv4 designated subnets that are reserved for local use from the reverse lookup, or a way to specify an arbitrary list of IP ranges that you don't want to reverse-lookup.
-- DavidWardeFarley, June 16, 2006
I don't think we add such a "exclude the broken part of my dns and keep the working part" feature, but I have already added a switch to simply disable reverse dns lookups to moin-1.5 and -1.6 branches.
So if your dns is broken you either have to fix it (completely) or disable usage of it (completely) or live with editing from the broken part taking a bit longer.
-- ThomasWaldmann 2006-06-17 10:45:03
This is an okay solution, but nearly NOBODY has working LAN Reverse DNS. And it's a pretty simple fix that I suggested. Oh well. -- DavidWardeFarley 2024-04-29 04:39:37
---
I'd like to second David's request emphatically. On our LAN, there is a working DNS, but it takes several seconds to resolve reverse DNS to dynamic client names most of the time. We're using Desktop Edition, and that adds two to four seconds to every single page access that comes over the VPN or proxy.
The log_reverse_dns_lookups option defeats the reverse DNS only on page saves, not on page reads, according to the docs. For my configuration, I would prefer to reverse that option. Write is a rare operation relative to read, so I would not mind the slight delay on page writes.
Please reconsider this request for a (near) future version of this great product. Thanks.
-- RickLandau 2007-05-11 18:11:15
Moin itself only does reverse DNS lookup for save, not for read. The stdlib code used for standalone (and MMDE) might do reverse lookups, though. In the latest moin versions we added some code to override that stdlib behaviour. -- ThomasWaldmann 2007-05-11 21:52:39
Thanks for the quick reply. I appreciate the clarification. I'm still a little puzzled because the latest Desktop Edition, retrieved and installed at 10:00 this morning, still emits nodenames (FQDNs) rather than IP addresses in its console log. Those names have to come from somewhere. The names seem to be bogus sometimes, true, so maybe it isn't really doing the reverse DNS. The delays are so irritating to users that I will switch to Apache as soon as I learn how to run standard MoinMoin at the same URLs that Desktop uses. (I posted a question about this, too.) Again, thanks. -- RickLandau 2007-05-11 22:29:31