01-31-2012
I didn't think of that, thanks for the suggestion. DNS can be a very detailed subject and finding exactly what you need can be very time consuming. At the moment I'm considering the Windows option but will keep that as a plan B.
10 More Discussions You Might Find Interesting
1. IP Networking
I have just started learning Unix on Solaris and have been asked to learn DHCP, DNS and LDAP very quick in order to implement them and maintain.
Does anyone know how to do this or a decent book that will include all the above three which tells you how to install and maintain. All i have found so... (2 Replies)
Discussion started by: ollyparkhouse
2 Replies
2. IP Networking
I have managed to setup my Solaris box to receive an IP number from a DHCP server. In addition, I can ping and telnet between my dhcp server and my solaris box using the IP number. However, I can't resolve addresses by name from my solaris box.
In my nsswitch.conf file I have:
hosts: dns
... (4 Replies)
Discussion started by: marist89
4 Replies
3. UNIX for Dummies Questions & Answers
Hi all,
I'm in the dark about this. I have setup a dhcp server and a DNS server. I'm confuss as to how to have DNS auto update any new clinet that the dhcp has given an ip address for. Can this be done. I think that I'm missing something in the configuration of DHCP. I was told that when a DHCPD... (3 Replies)
Discussion started by: larry
3 Replies
4. IP Networking
I asked a similar type question in the solaris forum but i think this relates closer to networking. I am trying to setup a small NIS environment that is contained within a large company network. The client machines are getting an IP from the companys' Windows DHCP server. The NIS server has a... (3 Replies)
Discussion started by: meyersp
3 Replies
5. Solaris
I'm running Solaris 9 and I need my box to request it's DNS servers off a DHCP server - can I do this? (1 Reply)
Discussion started by: Jdogg
1 Replies
6. IP Networking
I'm not sure it that's the right term for what I'm asking about, but it's the best I could come up with. Here is my situation...
I'm setting up a network using OpenVPN. The clients I'm setting up will need to be able to access their own DNS servers (to resolve internal names at their location)... (4 Replies)
Discussion started by: deckard
4 Replies
7. IP Networking
hello
i am running my sipx server in 192.168.2.14
i would like to configure domain name and host name for this .....
can anyone tell me how to configure dns server and dhcp server so that any body both outside and inside the lan could access the sipx server by their host.domain.com name (1 Reply)
Discussion started by: sudeepiit
1 Replies
8. UNIX for Dummies Questions & Answers
Hi to all.
Sorry for my bad english.
For pure self-educational, not professional, purposes, I am studying how to configure a server with several services operating on it.
For my experiment I'm using VirtualBox 3.1.4 on a WinXP host with 3 FreeBSD guests; one acts as a DHCP + DNS server; the... (0 Replies)
Discussion started by: marboxer
0 Replies
9. UNIX for Advanced & Expert Users
Is dnsmasq important for dhcp to setup dns? (3 Replies)
Discussion started by: cokedude
3 Replies
10. IP Networking
Let's say I have a home network containing a server that acts as the resident gateway and serves dhcp and dns requests. Laptop A is frequently connected and disconnected from the network as it is used as a travel computer. Is there a secure way to make sure that whenever laptop A is connected to... (3 Replies)
Discussion started by: Zygomorph
3 Replies
LEARN ABOUT DEBIAN
xpamethod
xpamethod(7) SAORD Documentation xpamethod(7)
NAME
XPAMethod - XPA Communication Methods
SYNOPSIS
XPA supports both inet and unix (local) socket communication.
DESCRIPTION
XPA uses sockets for communication between processes. It supports three methods of socket communication: inet, localhost, and unix. In gen-
eral, the same method should be employed for all XPA processes in a session and the global environment variable XPA_METHOD should be used
to set up the desired method. By default, the preferred method is "inet", which is appropriate for most users. You can set up a different
method by typing something like:
setenv XPA_METHOD local # unix csh
XPA_METHOD=local; export XPA_METHOD # unix sh, bash, windows/cygwin
set XPA_METHOD=localhost # dos/windows
The options for XPA_METHOD are: inet, unix (or local), and localhost. On Unix machines, this environment setup command can be placed in
your shell init file (.cshrc, .profile, .bashrc, etc.) On Windows platforms, it can be placed in your AUTOEXEC.BAT file (I think!).
By default, inet sockets are used by XPA. These are the standard Internet sockets that are used by programs such as Netscape, ftp. etc.
Inet sockets utilize the IP address of the given machine and a (usually random) port number to communicate between processes on the same
machine or between different machines on the Internet. (Note that XPA has an Access Control mechanism to prevent unauthorized access of XPA
access points by other computers on the Net). For users connected to the Internet, this usually is the appropriate communication method.
For more information about setting up XPA communication between machines, see Communication Between Machines.
In you are using XPA on a machine without an Internet connection, then inet sockets are not appropriate. In fact, an XPA process often will
hang for many seconds while waiting for a response from the Domain Name Service (DNS) when using inet sockets. Instead of inet sockets,
users on Unix platforms can also use unix sockets (also known as local sockets). These sockets are based on the local file system and do
not make use of the DNS. They generally are considered to be faster than inet sockets, but they are not implemented under Windows. Use
local sockets as a first resort if you are on a Unix machine that is not connected to the Internet.
Users not connected to the Internet also can use localhost sockets. These are also inet-type sockets but the IP address used for the local
machine is the localhost address, 0x7F000001, instead of the real IP of the machine. Depending on how sockets are set up for a given plat-
form, communication with the DNS usually is not required in this case (though of course, XPA cannot interact with other machines). The
localhost method will generally work on both Unix and Windows platforms, but whether the DNS is required or not is subject to individual
configurations.
A final warning/reminder: if your XPA-enabled server hangs at startup time and your XPA_METHOD is inet, the problem probably is related to
an incorrect Internet configuration. This can be confirmed by using the unix method or (usually) the localhost method. You can use these
alternate methods if other hosts do not need access to the XPA server.
SEE ALSO
See xpa(7) for a list of XPA help pages
version 2.1.14 June 7, 2012 xpamethod(7)