Sponsored Content
Full Discussion: DNS and two subnets
Special Forums IP Networking DNS and two subnets Post 302863297 by solaris_user on Sunday 13th of October 2013 04:34:11 PM
Old 10-13-2013
DNS and two subnets

Hi guys

I started to work in a small company which doesn't have infrastructure and I need to built it.

My problem is: I am a student with theoretical knowledge but without practical one so I don't have any ideas how to solve my problem.

I installed on CentOS 6.4 DNS and DHCP. This two worked well untill my boss told me to create two subnets. On the first subnet (192.168.1.0/32) we have out workstations and this is usually network on which our partners can connect. On subnet 10.0.0.0/32 I have servers which we need for our work.

Problem is: I don't know to set up corporate network so I can ping servers on subnet 10.0.0.0/32 from subnet 192.168.1.0/32. We don't have any fancy routers and all my servers are virtual, running inside Virtualbox.

On the same CentOS, I installed and configured DHCP and reserved addresses for all my servers, enabled routing, turned off firewall for now and add manually route on my Windows workstation. I can ping server on other subnet by IP address but not with hostname.

Please, help me.
 

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
DLINT(1)						      General Commands Manual							  DLINT(1)

NAME
dlint - Internet Domain Name System (DNS) error checking utility SYNOPSIS
dlint [ -n ] zone DESCRIPTION
DNS administrators can use dlint to scan recursively through the domain records of the fully-qualified zone zone, to get a report on any errors therein. You can scan a zone you own, or anyone else's zone on the Internet. dlint talks directly to a primary or secondary name- server for the zone, to make sure it's working with up-to-date information. dlint also suggests ways of fixing problems instead of just complaining about them like other debugging tools. The argument zone should always have an ending period to indicate it is a fully qualified domain name. OPTIONS
By default, dlint recursively traverses the entire hierarchy below the zone specified. The -n option may be used to disable recursive tra- versal, causing it to only examine the records in the given zone. Note that a zone may or may not contain any number of sub-domains (all of which will be checked with or without this option). EXAMPLES
example% dlint nau.edu. recursively scans the DNS records in zone nau.edu for problems. example% dlint 64.114.134.in-addr.arpa. recursively scans the DNS records associated with IP subnet 134.114.64.0 for problems. You had to already know that 134.114.0.0 was sub- netted. DIAGNOSTICS
The output from dlint is computer parsable, each line has a special meaning. Lines beginning with a semicolon (;) are comments only. Lines beginning with the phrase ``WARNING'' are useful information that you should consider. A warning is not necessarily an error, but may be a problem. Lines beginning with the phrase ``ERROR'' are definite errors and should be dealt with accordingly. EXIT STATUS
0 Successful run, no problems encountered with zone. 1 Successful run, worst problem with zone was a WARNING. 2 Successful run, worst problem with zone was an ERROR. 3 Usage error. 4 A signal interrupted the program run (i.e. user typed interrupt key sequence). BUGS
Dlint doesn't work behind some firewalls because it needs to talk to a root nameserver to get started. Dlint uses the zone transfer mechanism (AXFR) which some nameservers deny to unauthorized hosts. Other nameservers happily return zero records instead of an error, in response to an unauthorized AXFR! That is just wrong. AUTHOR
Paul Balyoz <pab@domtools.com> DISTRIBUTION
http://www.domtools.com/ COPYRIGHT
Copyright (C) 1993-1998 Paul A. Balyoz <pab@domtools.com> This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version. This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MER- CHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details. You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 675 Mass Ave, Cambridge, MA 02139, USA. 18 July 1998 DLINT(1)
All times are GMT -4. The time now is 01:21 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy