Sponsored Content
Full Discussion: DNS and two subnets
Special Forums IP Networking DNS and two subnets Post 302867199 by DGPickett on Wednesday 23rd of October 2013 04:04:32 PM
Old 10-23-2013
DNS is about 3 things, finding Domain servers, reverse lookup of all IPs including local, and forward lookup of hosts including local. The last part is divided into twoareas, dynamic supporting DHCP and fixed for servers. The forward and reverse domains need to be known to the parent domain. Reverse IP lookup is done using domain inaddr.arpa.IP, so in addition to servers being installed in the local domain, somehow all IPs have to be installed into inaddr.arpa.

New subnets is about configuring them on a router so they get routed to. Manual routes is a hack. Giving them reverse DNS support is also nice. But do not otherwise confuse domains and subnets. One is in the Name space, the other in IP address space. DNS lookup is hierarchical through name servers, although local overrides are possible (I once configured local DNS so aol.com was our firewall, where there was a proxy to the real AOL.) and the IP routing world, handled by routers. Now, any host with two NICs is a potential (when IP forwarding is turned on) router. Best practices is to use dedicated routers, so non-router hosts just point to the router(s) at the head of their subnet. Routing protocols or manual settings on routers establish the routes for all hosts to and from your hosts. You could use any box as a router (even if it is also a server):
  1. configure it with 2 or more NICs, for each child subnet and the parent subnet,
  2. IP Forwarding turned on and
  3. higher level router(s) as its default route
  4. set the child subnet hosts to see it as the default route,
  5. To enable routing in, either:
    • install and activate a routng protocol compatible to the parent router(s) (you can look for their packets to discover what is running) or
    • set the parent routers manually to see it as the route for your subnets.
When hosts send it traffic, it will forward to the a local subnet or up to its default.

For redundancy, my guess is that you do it twice. I suspect a host with two routes will use one until it stops working and then try the other. But there are many ways to do this, like two hosts using the same IP but only if the other is not, like a cluster.

Last edited by DGPickett; 10-23-2013 at 05:19 PM..
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

communication problem between two subnets

We have two Sun Sparc systems running on the xxx.xxx.1.xxx network and can be access fine by machines on that subnet. We are able the ping one of the machines from the xxx.xxx.2.xxx network, but we are not able to ping or communicate with the other machine on the (1) subnet from the (2) subnet. ... (8 Replies)
Discussion started by: pyerj
8 Replies

2. AIX

Printing across subnets (Xerox)

All, I have a pSeries 550 and several Xerox printers I need to print to from there. I can define the printers via the Xerox "xpadmin" utility for all the machines locally (in my building, .244.xxx subnet), but if I go to a different subnet (say .131.xxx) I can not apply any changes. I can... (1 Reply)
Discussion started by: kjbaumann
1 Replies

3. IP Networking

Routing across different subnets

I have a routing problem that I need to solve for both Windows and Linux. In our test lab, I've set up a small network that is separated from the rest of the work by a firewall. One interface is on the 15.8.152 network, the other is on the 192.168.100 network. I can already get to the... (2 Replies)
Discussion started by: thomn8r
2 Replies

4. Solaris

Solaris as router between two subnets

I have two networks which is not connected to each other. Each network has its own internet connection. I also have one Solaris machine with two NICs connected to both of the networks. How do I use the Solaris to connect both network so that hosts from either side of the network can... (9 Replies)
Discussion started by: Ahmad Pakhri
9 Replies

5. UNIX for Advanced & Expert Users

solaris zones on different subnets

Greetings, Having an issue with a multihomed global zone hosting zones on different subnets. The issue is with the dev zone that is hosted on the non-default network. Any help, other than going to exclusive IP, as I have one card for admin ntwk for both zones, would be appreciated. ... (1 Reply)
Discussion started by: 22blaze
1 Replies

6. Solaris

Jumpstart server over Multiple subnets

Hi, I need some recommendations as to how I can create a single jumpstart server over multiple subnets and what would be the best physical server for this purpose. Thanks . (1 Reply)
Discussion started by: gunnervarma
1 Replies

7. IP Networking

Freebsd Bind DNS server - multiple subnets

Hello all, I have configured Freebsd 8.1 Bind DNS as DNS server for intrenal domain and clients on one subnet 192.168.10.0/24 . What do I have to change in zone file and in in-addr.arpa zone file if I have two additional subsets 192.168.20.0/24 and 192.168.30.0/24? Do I have to create another... (0 Replies)
Discussion started by: kreno
0 Replies

8. Red Hat

DHCP & DNS - Clients get IP but don't register in DNS

I am trying to setup a CentOS 6.2 server that will be doing 3 things DHCP, DNS & Samba for a very small office (2 users). The idea being this will replace a very old Win2k server. The users are all windows based clients so only the server will be Linux based. I've installed CentOS 6.2 with... (4 Replies)
Discussion started by: FireBIade
4 Replies

9. UNIX for Advanced & Expert Users

Rsyslog Monitoring Multiple Subnets

Hello, I have a rsyslog server configured on a server with two IP's on different Class C subnets. By default, it receives all logs from servers on these two subnets. The problem I have is that I want the Rsyslog server to monitor other subnets as well. Is there anyway to do this? I have searched... (0 Replies)
Discussion started by: mojoman
0 Replies

10. Shell Programming and Scripting

Breaking out ip subnet to smaller subnets

I have a script and it works fine, but I am sure this can be shrunk down to something much better. I would appreciate someone taking a crack at it for me. What it does is take the ip block submitted and breaks it out down to /24's. #!/bin/ksh ipadd=${1} octet1=`echo $ipadd | nawk -F.... (3 Replies)
Discussion started by: numele
3 Replies
IRDPD(8)						      System Manager's Manual							  IRDPD(8)

NAME
irdpd - internet router discovery protocol daemon SYNOPSIS
irdpd [-bsd] [-U udp-device] [-I ip-device] [-o priority-offset] DESCRIPTION
Irdpd looks for routers. This should be a simple task, but many routers are hard to find because they do not implement the router discov- ery protocol. This daemon collects information that routers do send out and makes it available. At startup irdpd sends out several router solicitation broadcasts. A good router should respond to this with a router advertisement. If a router advertisement arrives then no more solicitations are sent. The TCP/IP server has filled its routing table with the info from the advertisement, so it now has at least one router. If the advertisement is sent by a genuine router (the sender is in the table) then the irdpd daemon goes dormant for the time the advert is valid. Routers send new adverts periodically, keeping the daemon silent. Otherwise irdpd will listen for RIP (Router Information Protocol) packets. These packets are sent between routers to exchange routing information. Irdpd uses this information to build a routing table. Every now and then a router advertisement is sent to the local host to give it router information build from the RIP packets. Lastly, if a router solicitation arrives and there is no router around that sends advertisements, then irdpd sends an advertisement to the requestor. Note that this is a direct violation of RFC1256, as no host is supposed to sent those adverts. But alas the world is not always perfect, and those adverts make booting hosts find routers quickly with this help from their brothers. (Of course, they will lose the router soon if they don't have an irdpd daemon themselves.) OPTIONS
-b Broadcast advertisements instead of sending them to the local host only. This may be used to keep (non-Minix) hosts alive on a net without adverts. -s Be silent, do not send advertisements to hosts that ask for them. -d Debug mode, tell where info is coming from and where it is sent. Debugging can also be turned on at runtime by sending signal SIGUSR1 or turned off with SIGUSR2. -o priority-offset Offset used to make the gateway's preferences collected from RIP packets look worse than those found in genuine router adverts. By default -1024. SEE ALSO
set_net_default(8), boot(8), inetd(8), nonamed(8), rarpd(8). BUGS
Under standard Minix this daemon can't listen to two both IRDP and RIP at the same time, so it starts out with IRDP. It switches over to RIP if it can't find a router, or if it threatens to lose its router. It does not switch back. Irdpd may help a host that should not be helped, i.e. if it doesn't have an irdpd daemon with RIP collecting trickery. It will make System Administrators pull out their remaining hair trying to find out why a host can access outside networks for a some time after boot, but goes blind afterwards. AUTHOR
Kees J. Bot (kjb@cs.vu.nl) IRDPD(8)
All times are GMT -4. The time now is 03:24 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy