DD-WRT Router Problem - Can Not Access by Host name, Only by IP Address

I have configured Netgear N600 Wireless Router and have separated the Wireless and Wired Network, each with their own DHCP server. The Wireless has access to the wired connection but does not have access to the WAN port. The goal is to limit wireless access to just those Hosts connected to the router.

The incoming Wan connection is coming from a larger LAN and is assigning the router IP address via DHCP. The larger LAN connection then goes to the Public WAN address.

I currently have 2 issues:

Issue #1: I can connect from the wired computer to LAN outside the router by IP address but not by Computer name, which I would prefer, since the IP address may change on the HOST but the name will not.

Issue #2: I can not connect from the LAN to the wired computer on the the router in any manner. I can PING the router but can get no further.

I have been trying various options and have even put DNSMasq on the router to help with any DNA issues.

Any help with my problem would be great, as I'm currently banging my head against my desk.
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Bryant SchaperCommented:
1.  You will need to setup DNS so you can use the computer names, on the router use the DNS server on the larger LAN, not a public DNS server.

2.  Many reasons come to mind, but initially I would say that the LAN has no knowledge that the computers exist on the inside interfaces of the router, they would need a static route or something to get in.
- You need to have some DNS in order to resolve hosts names to IP addresses
- your router must actually ROUTE packets between LAN and wired hosts. Thus it cannot be set to be a "gateway" (Network Address Translator) and must actually be a real router.
FujiFrankAuthor Commented:
Thanks for the starting points, which I figured I'm dealing with a DNS issue for number 1.

My problem for number 1,  is that the DNS server will not always be the same, is there a way I can use the larger LAN DNS even though it will be different from location to location?

On number 2, I know I need to "open" the router but if not using NAT, what suggestions do you have?
Bryant SchaperCommented:
Not sure I understand #1, but you could point your router to a fixed DNS, or multiples right

On #2, if you don't nat, the larger network needs to know the other router is there.

for example if the larger is 1.1.1.x with a default gateway of all workstations on that network will talk to router to get to say 2.2.2.x behind the new firewall.  So has a route that says 2.2.2.x is on (ip of new router on larger network)

maybe you could provide a diagram.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.