Framed web forwarding

[ricob]

[Apparently this failed last time, so trying again...]

Never had to deal with this b4, so i'm a bit in the dark. Friend of a friend has got me a domain name, and I want to point it to some random web space maintaining the domain name (not the web space address) in the address bar.

I thought this was simple - handled server-side using framed web forwarding, with just a tick of a box on the server settings for that domain name. However, he's asking me for the primary and secondary name servers for the web space, or the dns servers, a-record and mx-record details. What's this about? I want to use some ntl webspace for the mo, and don't have these details.

I start to get hazy here, so if anyone can point me to a good reference on the net I'm happy to learn. I googled but couldn't find anything to explain how it works which wasn't trying to sell me forwarding or domain registration.

Cheers,
Rich.

[Stoo]

he's setting it up as a full domain by the sound of it, tell him you just want web-forwarding..

[ricob]

What's the difference? Is it possible/worth setting it up as a full domain? What advantages does it offer?

Cheers.

[Stoo]

well, forwarding is useful if you just have a cheapo webhost that doesn't support domains, and you can move them a lot quicker, but if your webspace is semi permanent then the full domain solution is much neater.

Have a look on the NTL support pages and see if they allow you to use your own domain on their webspace (quite a few do these days)

[BlueMagician]

...he's asking me for the primary and secondary name servers for the web space, or the dns servers, a-record and mx-record details...

Domain name MX records must point to a valid IP address of a server capable of processing all services associated with that domain name.
If whoever bought the domain name didn't also pay for email/web hosting, then the registrar need to know where you would like everything to do with the domain name to be pointed at, not just port 80 (web) requests.

S.