Resolve to private IP for internal clients


G

Guest

I currently have a server that is accessable from outside the network at
ftp.mysite.com. The server sits behind our firewall and is access using NAT.
Because of this, internal clients cannot connect to ftp.mysite.com because
even internally it still resolves to the public IP address. I would like to
configure our W2K DNS server to resolve ftp.mysite.com to the private IP
address of the server instead.

I opened the DNS management utility and added a new zone called mysite.com.
Now there are two zones listed, one is networkdomain.com and mysite.com.
Then I added two Host (A) records. One for ftp (ftp.mysite.com) and abc
(abc.mysite.com).

When I ping ftp.mysite.com is still resolves to the public IP address. When
I ping abc.mysite.com (which is not resolvable externally) it successfully
resolves to the IP address I entered in the Host (A) record.

So, it appears that my DNS server is letting higher level DNS servers
resolve the ftp.mysite.com address, and since the higher level DNS servers do
not have an entry for abc.mysite.com, my DNS server issues the right IP.

What am I doing wrong? How do I force my DNS server to use its the Host (A)
record I entered for ftp.mysite.com?
 
Ad

Advertisements

G

Guest

I figured it out... All I had to do was run ipconfig /flushdns on my XP
box... fixed.
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Top