Sponsored Content
Full Discussion: bind zone transfer?
Special Forums IP Networking bind zone transfer? Post 8635 by Andy Hibbins on Monday 15th of October 2001 04:30:04 PM
Old 10-15-2001
solvman,

You can also use the "allow-transfer" in the options section of the named.conf file.

an example is:

allow-transfer { 192.168.1.1; 192,168.1.2};

Andy H
 

9 More Discussions You Might Find Interesting

1. Shell Programming and Scripting

zone transfer - free site

Dear all, Did anyone in this forum know site that offer free DNS zone transfer? if anyon know, please reply my message. Thanks (0 Replies)
Discussion started by: unknown2205
0 Replies

2. Solaris

Bind zone transfer recategorises zone file?

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

3. Solaris

How to obtain DNS Zone transfer settings on Sun OS 5.7

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

4. Solaris

Zone failes to boot due to mount issue, dir exists in zone.

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

5. Solaris

DNS zone transfer Problem.

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

6. Solaris

showing 2 different time zones in global zone and nonglobal zone

can some one help me out as it is showing 2 different time zones in global zone and nonglobal zone .In global zone it is showing in GMT while in nonglobal zone i it showing as PDT. System in running with solaris 10 (3 Replies)
Discussion started by: ravijanjanam12
3 Replies

7. Ubuntu

Bind dns server zone file

I have a couple of zone conf files for the BIND server. There are some records that contains the "IN" statement and some do not. But anyway this works. So my question is what this "IN" is intended for? Here is the zone file example: ORIGIN . $ttl 60 example.com. IN SOA ... (4 Replies)
Discussion started by: andriesh
4 Replies

8. UNIX for Advanced & Expert Users

Solaris 10: I forgot to detach a zone before zpool export. Uninstall zone?

Dear all, recently, I migrated a solaris zone from one host to another. The zone was inside of a zpool. The zpool cotains two volumes. I did the following: host1: $ zlogin zone1 shutdown -y -g0 -i0 #Zone status changes from running to installed $ zpool export zone1 host2: $ zpool... (2 Replies)
Discussion started by: custos
2 Replies

9. Solaris

Solaris 11 zone has no external network access (except to Global Zone)

Hi, hoping someone can help, its been a while since I used Solaris. After creating a NGZ (non global zone), the NGZ can access the GZ (Global Zone) and the GZ can access the NGZ (using ssh, zlogin) However, the NGZ cannot access any other netwqork devices, it can't even see the default router ... (2 Replies)
Discussion started by: GazinLincoln
2 Replies
vzmigrate(8)							    Containers							      vzmigrate(8)

NAME
vzmigrate - migrate a container between two OpenVZ servers SYNOPSIS
vzmigrate [-r|--remove-area yes|no] [--ssh=ssh_options] [--rsync=rsync_options] [--keep-dst] [--online] [-v] destination_address CTID DESCRIPTION
This utility is used to migrate a container from one (source) Hardware Node (HN) to another (destination) HN. The utility can migrate either stopped or running container. For a stopped container, simple CT private area transfer is performed (rsync(1) is used for file transfer). For running containers, migration may be offline (default) or online. This program uses ssh as a transport layer. You will need to put ssh public key to destination node and be able to connect to node without entering password. OPTIONS
-r, --remove-area yes | no Whether to remove a container area on source HN for the successfully migrated container. Default is yes. --ssh=options Additional options that will be passed to ssh while establishing connection to destination HN. --rsync=options Additional options that will be passed to rsync(8). You may add options like -z to enable data compression if you are migrating over a slow link. --keep-dst Do not clean synced destination container private area in case of some error. It makes sense to use this option on big container migration to avoid syncing container private area again in case some error (on container stop for example) occurs during first migration attempt. --online Perform online (zero-downtime) migration: during the migration the container hangs for a while and after the migration it continues working as though nothing has happened. -v Verbose mode. Causes vzmigrate to print debugging messages about its progress. Multiple -v options increase the verbosity. The maximum is 3. EXAMPLES
Migration of CT 101 to 192.168.1.130 with downtime: vzmigrate 192.168.1.130 101 Online migration of CT 102 to 192.168.1.130: vzmigrate --online 192.168.1.130 102 EXIT STATUS
0 EXIT_OK Command completed successfully. 1 EXIT_USAGE Bad command line options. 2 EXIT_VE_STOPPED Container is stopped. 4 EXIT_CONNECT Can't connect to destination (source) HN. 6 EXIT_COPY Container private area copying/moving failed. 7 EXIT_VE_START Can't start or restore destination CT. 8 EXIT_VE_STOP Can't stop or checkpoint source CT. 9 EXIT_EXISTS Container already exists on destination HN. 10 EXIT_NOTEXIST Container does not exists on source HN. 12 EXIT_IP_INUSE You attempt to migrate CT which IP address(es) are already in use on the destination node. 13 EXIT_QUOTA Operation with CT quota failed. SEE ALSO
rsync(1). COPYRIGHT
Copyright (C) 2001-2010, Parallels, Inc. Licensed under GNU GPL. OpenVZ 28 Jun 2011 vzmigrate(8)
All times are GMT -4. The time now is 08:58 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy