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
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
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
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
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
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
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
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
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
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
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
dns(n) dns dns(n)
NAME
dns - Tcl Domain Name Service Client
SYNOPSIS
package require Tcl 8.2
package require dns ?1.0.1?
::dns::resolve query ?options?
::dns::configure ?options?
::dns::name token
::dns::address token
::dns::cname token
::dns::status token
::dns::error token
::dns::reset token
::dns::wait token
::dns::cleanup token
DESCRIPTION
The dns package provides a Tcl only Domain Name Service client. You should refer to RFC 1034 and RFC 1035 for information about the DNS
protocol or read resolver(3) to find out how the C library resolves domain names. The intention of this package is to insulate Tcl scripts
from problems with using the system library resolver for slow name servers. It may or may not be of practical use. The package also
extends the package uri to support DNS URIs or the form dns:what.host.com or dns://my.nameserver/what.host.com. The dns::resolve command
can handle DNS URIs or simple domain names as a query.
Note: This package uses TCP to query DNS servers as the tcl core does not implement UDP networking. This means that this module will not
work if DNS over TCP is blocked by a firewall, or not accepted by the chosen nameserver.
COMMANDS
::dns::resolve query ?options?
Resolve a domain name using the DNS protocol. query is the domain name to be lookup up. This should be either a fully qualified
domain name or a DNS URI.
-nameserver hostname or -server hostname
Specify an alternative name server for this request.
-protocol tcp|udp
Specify the network protocol to use for this request. Can be one of tcp or udp. However only tcp is currently implemented in
the package.
-port portnum
Specify an alternative port.
-search domainlist
-timeout milliseconds
Override the default timeout.
-type TYPE
Specify the type of DNS record you are interested in. Valid values are A, NS, MD MF, CNAME, SOA, MB, MG, MR, NULL, WKS, PTR,
HINFO, MINFO, MX, TXT, AXFR, MAILB, MAILA and *. See RFC1035 for details about the return values.
-class CLASS
Specify the class of domain name. This is usually IN but may be one of IN for internet domain names, CS, CH, HS or * for any
class.
-recurse boolean
Set to false if you do not want the name server to recursively act upon your request. Normally set to true.
-command procname
Set a procedure to be called upon request completion. The procedure will be passed the token as its only argument.
::dns::configure ?options?
The ::dns::configure command is used to setup the dns package. The server to query, the protocol and domain search path are all set
via this command. If no arguments are provided then a list of all the current settings is returned. If only one argument then it
must the the name of an option and the value for that option is returned.
-nameserver hostname
Set the default name server to be used by all queries. The default is localhost.
-protocol tcp|udp
Set the default network protocol to be used. Defaults to tcp.
-port portnum
Set the default port to use on the name server. The default is 53.
-search domainlist
Set the domain search list. This is currently not used.
-timeout milliseconds
Set the default timeout value for DNS lookups. Defaults to 30 seconds.
::dns::name token
Returns a list of all domain names returned as an answer to your query.
::dns::address token
Returns a list of the address records that match your query.
::dns::cname token
Returns a list of canonical names (usually just one) matching your query.
::dns::status token
Returns the status flag. For a successfully completed query this will be ok. May be error or timeout or eof. See also ::dns::error
::dns::error token
Returns the error message provided for requests whose status is error. If there is no error message then an empty string is
returned.
::dns::reset token
Reset or cancel a DNS query.
::dns::wait token
Wait for a DNS query to complete and return the status upon completion.
::dns::cleanup token
Remove all state variables associated with the request.
EXAMPLES
% set tok [dns::resolve www.tcl.tk]
::dns::1
% dns::status $tok
ok
% dns::address $tok
199.175.6.239
% dns::name $tok
www.tcl.tk
Using DNS URIs as queries:
% set tok [dns::resolve "dns:tcl.tk;type=MX"]
% set tok [dns::resolve "dns://l.root-servers.net/www.tcl.tk"]
SEE ALSO
resolver(5)
AUTHORS
Pat Thoyts
KEYWORDS
DNS, resolver, domain name service
dns 1.0.1 dns(n)