I have always used my server as its own nameserver. I know this is frowned upon, but it has never caused me any problems.
There's nothing wrong with that.
The issue is if you are *only* using one server for the nameserver as it creates a single point of failure.
The most common strategy is to run the primary nameserver (ns1) on your main server with a secondary (ns2) somewhere else - anything from one of those free secondary dns services up to a small vps would take care of that - AXFR between the 2 to keep them in sync and you're all set.
I've had a dedicated server for the past 8 years or so. I have always used my server as its own nameserver. I know this is frowned upon, but it has never caused me any problems.
Anyway, I am about to move to a nice server and I think it's time to start using a different server as my nameserver.
Should I simply use my data centres nameserver (i.e. The Planet) or should I use a third party for my nameservers? If so, can you recommend any?
All advice greatly appreciated.
continue using your own.
Use your old server to do it.
ALWAYS at least use a slave nameserver on your single dedicated server.
Just one server and no need to ever go outside of it for a DNS.
By not having at a minnimum a slave on the server itself, your third party dns use can fail and your site is 'gone' or sent somewhere else by accident.
There is no reason in a single server set up to not use your own webserver as your own dns. If you have two servers, then I would use one for dns and mail and such...but still use the actual website server as a slave.