
Originally Posted by
hostb
1.) I wanted the domains url to remain in the browser address bar for my 'parked' pages. This would not happen using parked domains.
That's Wrong! 
With parked domains, the domain you used to reach the site remains in the URL address bar!
I have many servers with hundreds of parked domains and I can tell you first hand that the parked domains stay in the url bar and you can even navigate to different web pages in the site and the parked domain STILL stays up the URL bar showing as the site you are connected to the entire time!
I can give you hundreds of examples and in each and every one, the domains -- just mere parked domains --- appear
to be the main domain and you are totally and completely unaware they are "parked" domains.
The only time you would get the domain in the URL change is if you used a redirect or a hyperlink to a different domain name but a "parked" domain is NOT a redirect and the domain shown in the address bar *IS* the "parked" domain you typed to originally get to the web site and does not change! Apparently, you somehow got the notion that a parked page is a redirect and gets updated to the main domain when you connect, but that is completely incorrect!
A parked domain is fully a secondary name for the "web account" on the server. It is NOT a redirect to the main address!
(Incidentally redirects can be generated by Apache such as web file redirects or .htaccess redirect commands (OR) by DNS such as using a CNAME record instead of an A record. Parked domains uses "ServerAlias" which is different and the web server cannot distinguish the parked domain from the main domain as they are equals and the server answers to both domains and delivers the content found at DocumentRoot for the account)
Code:
<VirtualHost x.x.x.x:80>
ServerName mydomain.com
ServerAlias www.mydomain.com parkeddomain.com www.parkeddomain.com
DocumentRoot /home/login/public_html
2.)But most importantly for the local domains I sell,
they must resolve correctly to a nameserver for the domains regulator to approve the domain. So in a way they always need
some sort of 'hosting'
Again you are wrong! 
You do not need to setup any hosting account at all!
Most registrars do not require DNS to be setup in advance of hosting but for those few that do (and some countries), you still do NOT need to setup a hosting account but rather just simply the DNS zone file for the domain and nothing more. Drop in a simple zone file pointing to your default shared IP and everything I said before will work just fine and the registrar will be able to resolve the zone for the domain at your DNS servers. So I must put them on my nameservers somehow.
The only way to get the domains onto my nameserver automatically is add them with the cpanel API's as either new, parked or addon
Once again you are wrong!
Setting up "parked" or "addon" domains or hosting accounts is NOTthe ONLY way to get domains in to your nameserver.
There is also "Add a DNS Zone" listed under "DNS Functions" that generates the exact same zone files as creating any of the above but is actually even simpler because you don't have to specify a username or password or anything. Just type the name of the domain and that's it!
Like "parked" and "add-on" domains, adding DNS zones can also be done through the cPanel API functions automatically as well just the same!
My /root/cpanel3-skel/ directly contains a default page for full hosting accounts. So I can't change that.
That's the whole point. You were updating the page for the "hosting accounts" you were creating!
However, for what you are talking about with adding new domains, you really
don't even need to do any of that as you already would have a page setup for the domains before hand and don't even need to setup any hosting account for the new domains in the first place, not until you are actually ready to host the domains and then you can deploy your "full hosting account" skeleton at that time or whatever you want to do!
Setting up the redirect page in the skeleton was just a little extra icing to have redirects AFTER the hosting account was created but is totally optional and completely unnecessary in your case since you already have the page setup for the new domains already anyway from the default IP address page I told you about previously.
I hope my question sounds a little less stupid now.
Actually just the opposite as it makes it more clear you don't have a full grasp on what you can and can't do with Cpanel or how thing operate although that is something we can hopefully help you remedy around here!