Sponsored Content
Full Discussion: dns and hosts file
Special Forums IP Networking dns and hosts file Post 42139 by norsk hedensk on Wednesday 22nd of October 2003 03:59:18 PM
Old 10-22-2003
if you have a small network (~4 systems) you might as well just add them to your /etc/hosts file. however, if you already have a private DNS server running on your internal network, then yeah add everything in there. that helps to keep consistency in your network and you wont have to worry about one /etc/hosts being outdated.
 

10 More Discussions You Might Find Interesting

1. UNIX for Advanced & Expert Users

Virtual Hosts and Alteon DNS conflicts

Hi, This is more of a verification rather than a question of technical nature. This is based on solaris 10 machine Could we use Virtual hosts (within our hosts file): 123.1.1.10 virtual_host_name 123.1.1.10 host_A (note: 123.1.1.10 - host_A is also in our DNS server entry) And... (0 Replies)
Discussion started by: jackola
0 Replies

2. Solaris

/etc/nsswitch.conf hosts ldap dns

Hi all Is there any reason to have "hosts ldap dns" as line in /etc/nsswitch.conf ? My understanding is that ldap does not contain any host information..(?) Best regards...Ludwig (1 Reply)
Discussion started by: ludwig
1 Replies

3. Solaris

Which lookup tool query both hosts and DNS server?

As i understand, host/nslookup/dig only query DNS server to resolve name to ip. ping can query both, but it seems if ping is blocked, ping won't return IP. traceroute can query both, but i am not able to test if traceroute is blocked, What is the result? Neither ping/traceroute is... (3 Replies)
Discussion started by: honglus
3 Replies

4. IP Networking

Hosts file ignored, no DNS entry but still routes!!

Hi all, I have an entry in my hosts file on a server called tractor as follows: 10.67.34.128 digger-m2m digger I have a DNS server configured but it doesn't seem to know about digger. When I do an nslookup on tractor for digger i get the following: new_dns1.oam.uk can't find digger: Non... (0 Replies)
Discussion started by: Donkey25
0 Replies

5. AIX

aix tcp wrappers hosts.allow hosts.deny?

hi all just installed the netsec.options.tcpwrapper from expansion pack, which used to be a rpm, for my aix 6.1 test box. it is so unpredictable. i set up the hosts.deny as suggested for all and allow the sshd for specific ip addresses/hostnames. the tcpdchk says the hosts allowed and... (0 Replies)
Discussion started by: wf201626
0 Replies

6. IP Networking

Newbie BIND DNS question: resolving upstream hosts?

Old skool UNIX and Linux geek here, but newbie to the world of DNS and bind. I've recently been tasked with replacing our DNS infrastructure, currently on Windows, with a RHEL based solution. And I assume that means using bind, which I've not used before. Here's my question: Suppose our company... (3 Replies)
Discussion started by: lupin..the..3rd
3 Replies

7. Proxy Server

IPtable rules for DNS/http/https traffic for specific hosts only, not working.

Hi there, I have a VPS and am working on a little side project for myself and friend which is a DNS proxy. Everything was great till recently. My VPS IP has been detected by some botnet or something, and I believe SMURF attacks are occuring. The VPS provider keeps shutting down my VPS... (3 Replies)
Discussion started by: phi0x
3 Replies

8. AIX

Use of /etc/hosts files in resolving the dns name

Hello, For what purpose /etc/hosts file is used.I mean how any request coming to a DNS server or a switch would know that which name and ip are configured in /etc/hosts files of a server? Best regards, Vishal (3 Replies)
Discussion started by: admin_db
3 Replies

9. AIX

How to find which internal hosts still using my DNS service ? Please help

Hello guys, I am new to AIX . I have two AIX v5.3 servers running BIND DNS service on them. The plan is to shut down only the DNS service on them, but in order to do that I have to determine which internal hosts are still using the servers to resolve DNS queries. Can you please advice on... (2 Replies)
Discussion started by: tihomirvs
2 Replies

10. Solaris

How to copy a tar file on a series of remote hosts and untar it on those hosts?

Am trying to copy a tar file onto a series of remote hosts and untar it at the destination. Need to do this without having to do multiple ssh. Actions to perform within a single ssh session via shell script - copy a file - untar at destination (remote host) OS : Linux RHEL6 (3 Replies)
Discussion started by: sankasu
3 Replies
SLIRPVDE(1)						      General Commands Manual						       SLIRPVDE(1)

NAME
slirpvde - Virtual Distributed Ethernet-Slirp interface SYNOPSIS
slirpvde OPTIONS [ socketdir ] DESCRIPTION
slirpvde is a slirp interface for a VDE network. Slirpvde connects all the units (virtual or real machines) to the network of the host where slirpvde runs as it were a NAT/Masquerading router. The default route is the node 2 (10.0.2.2 in the default network configuration) and DNS is re-mapped in node 3 (10.0.2.3). Slirpvde runs using standard user privileges (no need for root access): all the connections are re-generated by slirpvde itself. IPv4 only. IPv6 is still unsupported (will be supported when slirpvde will be rewritten using the LWIPv6 network stack). OPTIONS
-s, --sock, --socket, --vdesock, --unix directory specify the VDE switch directory (default /var/run/vde.ctl). The VDE switch directory can be also specified at the end of the com- mand, as illustrated by the optional parameter socketdir in the synopsis section, above. When '-' is used in place of the VDE switch directory, slirpvde works as a plug (see vde_plug(1)). The command: dpipe vde_plug = ssh remote.machine.org slirpvde - which is the same as: dpipe vde_plug = ssh remote.machine.org slirpvde -s - connects the default local switch to a remote slirpvde. -p, --pidfile filename specify the name of the file which contains the PID of slirpvde. -g, --group group specify the UNIX group for the VDE communication socket. -m, --mod mode specify the octal UNIX permissions for the VDE communication socket. -P, --port port specify the port of the vde switch whern slirpvde must be connected. -d, --daemon detach from terminal and run slirpvde in background. -H, --host address [ / masklen ] specify the host address (default 10.0.2.2/24). This option automatically defines the network. e.g. -H 192.168.55.1 or: --host 10.1.2.3/16 The default value for masklen is 24. If the host part of the address is zero this option defines only the network. The default host addr is addr 2, the default dns proxy is 3. e.g. -H 10.1.0.0/16 defines the network only. The host address is 10.1.0.2 and the DNS proxy 10.1.0.3. -n, --network address [ / masklen ] specify the network address (default 10.0.2.0/24). Deprecated, it has been included for back compatibility only. It is an alias of -H, --host. -N, --dns address Specify the address of the dns server. If this is an address inside the slirp network, slirvde acts as a dns proxy on that address. The slirpvde dhcp server sends this dns address to the clients. By default this is the host number 3 in the slirpvde network. Using the default network it is 10.0.2.3. Warning: do not use the same address for host and dns. -D, --dhcp turn on the DHCP server for the network autoconfiguration of all the units connected to the VDE. It is possible to specify the start address assigned by the DHCP server as follows: --dhcp=10.1.1.44 DHCP assign addresses starting at host number 15 by default. Using the default network it starts from 10.0.2.15 -L port:vde_host:vde_hostport specifyes a TCP port redirection. All the TCP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -U port:vde_host:vde_hostport specifyes a UDP port redirection. All the UDP packets received by the host running slirpvde at port port will be forwarded to vde_host at port vde_hostport. -X vde_host[:display.[screen]]i redirect a X window screen of a virtual machine. Slirpvde gets the first unused X display on the host running slirpvde and redirects all the requests to vde_host. display and screen] must be specified when different from :0.0. -x port:unix_socket_path] redirect a port of the virtual router (usually 10.0.2.2) to a unix stream socket. It is used for example to redirect a X display of the hosting computer on the virtual network. e.g. -x6000:/tmp/.X11-unix/X0. (A suitable xhost configuration is needed (e.g. 'xhost local:'). -t, --tftp pathname slirpvde enables a tftp server sharing (read-only) the directory at pathname. -q, --quiet Quiet; do not write anything to standard output. NOTICE
Virtual Distributed Ethernet is not related in any way with www.vde.com ("Verband der Elektrotechnik, Elektronik und Informationstechnik" i.e. the German "Association for Electrical, Electronic & Information Technologies"). SEE ALSO
vde_switch(1), vde_plug(1), vde_plug2tap(1), dpipe(1). AUTHOR
VDE is a project by Renzo Davoli <renzo@cs.unibo.it>. This tool includes software developed by Danny Gasparovski: Slirp code is by Danny Gasparovsky. Bootp/DHCP code is by Fabrice Bellard. Virtual Distributed Ethernet June 15, 2008 SLIRPVDE(1)
All times are GMT -4. The time now is 07:05 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy