Question Locked

Cannot resolve websites with Internal DNS

0 helpful
6 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

Recently, I have setup a few websites running on couple of servers (Linux & Windows). Here are the components in my network.

- Cisco 3620 Router (DHCP, NAT)
- Cisco 2950 Switch (VLAN1)
- Windows 2003 EE DC (Active Direcotry, DNS)
- Windows 2003 Web Server (IIS)
- CentOS 4.4 Web Server (Tomcat)

All machines are connected to the switch with default VLAN and use DHCP info from the router and DNS from Domain Controller.

There are 3 websites on IIS and 2 on Tomcat and I am using Host Headers for all of them.

I am able to browse all the websites from the Internet but I can't browse any sites from within my network, not even on the servers that are hosting them.

I have static NAT configured on my Router that allows the mapping of public to private IP address for these websites. I also have PAT configured that allows client machines on the Nework to browse the internet.

I heared from someone that to view websites that use Private IP addresses you need to implement something called DNS Doctoring. I have searched a lot on this and came with nothing.

Hope someone out there can help me out. Here is snap-shot of my Cisco router running-config if you find something wrong with the NAT settings... Thanks in advance

------------------ show running-config ------------------

Building configuration...

Current configuration : 1841 bytes
!
version 12.2
service timestamps debug uptime
service timestamps log uptime
service password-encryption
!
hostname RT-3620
!
enable secret 5
!
ip subnet-zero
!
!
ip name-server 4.4.4.4
ip name-server 5.5.5.5
ip name-server 6.6.6.6
ip dhcp excluded-address 192.168.2.23 192.168.2.254
!
ip dhcp pool Twenty
network 192.168.2.0 255.255.255.0
default-router 192.168.2.1
dns-server 192.168.2.225
!
ip ssh time-out 120
ip ssh authentication-retries 3
!
call rsvp-sync
!
!
!
!
!
!
!
!
interface Ethernet0/0
ip address 3.3.3.10 255.255.255.0
ip nat outside
half-duplex
!
interface FastEthernet1/0
ip address 192.168.2.1 255.255.255.0
ip nat inside
duplex auto
speed auto
!
interface TokenRing1/0
no ip address
shutdown
ring-speed 16
!
ip nat inside source list 1 interface Ethernet0/0 overload
ip nat inside source static tcp 192.168.2.128 80 3.3.3.11 80 extendable
ip nat inside source static tcp 192.168.2.128 443 3.3.3.11 443 extendable
ip nat inside source static tcp 192.168.2.127 443 3.3.3.12 443 extendable
ip nat inside source static tcp 192.168.2.127 80 3.3.3.12 80 extendable

ip classless
ip route 0.0.0.0 0.0.0.0 3.3.3.1
no ip http server
ip pim bidir-enable
!
access-list 1 permit 192.168.2.0 0.0.0.255
!
dial-peer cor custom
!
!
!
!

!
end

6 replies

by tg2

try testing by editing the hosts file on a workstation

192.168.1.x www.somesite.com

with the internal address of the web server, and the www.somesite.com being the valid host header name for one of the iis instances on the server.

if that works, check to see if one of the other workstations shows traffic coming back to itself from the webserver internal or external ip address, when expecting the latter. ie. if your other workstation gets an outside ip, but then sees traffic back from a different internal, that would cause this.

This is also the reason you use DMZ's ... put your web server into the DMZ and that will probably solve the issue. Of course you have to set up the DMZ !!

If you have services that have to run internal, then you may have to multi-home the machine, 192.168.1.x for internal stuff, 192.168.100.x for externally accessed items. Then let your router do the right work, and make sure your firewall isn't allowing the internal 192.168.1.x stuff to be gotten to through a 192.168.100.x address.

by h_buchal

Thanks TG2 for your prompt reply.

Putting up the entries in the hosts file worked but that's not what I actually want.
Are there some settings that I need to change on my DNS server as every DNS request goes through there.

I understand the DMZ but unfortunately There are only 2 interfaces on Cisco Router (one connected to WAN and other to LAN). I can do VLANs but current IOS doesn't have support for it or atleast the commands I tried didn't work. I will try to upgrade and try that again. Is there any other way beside setting up DMZ that will work?

What about DNS Docotring/DNS Rewrite? I am not much familiar with these concepts but this is what is configured at my work place I think and there is no DMZ I believe. But they have external and Internal pix firewalls.

Thanks

by koolone4u

hello mate i have a some sort of similer problem with my server..what i am facing, i have hosted 4 websites on my iis with hostheader and define host record

on local dns server(internal server).i can view websites from sever and as well as from clients pcs but i wont able to access from internet. well let me tell

you my network configration

i have windows 2003 server with two nic card one is connected to local network and second is connnected to isp router .
internal nic have a ip 192.168.2.200
DNS - 192.168.2.200

second nic which is connected to router
192.168.1.72
dns - 192.168.1.254

i have a domain on godaddy sever,let say www.xyz.com, what i have done on the godaddy server i just add host record let say local.xyz.com and put my router

public ip address for local, and what i have done on speedtouch isp router , i just simple forward all incoming request on router public address to my sever

local ip address which is 192.168.1.72

but i dont know why it does not working. when i try to nslookup the local.xyz.com ,i do get my router public ip in reponce but the request does not forward

to the server..

kindly help to slove this issue

regard

by tg2

What is your default gateway?

you should have only one, and it should not be your local lan, it should be the one that the network is attached to the internet router on.. 192.168.1.x

While Microsoft does support multiple gateways, and can fail from one to the other, they don't (as of last search) fail over and back.

That is if one gateway goes down, MS will fail over to the other gateway, and when that failed gateway comes back up, MS does not switch back on its own.

Most likely you are seeing some form of route issue... ie. traffic comes in on the 192.168.1.x interface, and then leaves through the 192.168.2.x interface.

You should also be able to have some logging on your router/firewall so that you could see if traffic is failing that way.

Remember NAT wants to solve the machine IP for traffic in and out.

This discussion is closed to new replies.