Discussion Locked
0 helpful
3 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I recently deleted the "." zone out of the forward lookup zones and took the remaining zone and put the forwarders in for the ISP. I have the clients getting the local DNS and the 2 ISP servers for their DNS servers (the local being the primary). I have the following issue: our website (which is the same name as the remaining forward lookup zone) doesn't resolve by name internally (it will by IP). It resolves fine externally. I wonder how I fix this???
3 replies
by tbragsda
You problem may be with NAT, not DNS.
Is your web server internal, with a pri address? The reason is, if you have DNS setup to the external address, it may cause problems.
If its somthing like this.
Internal clients on 10.x.x.x
WEB server 10.x.x.x
www.domain.com=65.105.75.20
and your doing NAT on the server, well the internal client will try to leave your network to get to a internal resource.
by ghstinshll
a HOSTS entry sounds good right about now...
by cliff680
Could I put a hosts entry on the win2k server to take care of this, or do I have to go to all of the workstations??? I don't want to go to all of the workstations.
This discussion is closed to new replies.
Trending IT Employment posts
Sort by Trending
0 helpful
1 reply
0 helpful
6 replies
0 helpful
11 replies
Discussion Locked
How should organizations verify AI generated information before using it
0 helpful
0 replies
Discussion Locked
Which team communication software is used in corporates?
0 helpful
9 replies