Full URL for images?

How should I access images located at a different machine?

[SoCal resident]

I was having bandwidth problems and the cheapes way around it according to my hosting company was to purchase a new account at next.mysite.com. I decided to put my images up there so now HTML file calls images as [next.mysite.com...]

A friend clamed that I was slowing down service to my users since their browser had to access the DNS for [next.mysite.com...] for all the images, of which there are many.

Is this true? If so, would exchanging [next.mysite.com...] for the IP address help? Is there a better solution?

I'll someday be going to a colocation server arrangement, but in the meantime?

[jtara]

A friend clamed that I was slowing down service to my users since their browser had to access the DNS for [next.mysite.com...] for all the images, of which there are many.

Not true.

There would be a DNS lookup for the FIRST occurence of next.mysite.com. After that, the address would be cached by your computer's DNS resolver.

[lammert]

Do you receive a lot of search engine referrals from your images?

In that case you may want to keep the images at your current server and not move them to a different domain. On some sites, image search can be the source of substantial incomming traffic and it would be sad to see that traffic affected just because you wanted to save a few dollars on more bandwidth with your current hosting account.

[eville84]

dns is also cached by isp's