Just wondering if you can help with the following, i'm trying to resolve a couple of 302 errors on the server and have been told that it may be a DNS issue, and after checking with nslookup on the server i get the following:

nslookup paypal.com ns1.theplanet.com
Server: ns1.theplanet.com
Address: 216.234.234.30

Non-authoritative answer:
Name: paypal.com
Addresses: 216.113.188.64, 216.113.188.34

nslookup paypal.com ns1.theplanet.com
Server: ns1.theplanet.com
Address: 216.234.234.30

Non-authoritative answer:
Name: paypal.com.<mydomainname>.com
Address: <myserverip>

As you can see it randomly pulls the correct IP for the request, and also pulls the incorrect IP (this servers IP) - to me there is no real pattern and i'm basically a complete novice and only know the most basic information when it comes to DNS.

I'm pretty sure that that is not right, and if a nslookup is done using either theplanets nameservers or my servers dns i always get the right result, but if i run nslookup on the server, i (most of the time) resolve to my own ip? - thats not right is it, lol

I was just wondering if there is a quick resolve to this?

Can't see anything if you don't tell us what the domain is - all I see is you doing a lookup on paypal.com.

If you are doing this on your server, it may be appending your default domain to the lookup (which explains paypal.com.yourdomain.com). You should do a lookup with a trailing period, eg:

nslookup
> server ns1.theplanet.com
> paypal.com.

or

> yourdomain.com.

which ensures that nslookup doesn't append common TLDs on a failed lookup.