10 More Discussions You Might Find Interesting
1. IP Networking
Hi @all,
I try to connect 2 LANs with IPSec/Openswan
LAN 1: 192.168.0.0/24
LAN 2: 192.168.1.0/24
This is my Config:
conn HomeVPN # # Left security gateway, subnet behind it, nexthop toward right. left=192.168.1.29 ... (1 Reply)
Discussion started by: bahnhasser83
1 Replies
2. IP Networking
Q: "Does Cisco 1921 router support,, act as an endpoint for, site to site VPNs using IPSec? If so, how many? "
A: If you get the Cisco 1921/k9 with the security services bundle then it will have built in security features. Cisco, typically includes IP Sec tunnels I believe as part of that... (0 Replies)
Discussion started by: Ayaerlee
0 Replies
3. IP Networking
Hi,
I am trying to establish vpn between my linux server and cisco asa at client side.
I installed openswan on my cent os.
Linux Server
eth0 - 182.2.29.10
Gateway - 182.2.29.1
eth1 - 192.9.200.75
I have simple IPtables Like
WAN="eth0"
LAN="eth1" (0 Replies)
Discussion started by: ashokvpp
0 Replies
4. Solaris
Hi All ,
I have 2 DNS servers (BIND 9.6.1 -Solaris 10) .Its configured as master ,slave serves .Now i am recieving error messages related to zone transfer in both the servers as mentioned below .
Primar Server
named: client x.x.x.x#40825: transfer of './IN': sending zone data: ran... (1 Reply)
Discussion started by: sandeep.tk
1 Replies
5. Solaris
I have two physical servers, with zones that mount local storage.
We were using "raw device" in the zonecfg to point to a metadevice on the global zone (it was not mounted in the global zone at any point).
It failed to mount on every boot because the directory existed in the zone.
I... (6 Replies)
Discussion started by: BG_JrAdmin
6 Replies
6. Solaris
Hi all,
I have a server running an Oracle database that is part of a Solaris M5000 container. Presumably this is referred to as a zone within a cluster, not sure if I get the terminology right.
Anyway, a third-party manages the zone and unfortunately is not "helpful/friendly" to assist me on... (1 Reply)
Discussion started by: newbie_01
1 Replies
7. Solaris
I have an old Sun SparcStation 5 that is running Sun OS 5.7, I'm not sure which commands would allow me to obtain the DNS zone transfer settings?
1.) I'm needing to know if the zone transfers are enabled.
2.) If it is enabled, does it transfer to specific servers
3.) If so, how do I go about... (1 Reply)
Discussion started by: Fhistleb
1 Replies
8. Solaris
Hi,
I have a primary/slave Bind 9 setup running on a Solaris 10 platform. Everything is hunky dorey, except for when I make a zone file change and up the serial the file that is transferred to the slave looses all its comments, and the entries are place in alphabetical order.
I administer many... (1 Reply)
Discussion started by: fulhamfcboy
1 Replies
9. Windows & DOS: Issues & Discussions
Please help. Reply and tell me if you find one. Lots of thanks!
Computek (6 Replies)
Discussion started by: computek
6 Replies
10. IP Networking
Hi all,
How to deny any zone transfer out of my host??? bind 8.2.3
Thank you all,
Regards
:D (2 Replies)
Discussion started by: solvman
2 Replies
named-xfer(8) System Manager's Manual named-xfer(8)
Name
named-xfer - pull BIND/Hesiod zones from another server
Syntax
/usr/etc/named-xfer -z zone_to_transfer -f db_file -s serial_no [ -d debug_level ] [ -l debug_log_file ] [ -t trace_file ] [ -p port ] [ -n
] [ -a auth_type.auth_ver ] servers...
Description
The transfer daemon, is a server that is usually run by the daemon, but it can also be run manually with the given arguments. The transfer
daemon runs on a BIND/Hesiod secondary server and pulls BIND/Hesiod zones from a primary server. This daemon is not run by default, nor
can it be started up from
Options
-z zone_to_transfer
This option is required to pull a zone. The zone_to_transfer argument specifies the name of the BIND/Hesiod zone that
the daemon will transfer, for example, dec.com.
-f db_file This option is required to pull a zone. The db_file argument specifies the name of the file into which the pulled zone
information is placed.
-s serial_no This option is required to pull a zone. The serial_no argument should be set to the current serial number of the SOA
record for the zone zone_to_transfer. If serial_no is set to 0, the zone is always pulled.
-d debug_level The debug_level argument sets the debug level and determines the amount of debug information to be displayed.
-l debug_log_file The debug_log_file argument specifies the file that will contain any debug messages from the zone pull.
-t trace_file The trace_file argument specifies the file that will contain a trace from the zone pull.
-p port The port argument specifies the port that will be used instead of the default nameserver port listed in
-n This option must be used when the daemon is running in the network safe mode. It indicates that the zone pull must be
authenticated.
-a auth_type.auth_ver
This option must be used if the daemon is running in the network safe mode. The auth_type argument indicates what type
of authentication to use and the auth_ver argument indicates what version of the authentication type to use. Currently,
the auth_type must be "kerberos" and the auth_ver must be "one".
servers... The servers argument is a list of Internet addresses from which to pull a zone. If the first host cannot be ddreached,
the transfer daemon will try to pull the zone from the next host listed.
See Also
services(5), named(8), kerberos(8krb)
Guide to the BIND/Hesiod Service
Guide to Kerberos
named-xfer(8)