I've been looking for the best OpenSolaris distribution for hosting Solaris Zones backed by ZFS.
I don't know how many good responses I will get back, but my options are below:
OpenSolaris 2008.5 - I've heard slow updates, but this is good for VPS hosting where we don't want many reboots -- release cycles like RedHat.
Solaris Express Community Edition (SXCE) - Very fast development like Fedora, but bugfixes are released much faster. Downside is much more maintenance to get all those bugfixes.
Nexenta - This is the OpenSolaris kernel built around a GPL userland (Debian based, uses apt, etc). Does anyone have any experience with this? It seems releases are not as fast as SXCE, but quicker than OpenSolaris and it supports all the OpenSolaris features such as Zones/ZFS and even allows for Debian/Ubuntu zones.
Any input would be highly appreciated, especially from those running 1 or more of the above distributions.
Is there any distro that will do EFI without having to mess around with a ton of stuff, and hope it works? I have a Intel Max Mini, and I want to install a *nix distro on it to play with.
This is a tough question cause the distro you choose makes all the difference.
So my question now is if your choices were:
Centos 4 or 5 (32bit or 64bit) Ubuntu (32bit) Debian (32bit)
which would you pick and why?
on a side note I believe that the distro that gets picked the most is the one that has the most servers and if someone were to pick one thats not favored by many then he/she may get a faster server cause there wont be so many VPSs on it. Correct in this assumption?
i "played" a little bit with linux years ago, with a debian based version, but i think i already forgot everything
So this theres this dedicated server that only has linux , one thing that i know that i'll be using for torrents, but not only it, so in general which distro will be easier for me to handle?
I am looking to redirect all web & email services over to a new Server.
Is the best approach to simply repoint the main A record to the new Server IP and this will redirect the traffic? then, i will update the nameservers at the registrar to point to the new server.
I'm in the process of migrating a site to a new server. we're not ready to move email yet, so ideally i would like to just move web traffic at this time. i would like to be able to do this without changing the nameservers with the domain's registrar at this time.
which records to i need to manipulate in order to do this?
can i just change the A record for domain.com to point to a new IP and this won't impact the current email or do i need to move the entire site?
My biggest concern right now is impacting email by moving the everything to the new server.
I'm using ddclient. When the external ip change, ddclient update the A register.
I see that A register updated in the control panel interface.
But that updated IP does not propagate. I have waited more than one hour and do not see the changes spread.
Only when I change the A register inside the control panel for any value and then I change it again into the real value the change is spread and everything works well.
Looks like ddclient not force reload my zone, only when change the ip in the control panel.
I have a windows 2000 server and I would like to configure two domain names, c.com and bnvsaj.c.com and requests to these domains should be forwarded to 192.168.0.1 and 192.168.0.2. How can I configure like this?
After Cpanel update latest release version. I have issue with named.conf. I tried to rebuild named. but..
/scripts/rebuilddnsconfig fixrndc requires a syntactically correct /etc/named.conf. No changes were made to /etc/named.conf.
Problem was:
/etc/named.conf:23: when using 'view' statements, all zones must be in views Anyone can explain me about "/etc/named.conf:23: when using 'view' statements, all zones must be in views"?
This is a clean installation of Plesk, nothing else has been done on the server. After the Plesk 12 Installation I installed the Route53 Extension directly from the Panel.
I authenticated with the Access ID / Secret key, as soon as I start creating Domains I get duplicated zones in Route53. When I delete the Domain from Plesk only one Domain gets deleted, the other one remains.
This is my debug log where I see it executes the script twice:
I am setting up slave DNS servers using bind 9.8 on CentOS 6. I have followed the procedure here successfully: [URL] ....
The problem is that even if I see something like the following in named.run on the slave server (which implies the rndc connection worked):
received control channel command 'addzone xxxxxxxx.com { type slave; file "xxxxxxxx.com"; masters { x.x.x.x; }; };' received control channel command 'refresh xxxxxxxx.com' received control channel command 'addzone xxxxxxxx.com { type slave; file "xxxxxxxx.com"; masters { x.x.x.x; }; };'
I still cannot query any entries for that zone from the slave DNS server:
$ dig @y.y.y.y xxxxxxxx.com ; <<>> DiG 9.8.3-P1 <<>> @y.y.y.y xxxxxxxx.com ; (1 server found) ;; global options: +cmd
[Code] .....
I also do not see any zone files created anywhere on the slave server.
I have recently started using the slave DNS manager in the Plesk extension library. I've found that even for DNS zones that are switched off in Plesk, failed sync/transfers still try to take place between the slave and master. Why is this so?
Shouldn't turning the DNS functionality off in Plesk remove the zone from the slave DNS server?
When a domains DNS functionality is turned off, it removed the zone info from the master, but no command is issued to remove it from the slave??
Domain that is trying to sync/transfer: example.com Plesk/Master server: 111.11.11.111 Slave DNS: 222.222.22.222
Code: May 6 08:51:39 ns2 named[1178]: zone example.com/IN: refresh: unexpected rcode (REFUSED) from master 111.11.11.111#53 (source 0.0.0.0#0) May 6 08:51:39 ns2 named[1178]: zone example.com/IN: Transfer started. May 6 08:51:40 ns2 named[1178]: transfer of 'example.com/IN' from 111.11.11.111#53: connected using 222.222.22.222#53166
