LAN DNS Issue

[madrino]

Problem
I cannot get to our website from the LAN but can from the WAN. The website is on a DMZ with a public and private IP but the Lan is using a forwarder to point to the ISP's DNS servers. So when you try to go to our website the LAN traffic goes through the Cisco PIX and tries to connect to the external IP to resolve the website but the PIX does not allow loopback.

Question
How do I setup DNS on the internal dns server so it knows to go to the internal IP and not the public IP?

What I have tried
I tried to setup a

http://www record

on the lan but the problem with that is the lan domain is example.com but the website is

http://www.website.com.

So when you add the record you can get to the website but you have to type

http://www.website.com.example.com

because it adds the FQDN of the internal LAN to the website.

Thank you in advance for reading my post and helping me with this challenge.

 

[NetIntruder]

Try adding a new zone in DNS for website.com and add a

http://www record

there for the internal address of

http://www.website.com

- this should work for you.

~Intruder~
CEH, MCSA/MCSE 2000/2003

"The Less You Do, The Less Can Go Wrong"

 

[cathanas]

I would like to tag along to this thread. I have basically the same issue. We run a mortgage program that connects the client to MS SQL through a secured website. I created an A record for the website (

http://www.whatever.com)

and it resolved to the internal IP number. Everything worked. When I setup the external IP number for the website (

http://www.whatever.com),

the DNS immediately started to resolve to the external IP number. This, of course, caused the internal users to no longer has access. I have a stupid work around by listing the website and internal IP in the hosts file of the internal users. I also created a batch file to swap the line in and out for mobile users, so they can work both internally and externally. I have never experienced a DNS that would not resolve from it's own manually created records first, before forwarding to an outside server. Anyway, I have created an additional zone, but I have no idea how to force the DNS to use it for internal requests first. Any help would be appreciated.

 

[bcardona]

do you have an internal and external dns servers

 

[cathanas]

No, I run an internal DNS (behind my router and firewall) and resolve (root hints) to my ISP for external IP numbers.

 

[ITPangaeaArchitect]

madrino-
follow NetIntruder's instructions is the simplest route for you

cathanas-
sounds like you created the records in teh same zone...can't do this..it will use one or the other...but not both....

externally you should not need a record...whoever your registrar is should be pointing the address needed to your routers public IP (or firewall) for that web address....from teh firewall and/or router, you should have port mapping to send the ports necessary back to the correct internal IP....



for both:
I would keep the website set to <all unassigned> for the IP to use

-Brandon Wilson
MCSE00/03, MCSA:Messaging, MCSA03, A+
almost got a paragraph there