DancesWithLysol
Occasional Visitor
My current router is a D-Link DGL-4500, but I've had similar issues with all my previous routers.
I've got a local network with a number of computers on them (computers and other devices like cell phones, consoles, TV, etc). I've always had major problems when trying to get my router to properly look up the machine names on my local LAN.
For example, if I run nslookup, it connects to my router IP as the nameserver, and then I try looking up a machine name of one of my computers. The lookup times out. Reverse lookups fail too.
I'm expecting for the nameserver portion of my router to check and see if there is a local machine of a given name "machinename.domain.local" before forwarding the request to my ISP's nameserver. If I'm looking for "google.com", it would work, but it would never properly lookup local machines. In other words it's only forwarding requests, never answering requests for local machines itself.
Ultimately, I solved this problem using my Windows Home Server box, installing and configuring the DHCP/DNS/Wins functionality and turning off DHCP on my router. Everything works great now, but when looking at my router documentation it sounds like the router should be able to do this, and I can't seem to get it to happen.
So, my question for this forum: do modern consumer level routers normally have this functionality? Am I just buying the wrong routers? Perhaps I'm just a stupid-head and need to learn how to use these routers?
I've got a local network with a number of computers on them (computers and other devices like cell phones, consoles, TV, etc). I've always had major problems when trying to get my router to properly look up the machine names on my local LAN.
For example, if I run nslookup, it connects to my router IP as the nameserver, and then I try looking up a machine name of one of my computers. The lookup times out. Reverse lookups fail too.
I'm expecting for the nameserver portion of my router to check and see if there is a local machine of a given name "machinename.domain.local" before forwarding the request to my ISP's nameserver. If I'm looking for "google.com", it would work, but it would never properly lookup local machines. In other words it's only forwarding requests, never answering requests for local machines itself.
Ultimately, I solved this problem using my Windows Home Server box, installing and configuring the DHCP/DNS/Wins functionality and turning off DHCP on my router. Everything works great now, but when looking at my router documentation it sounds like the router should be able to do this, and I can't seem to get it to happen.
So, my question for this forum: do modern consumer level routers normally have this functionality? Am I just buying the wrong routers? Perhaps I'm just a stupid-head and need to learn how to use these routers?
