granitecanyon help ... pls : )

[anton]

Hello ,

I just couldn't understand their examples, so I'm turning to you all for help : )

well , anyway , I have multiple domains, and all of them I want to point to my IP ... well , let's work with one domain for now ...


let's say I have domain abc.com , so I want everything , like *.abc.com and every port to point to my IP (already learned how to configure Virtual Host on linux :p ) ... so , what should I write in granitecanyon ?


ur help is greatly appreciated,
thanks.

[Craig McPherson]

Define the nameservers, like this:

domain.com. IN NS ns1.granitecanyon.com.
domain.com. IN NS ns2.granitecanyon.com.

Then point "domain.com." itself to your IP, like this:

domain.com. IN A 123.123.123.123

Then add any subdomain aliases you want:
www.domain.com. (http://www.domain.com.) IN CNAME domain.com.
mail.domain.com. IN CNAME domain.com.
ftp.domain.com. IN CNAME domain.com.

And an MX record, for e-mail:

domain.com. IN MX 10 domain.com.

also I want everything , like *.abc.com and every port to point to my IP

I have no idea if CNAMEs can take wildcards (never tried it, personally, so I have no idea if it works) so I don't know if you can do that, but you can define as many CNAMEs manually as you want.

If CNAMEs *do* take wildcards, then this would do what you're wanting to do:

*.domain.com. IN CNAME domain.com.

[anton]

thanks ;)

but I just got one question ...
what does this do ?
domain.com. IN MX 10 domain.com.
like what does it do for e-mail ?
(don't want to just type that in without understanding :) )

and now I'll have to wait, until my domain will have update dns settings : )

thanks.

[Craig McPherson]

Originally posted by anton:
<STRONG>what does this do ?
domain.com. IN MX 10 domain.com. like what does it do for e-mail ?</STRONG>

When a mail server has a piece of e-mail it needs to deliver to domain.com, it doesn't just look up domain.com's IP address and then make an SMTP connection to that IP. Imagine aol.com: with something like 30 million e-mail addresses in that domain, one single mailserver couldn't possibly stand up to the load.

Rather, when a mail server has a piece of e-mail to deliver to domain.com, it looks up the MX record for domain.com, which tells it what server it should actually connect to, to deliver mail to domain.com.

Multiple MX records allow multiple mail servers for a domain to be specified. If the one with the highest priority (the one with the lowest number in the MX record) can't be reached, it'll attempt delivery at the next one, and so on, and so on, until one works.

Even if you only have one mail server for your domain, you should still use an MX record for the domain -- most mail servers will fall back to doing a normal DNS lookup of your domain name if there's no MX record, but some might not.

[anton]

Craig :
thanks for explaining, now I got it : )