How do I create host record with 2 IPs?

  • Thread starter Thread starter Sam
  • Start date Start date
S

Sam

Hi,

This is for my public DNS server running W2K. This is what I have in my DNS
records

My Domain: xyz.com

Host Record: MyHost - x.y.z.101
Alias Record www - MyHost.xyz.com

Now, I'd like to have an FTP site with a unique IP on the same machine
(MyHost). How would I create the necessary records my host so that it will
have 2 IPs i.e. Host Record MyHost x.y.z.102

Thanks,

Sam
 
Now, I'd like to have an FTP site with a unique IP on the same machine
(MyHost). How would I create the necessary records my host so that it will
have 2 IPs i.e. Host Record MyHost x.y.z.102

Create two A (host) records in DNS, they will be offered either
round robin (rotated for load balancing) or on a subnet priority
basis (best match). Depends on your advanced settings.

In a Hosts FILE only the first with the same name would be used
 
I want the DNS to serve the first IP address for the web site and the second
for the FTP site. I don't want it to do a round robin.

Isn't there a way for me to setup two IP's served by the same host so that I
can send the client to a specific IP based on my needs?

Thanks,

Sam
 
DNS -- as generally implemented -- has no knowledge
of ports, applications or intended uses. The request doesn't
say, the server doesn't know, and the reply doesn't
specify. IOW -- not gonna happen.

The exception is the SRV record which has only a
very specialized utility at present.

However most decent routers can be programmed to
pinhole an inside server IP through translation based on
incoming port number (21 vs 80), so perhaps that is where
you want to be looking?

Steve Duff, MCSE
Ergodic Systems, Inc.

Sam said:
I want the DNS to serve the first IP address for the web site and the second
for the FTP site. I don't want it to do a round robin.

Isn't there a way for me to setup two IP's served by the same host so that I
can send the client to a specific IP based on my needs?

Thanks,

Sam
 
What Steve said is true.

There is only one major exception (ok, maybe two but the
second one doesn't count <grin>): SMTP-Email servers
have their own record type which separates their issues.

The second is the SRV but almost no application servers
OR clients use these (AD, DFS, uh?)

You can do what most people do:

ftp.yourdomain.com
www.yourdomain.com
 
In
Herb Martin said:
You can do what most people do:

ftp.yourdomain.com
www.yourdomain.com

Using the same IP addresses for both records.....

:-)

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Hi,

Thanks for all your responses. ftp.mydomain.com and www.mydomain.com is
exactly what I want to do. I just wanted to use separate IP addresses as
they are going to be separate folders on the web server.

Sam


"Ace Fekay [MVP]"
 
Sam said:
Hi,

Thanks for all your responses. ftp.mydomain.com and www.mydomain.com is
exactly what I want to do. I just wanted to use separate IP addresses as
they are going to be separate folders on the web server.

We still aren't communicating clearly, I think.

You don't have to use separate IP addresses to separate
FTP and HTTP.

You MIGHT need to do that if you wanted to separate two
different WEB sites OR two different FTP sites on the same
physical server (there are other common choices, "host headers"
and "ports" in HTTP however.)

If you have two different services they are already distinguish
(in almost all cases) by the port number and not only CAN
you put the content in different places this is almost always the
way everyone does it.

If you want this to work you just make two A records, one for
FTP and one for the Web (http) server and use the same address
with the different names.

(If the server already has a Name/IP A record you can also use
a pair of CNAME --aliases-- for the FTP and Web servers.)
 
Got it. Thanks Herb.

Sam


Herb Martin said:
We still aren't communicating clearly, I think.

You don't have to use separate IP addresses to separate
FTP and HTTP.

You MIGHT need to do that if you wanted to separate two
different WEB sites OR two different FTP sites on the same
physical server (there are other common choices, "host headers"
and "ports" in HTTP however.)

If you have two different services they are already distinguish
(in almost all cases) by the port number and not only CAN
you put the content in different places this is almost always the
way everyone does it.

If you want this to work you just make two A records, one for
FTP and one for the Web (http) server and use the same address
with the different names.

(If the server already has a Name/IP A record you can also use
a pair of CNAME --aliases-- for the FTP and Web servers.)
 
Back
Top