Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 39
  • Last Modified:

website not working for lan

hi my our company website working fine from outside. it is not working from outside. we have windows 2012 Domain controllers. What steps we need in dns to resolve this issue.

Regards
jig
0
swatujct
Asked:
swatujct
  • 3
  • 2
  • 2
  • +2
2 Solutions
 
Gary DewrellSenior Network AdministratorCommented:
I assume your webserver is in a DMZ or on your internal lan and then published to a public outside IP address through a firewall. On your internal DNS server add an A record that points to the Internal ip address, not the outside public IP address.

For example if you have a website at www.mycompany.com running on a server name WebServer that is in your DMZ at IP address 192.169.200.101 and published to the internet with a public IP of 208.152.22.4 then you would have a DNS record on your internal DNS server that says.

www.mycompany.com      A        192.168.200.101
0
 
Member_2_7971300Commented:
Hi Jin,

Your application is hosted in the server which uses Company specific Network. You can't access those from outside. In order to access outside you need to connect to your company network.

Thanks,
Ron
0
 
Gary DewrellSenior Network AdministratorCommented:
Member_2_7971300 I think you may have misunderstood the question because of a typo in the question.

I believe the issue is they cannot access the website from internal systems.
0
When ransomware hits your clients, what do you do?

MSPs: Endpoint security isn’t enough to prevent ransomware.
As the impact and severity of crypto ransomware attacks has grown, Webroot has fought back, not just by building a next-gen endpoint solution capable of preventing ransomware attacks but also by being a thought leader.

 
Alexandre MichelCommented:
gdwrell

Assuming your website URL is www.mywebsite.com and your internal DNS IP is 192.168.16.2, what happens when you run this in a CMD prompt:
  1. PING www.mywebsite.com
  2. NSLOOKUP www.mywebsite.com 192.168.16.2
  3. NSLOOKUP www.mywebsite.com 8.8.8.8

From the error you appear to have, your internal DNS might not be configured properly
You might need to add an A record to your own DNS to point www.mywebsite.com to the (external) IP of your website

To test that theory, you can edit the HOST file of one of your computers then do a PING test. If it works, then it confirms you need to fix your internal DNS
Follow for example this site to edit your HOST file: http://helpdeskgeek.com/windows-7/windows-7-hosts-file/ .
0
 
Gary DewrellSenior Network AdministratorCommented:
alexander, I am not the person asking the question but good input.
0
 
swatujctAuthor Commented:
our website is hosted with 3rd party hosting company. We dont have any website on dmz or internal network. Hosting company block our ip. as per request they released now. earlier i was not able to ping www.stackteck.com our website from our internal network. after they released from block we can ping. but still i am not able to access using www.stackteck.com

i have cleared cookies and tried still same issue. i setup another browser n tried still same issue.
0
 
DrDave242Commented:
Is your internal (Active Directory) domain also named stackteck.com? If so, that's the problem. There's an HTTP redirect on the www.stackteck.com site that redirects your request to simply stackteck.com. (You can confirm this by browsing to www.stackteck.com from outside. When the page loads, you'll notice that the URL in the address bar changes to stackteck.com.)

The problem is that stackteck.com will resolve to the address of one of your domain controllers from inside, rather than the address of the website. This is by design. The only way to fix the problem is to remove the HTTP redirect from the website. You'll also have to make sure you have a host record named www on your internal DNS servers that points to the IP address of the site, and you'll have to instruct your internal users to always put www in the URL when browsing to the site.
0
 
Alexandre MichelCommented:
You will be able to confirm DrDave's explanation by doing the following in a command prompt

PING www.stackteck.com
NSLOOKUP www.stackteck.com 192.168.16.2
NSLOOKUP www.stackteck.com 8.8.8.8

Open in new window


Assuming your own internal DNS is 192.168.16.2
If you don't know what is your internal DNS, type IPCONFIG /ALL in a CMD prompt and look for the line that starts with "DNS Server"
0
 
DrDave242Commented:
Auto-closing due to inactivity. Would like to know for sure that this solution worked, but I'm confident that it will.
0

Featured Post

What does it mean to be "Always On"?

Is your cloud always on? With an Always On cloud you won't have to worry about downtime for maintenance or software application code updates, ensuring that your bottom line isn't affected.

  • 3
  • 2
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now