[Last Call] Learn how to a build a cloud-first strategyRegister Now

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

DNS Question

Recently a public website was developed & we cannot access it from our internal network. We have a Win 2003 AD domain & internal domain name is testing.com. Our exteranl domain name that is registered with Network Solutions is the same as our "AD Domain" name, i.e; www.testing.com is the link to this website. We can hit the site from out side of the network but not internally. The problem definetaly lies with our internal DNS servers trying to serve up the page for www.testing.com.  What records need to be added to our internal DNS server to allow our users to hit our external site? Thanks in advance for any help!
0
ZappaMang
Asked:
ZappaMang
  • 4
  • 3
1 Solution
 
oBdACommented:
You need to add a host record "www" in the forward lookup zone "testing.com" of your AD, pointing to your external IP address. You'll need to repeat this process for every outside address hosted at "testing.com" (mail, ftp, whatever).
0
 
oBdACommented:
Oh, and just in case: you will NOT be able to access just "testing.com" on the external webserver, unless you're setting up IIS on all DCs and make a redirect to "www.testing.com".
0
 
Darius GhassemCommented:
Just some quick help oBdA's suggestion is the way to go but add a "A" record in DNS with the external DNS server just in case you didn't understand exactly what type of record
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
ZappaMangAuthor Commented:
Thanks for the responce guys I really appreciate it. I actually had tried adding www as a Host record on my internal DNS server & that didn't seem to do the trick. If I try to ping www or www.testing.com , both names are unable to be resolved from my internal users. However, if I edit the HOSTS file directly & specify that x.x.x.x resolves to www.testing.com things work just fine. Why isn't DNS doing its job here? I really need to figure out why that is, the last thing I want to do is manipulate everyone's hosts file. Let me know what your thoughts are. Thanks.
0
 
oBdACommented:
What sort of troubleshooting have you done so far?
What is "my internal DNS server"; is this your DC?
Are *all* domain members using *only* your DC as DNS server?
Can you see the "www" entry in the forward lookup zone testing.com, next to the other host entries for your domain members? Is it of type "Host (A)", does it have the correct outside IP address?
Can you resolve www on your DC through "nslookup www" and "nslookup www.testing.com"?
Can you resolve www on a client using "nslookup www" and "nslookup www.testing.com"?
0
 
ZappaMangAuthor Commented:
oBda, yes "my internal DNS server", is my DC. All domain members point only to the DC DNS server. I do see the "www" entry in the forward lookup zone "testing.com". I did add the record as a "Host (A)" type & it is pointing to the correct IP address, the external Web Address IP. I cannot resolve www nor www.testing.com on my DC nor on a client PC. The other testing I have done was adding the Internet IP to the DC host file directly for both "www" & "www.testing.com". When I did that I could get to the Website, but as soon as I #'ed out those two entries I could no longer hit the website. Its def a DNS issue, I'm just not sure as to why it is not working...
0
 
oBdACommented:
In the DNS console, right-click the server and choose "Delete cache". On the server and on the client(s) you're trying this, open a command prompt and enter
ipconfig /flushdns
Then run
nslookup www.testing.com
again.
0
 
ZappaMangAuthor Commented:
oBda, thanks for the responces man, great responce times! All is good. I re-moved & re-added the Host record for this. I also flushed the dns cache on the server & client... All is working like it should be now. Enjoy the rest of your weekend.
0

Featured Post

Fill in the form and get your FREE NFR key NOW!

Veeam is happy to provide a FREE NFR server license to certified engineers, trainers, and bloggers.  It allows for the non‑production use of Veeam Agent for Microsoft Windows. This license is valid for five workstations and two servers.

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