FTP & DNS entry

  • Thread starter Thread starter Steve G
  • Start date Start date
S

Steve G

I'm just curious what DNS entry needs to be made for a
FTP site? Just a A record entry, with the FTP name and
the IP of the FTP server, if its not a local machine?

Steve
 
In Steve G <[email protected]> posted a question
Then Kevin replied below:
: I'm just curious what DNS entry needs to be made for a
: FTP site? Just a A record entry, with the FTP name and
: the IP of the FTP server, if its not a local machine?
:
: Steve

If you have a Zone for the domain name that the FTP site is in then you need
the record. The example of this is if your public name is example.com and
your AD domain is example.com when you make a query to your DNS server for
ftp.example.com and the ftp record is only in the public example.com zone.
Your DNS server will not forward because it is Authoritative for the
internal example.com domain it will not send the query out because it knows
nothing of the public zone. You have to create the records or delegate the
name to the DNS server that holds the name in the public zone.
 
Let me see if I can clear up something. I'm not using
AD, I have DNS running on 1 Wk2 Server box, and on my
same network, would install another W2k Server. I'd like
to have all FTP traffic go to that 2nd box and route it
via DNS.

Will adding the record to the current zone allow me to do
this?

Steve
 
Yes. The DNS record only servces to identify the machine. What happens to
the protocol/record being requested is entirely up to the destination
machine.

So, say your new machine is myServer, your zone is myZone.com and you then
create an A record under myZone.com, name it myServer(or myFTPServer, or
whatever) give it the IP address of the myServer machine, then tell your
users to point their FTP client to myServer.MyZone.com. The client will then
ask the DNS server for the IP address of myServer.MyZone.com, and your DNS
server will cough it up. From then onwards, the communication is between the
Client and myServer.

Hope I haven't terribly confused you ;)

--
Sincerely,

Dèjì Akómöláfé, MCSE MCSA MCP+I
www.akomolafe.com
www.iyaburo.com
Do you now realize that Today is the Tomorrow you were worried about
Yesterday? -anon
 
In
Steve G said:
Let me see if I can clear up something. I'm not using
AD, I have DNS running on 1 Wk2 Server box, and on my
same network, would install another W2k Server. I'd like
to have all FTP traffic go to that 2nd box and route it
via DNS.

Will adding the record to the current zone allow me to do
this?

Steve
Click to expand...

Just to point out, DNS does not route. Routers route. DNS just has a table
of names to an IP address.

So you would just create an 'ftp' A record under your zone name (without the
quotes) and give it the IP address of the ftp server.


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Let me see if I can clear up something. I'm not using
AD, I have DNS running on 1 Wk2 Server box, and on my
same network, would install another W2k Server. I'd like
to have all FTP traffic go to that 2nd box and route it
via DNS.
Click to expand...

DNS doesn't "route" anything, it simply matches a name to an IP
address. If you create an A record with a host name of FTP pointing
to the second server, but the first server has a host name of "bob",
there's no reason a client couldn't type ftp://bob.domain.com/ instead
of ftp://ftp.domain.com/. Naturally, you wnat to not run FTP services
on the server you don't want anyone FTP'ng to.
Will adding the record to the current zone allow me to do
this?
Click to expand...

Not exactly, as above.

Jeff
 
Back
Top