Adding a second Class c

  • Thread starter Thread starter Michael
  • Start date Start date
M

Michael

Hey everyone,

I have a problem, I am currently running a dns server with a class c
designated to it already I just recieved a second class c and I need to have
the same network (i.e. bccisp.net on 66.118.41.x) control the second class c
which is on network 12.5.104.x. The two networks in question are given per
two different providers.

Network one is provided by a company called Texlink.com and the network is
66.118.41.x
Network two is provided by AT & T and it's network is 12.5.104.x

How do I add the second network in my DNS server to be part of bccisp.net's
network.

If I haven't explained well I apologize. Prompt me and I will explain as
best I can.

Some one told me to add a second nic card to my server and then put forward
zone from 12 network to the 66 network there has to be a better way to do
this.

thanks,
--
Michael A Cooper
BCCISP.net
http://www.bccisp.net
281-854-2079
"Technology that counts, voices that matter!"
 
As far as DNS goes, it doesn't care who your ISPs are, and it (more or less) doesn't much know about subnets. Just populate the host
records you want with the IP addresses you care to assign to those names. "Forward zones" have nothing to do with forwarding data
traffic - that term just refers to a 'forward' lookup (ie a name to an IP address).

I believe you are asking about how to route traffic between your two different networks. This is not done by DNS -- except to the
extent that people trying to reach your servers will do public DNS lookups to get the corresponding IP address to talk to.

You would typically do this on the server by enabling the routing and remote access ("RRAS") service and configuring it. This gives
you the opportunity to setup network access rules and manage the ports and traffic you want to allow.

However, understand that a single Windows machine will only use one default gateway at a given time. Which is to say that even if
you have two NICs to service the incoming traffic for the two different networks, general outbound/return traffic will only flow out
one of them -- whichever of your public IPs you designate as the default gateway IP with the lowest cost. You cannot assign
different default gateways to different applications or ports running on the same server.

This may or may not be a problem -- for example if one of your routers is a NAT device it won't understand the return traffic for
the other connection for which it has no corresponding mappings. Likewise, this limitation mostly eliminates any opportunity to
load-balance outbound traffic across the two connections.

So people typically find that it is advantageous to get a firewall/router with interfaces to handle the multiple connections, and
then do the routing and traffic management at that point. To do real load balancing and traffic failover requires specialized
routing protocols and generally requires that your incoming lines derive from the same ISP. You might want to post this question in
..ras_routing.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.
 
Hey Steve,

Thank you for the information it is very helpful.

You do relize that I have two networks in two physically different locations
correct?

I have two different physical locations for this network and as of last
month two networks assigned.

In location one my equipment is physically co-located and on a 66.118.41.x
network behind a Linksys RV016 VPN Router.

In location two I am on a 12.5.104.x network behind a Cisco 2650 Router.

So you are saying as long as I route from network 1 to network 2 properly
and Vice versa I should be okay and getting the DNS to work shouldn't be to
tuff?

I have been reading for days on these subjects trying to make sense of it, I
apologize for the stupid questions but I am so new to this it should be a
crime.

Thanks in Advance,
--
Michael A Cooper
BCCISP.net
http://www.bccisp.net
281-854-2079
"Technology that counts, voices that matter!"
 
No, thank you for clarifying - I didn't realize that - I assumed when you spoke of adding two NICs we were talking about lines to
the same site.

From what I understand I don't see that you'd need to route these networks at all, the Internet itself takes care of that. If you
have a VPN or a separate site-to-site backbone there are other considerations. You should post a question to .ras_routing if you
aren't sure. I would probably toss the VP016 and get something a little more robust if that is a choice.

None of this matters to DNS. At the most basic level, you just put the host records you want for the IP addresses you want in your
DNS. People who query your DNS for those names will then get those IP addresses. How the data then gets routed from those people to
that IP is a completely separate operation.

Steve Duff, MCSE, MVP
Ergodic Systems, Inc.

I cannot really say wheter it is necessary for you to route between these networks at all since they
 
Back
Top