search for: myzone

Hi, all! There is no check of NS records in this document https://wiki.samba.org/index.php/Verifying_and_Creating_a_DC_DNS_Record For example, with two DCs at myzone $ host -t NS myzone dc1 (or dc2, or myzone) must return two records: myzone name server dc1.myzone. myzone name server dc2.myzone. $ host -t NS _msdcs.myzone dc1 (or dc2, or myzone) must return two records: _msdcs.myzone name server dc1.myzone. _msdcs.myzone name server dc2.myzone. Is it right...

Hi, a simple question.. is add dataset not part of zonecfg ? global# zonecfg -z myzone (OK) zonecfg:myzone> add dataset (fails as there is no dataset option) zonecfg:myzone> add zfs (fails as there is no dataset option) Basically how do I add a dataset to a zone ? Thanks Roshan please cc me pererar at visa.com

>> You''re right, if the package content from the global zone is >> reflected in all zones, the necessary files are already there. >> >> Typically I try to keep additional installed packages as >> independent as possible. So all additional software packages have >> the following parameters set in the pkginfo file: >> >>

I''m following the example provided in the type reference under ''zone'', i.e.: zone{myzone: autoboot=>true, create_args=>"-b", ip=>"nge0:10:130.55.201", path=>"/zoneds/%s", realhostname=>"myzone.example.com", sysidcfg=>template(sysidcfg...

...ast (e.g. "nslookup printer" returned the IP address of my printer). After adding the following line in /etc/named.conf according to the HOWTO: include "/usr/local/samba/private/named.conf"; ...I now get an error from samba_dlz: named: samba_dlz: Failed to configure zone 'myzone.priv' named: loading configuration: already exists If I comment-out my zone in /etc/named.conf, Samba4 works fine (it can even update the DNS database), but I can of course no longer access my devices, e.g. nslookup printer returns: aschweiz ~> nslookup printer Server: 172.16.1.18 Address...

Folks, I just posted an updated Crossbow virtualization architecture document. The new revision is available at: http://opensolaris.org/os/project/crossbow/Docs/crossbow-virt.pdf The main changes are the addition of support for multiple MAC addresses per client, and an explicit separation between consolidation private and project private MAC API entry points. See in particular the