Dns not resolving

  • Thread starter Thread starter Nic
  • Start date Start date
N

Nic

Hi Everyone,

I have a weird problem. I have DNS setup on a machine
that is the AD controller. I use a router The router is
setup with IP address like. 27.123.15.x and point to my
servers. Now, my servers have static IP's on them and
they are #'s like 10.1.1.x and so forth. If I go to one
of the machines on the network and try to hit my ftp site
by address it resolves, but when I do this on the AD
server, it will not. I also cannot hit the HTTP address's
by name from this server. I think that I am missing
something and don't know what it is. I can hit the ftp,
by typing in the 10.1.1.x number but not by the
27.123.15.x.

Does anyone have any suggestions on how I can get this
resolved?

thanks in advance
NIC
 
In
Nic said:
Hi Everyone,

I have a weird problem. I have DNS setup on a machine
that is the AD controller. I use a router The router is
setup with IP address like. 27.123.15.x and point to my
servers. Now, my servers have static IP's on them and
they are #'s like 10.1.1.x and so forth. If I go to one
of the machines on the network and try to hit my ftp site
by address it resolves, but when I do this on the AD
server, it will not. I also cannot hit the HTTP address's
by name from this server. I think that I am missing
something and don't know what it is. I can hit the ftp,
by typing in the 10.1.1.x number but not by the
27.123.15.x.

Does anyone have any suggestions on how I can get this
resolved?

thanks in advance
NIC
Click to expand...
What DNS do your Network clients use? The DC?
They should be using the DC for DNS if DNS is installed on the DC.

The same goes for the DC it should be pointing to its own IP for DNS.
So if the clients are resolving the private address the server should be to
if it is pointing to its own address.
If the DC is pointing to its own address and it is not resolving then the
ftp record is missing from your internal zone. That would make me ask how
are the clients resolving if the DC can't, I don't know what kind of router
you are using but most do not allow internal clients to connect to internal
clients by the public address.

I'm sorry for making such a long discussion out of this but you really don't
give many clues to you setup to tell me why the clients can connect but the
server can't.

Can you please elaborate a little more and provide an ipconfig /all from a
client and the server.
You can run nslookup for the name from both the client and server to see
what it is resolving to.
 
Can you reach the FTP site from the DC by IP address?

Thank you,
Mike Johnston
Microsoft Network Support

Thank you,
Mike Johnston
Microsoft Network Support
--

This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the
terms specified at
http://www.microsoft.com/info/cpyright.htm

Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from
which they originated.
 
Back
Top