140 reputation
115
bio website
location
age
visits member for 2 years, 4 months
seen Aug 21 at 1:45

May
3
comment Reverse DNS lookups slowing down network operations on LAN
Marking this as accepted answer. The 3 answers were helpful, but changing the dns servers solved the problem "at large".
Apr
28
comment Reverse DNS lookups slowing down network operations on LAN
Wow this actually makes a BIG difference! Apparently these DNS servers (Google's and OpenDNS') fail fast when given a private IP address. I'll run a few more tests, but I think this solves my problem!
Apr
27
comment Reverse DNS lookups slowing down network operations on LAN
I wish I could set up a DNS server with the actual equipment I have, but it's not really feasible unless I load an alternate firmware on the router. Thanks for the config options; I hadn't found out about the AS_NO_REVERSE_DNS option for Glassfish so I'll have a look.
Apr
27
comment Reverse DNS lookups slowing down network operations on LAN
My router is a "NETGEAR Router WNR3500L" @ 192.168.1.1. The logs only show DHCP leases and logins to the admin interface. You are right, the router sends 192.168.1.1 as the dns server when handling out DHCP leases (confirmed with Wireshark). On the router's admin interface, I'm using "Get Automatically from ISP" for the DNS adresses. The other option is to specify directly DNS servers by IP. I guess this means DNS requests are actually forwarded by the router.
Apr
27
comment Reverse DNS lookups slowing down network operations on LAN
Updated my post again. Thanks for your help so far.
Apr
27
comment Reverse DNS lookups slowing down network operations on LAN
Since this is only a test server (and a virtual one too!), I can't rely on it as a DHCP server for the whole LAN. There are other occasional wireless clients too that need an IP even when my dev pc, and therefore the test server, is not running.
Apr
27
comment Reverse DNS lookups slowing down network operations on LAN
Thanks. I updated my post with more info.