Question : Cant setup Child Domain, DNS Issue

I've been having issues in work so i have setup a vmware setup at home so i can finally nail down what im doing wrong without any risk. In work im having issues with replication between Parent and Child domains. So at home im trying to set up a 2 domain network. 1 Parent and 1 child as per Figure 1. In another question it was recomended that i following this link http://www.petri.co.il/how_to_install_active_directory_on_windows_2003.htm which is an example of how to setup the 1st domain in a forest and that has gone well. I havn't found a particually good guide for setting up the first child domain so i used the following http://support.microsoft.com/kb/255248 . The guide tells me to set up a delegation on the parent which goes fine, i then set the tcp/ip settings on the child to use a static ip (192.168.2.10) and point to the parent for the perferred dns (192.168.1.10) Everything goes well until i get to Promoting the child DC. I use DCPROMO and i get the following error shown in Figure 2. I havn't progressed past this point but have taken 2 more screenshots of the current state of the dns to try and help. Figure 3 shown the parent dns. As you can see there is a record in the delegated zone, on the other hand figure 4 shows the child dns which has got itself in a bit of a mess because i couldnt complete the DCPROMO. Could someone please take the help to help me understand what im doing wrong. Im already really grateful to everyone who's helped me so far.

Answer : Cant setup Child Domain, DNS Issue

So, far you have only DNS zone in your parent domain. What debuggerau was asking is that your zone configuration from  in your parent domain is allow secure dynamic or dynamic. When you set up the child domain, it will create it's own DNS zone for that domain. It will not integrated or automatically replicated as they are separate DNS zone in two separate AD database.

For your error message, it is a very common one and all refers to DNS. The most probably cause is that some name resolution is not properly done. What I usually do is always making sure the DC in the parent domain as well as the server(to be DC) can resolve name and IP of each other from both boxes.
Also, see if you have missing anything here: http://technet.microsoft.com/en-us/library/cc778452.aspx