Correct me if i'm wrong but did you not have the nameservers pointing to the ukwebsolutions servers and it didn't make a difference?
If you changed the name servers then uk2.net should have
no involvement in your DNS anymore.
To put it as simply as I can, to resolve this you should:
1) Point the nameservers to whoever you want to manage your DNS - i.e when someone types
www.yourdomain.com you want to be in control of what IP address is returned.
2) Configure the server the domain is pointed to so that when the site is visited it gets displayed, this should obviously be a web server and the server should handle the rest. For example you point the
www.yourdomain.com record to the IP address of the ukwebsolutions webserver.
I will give you an example.
so I go and register a domain name through uk2.net, let's say I register
www.eulogy.co.uk for arguments sake.
I then purchase some webspace with another provider, again for arguments sake let's say this is 34sp.com.
34sp.com say to me "if you want to use our webspace change your domain name servers to point to":
ns1.34sp.com
ns1.34sp.com
So off I go to uk2.net and get the name servers changed.
Now all DNS resolution is taken care of by 34sp.com's name servers rather than uk2.net.
UK2.net should no longer have a say in what addresses are returned when someone tries to email to you on that domain or type www.eulogy.com into their browser.
34sp.com make sure that the DNS records they have for your domain are correct, they would need to setup a WWW record for
www.eulogy.com and point it to the IP address of their webservers.
They then configure their webservers so that when access requests are made over the internet on TCP port 80 your site is loaded.
All is well.
You can remove any 302/301 redirects you have setup in your homepage code.