Windows DNS server er BIND kompatibel, og det skal sættes sådan som bunk skriver. Du kan ikke bare skrive IP der. - Det bliver bøvlet at arbejde med. Istedet skal du sætte en MX record som foreslået sammen med en CNAME record OG en A record. Det er lettest at administrere på den måde i længden efter min mening.
Det du kan med din egen DNS server er at registrere domæner hos .dk toplevel DNS servere således at din DNS server bliver autoritativ for dit navneområde. Sagt på en anden måde - når en forsøger at komme i kontakt med
www.ditnavn.dk spørger den .dk DNS server, som refererer den videre til ditnavn.dk DNS server. Dermed er det din DNS server som leverer det endelige IP for
www.ditnavn.dk til den forespørgende klient. Et afgrænset navneområde kaldes for en Zone, og det er en zone du skal oprette på din DNS server. Denne zone er autoritativ for din lille del, eller partition, af den store distribuerede DNS database, og det er i teorien kun dig der kan ændre i den.
Nuvel, DNS er et stort område så hvis du skal have mere hjælp så spørg igen.
Her er et en lille bid af hvad Win2k server resource kit siger om det:
MX Resource Records
The mail exchange (MX) resource record specifies a mail exchange server for a DNS domain name. A mail exchange server is a host that will either process or forward mail for the DNS domain name. Processing the mail means either delivering it to the addressee or passing it to a different type of mail transport. Forwarding the mail means sending it to its final destination server, sending it using Simple Mail Transfer Protocol (SMTP) to another mail exchange server that is closer to the final destination, or queuing it for a specified amount of time.
Note
Only mail exchange servers use MX records.
If you want to use multiple mail exchange servers in one DNS domain, you can have multiple MX resource records for that domain. The following example shows MX resource records for the mail servers for the domain noam.reskit.com.:
*.noam.reskit.com. IN MX 0 mailserver1.noam.reskit.com.
*.noam.reskit.com. IN MX 10 mailserver2.noam.reskit.com.
*.noam.reskit.com. IN MX 10 mailserver3.noam.reskit.com.
The first three fields in this resource record are the standard owner, class, and type fields. The fourth field is the mail server priority, or preference value. The preference value specifies the preference given to the MX record among MX records. Lower priority records are preferred. Thus, when a mailer needs to send mail to a certain DNS domain, it first contacts a DNS server for that domain and retrieves all the MX records. It then contacts the mailer with the lowest preference value.
For example, suppose Jane Doe sends an e-mail message to JohnDoe@noam.reskit.com on a day that mailserver1 is down, but mailserver2 is working. Her mailer tries to deliver the message to mailserver1, because it has the lowest preference value, but it fails because mailserver1 is down. This time, Jane\'s mailer can choose either mailserver2 or mailserver3, because their preference values are equal. It successfully delivers the message to mailserver2.
To prevent mail loops, if the mailer is on a host that is listed as an MX for the destination host, the mailer can deliver only to an MX with a lower preference value than its own host.
CNAME Resource Records
The canonical name (CNAME) resource record creates an alias (synonymous name) for the specified FQDN. You can use CNAME records to hide the implementation details of your network from the clients that connect to it. For example, suppose you want to put an FTP server named ftp1.noam.reskit.com on your noam.reskit.com subdomain, but you know that in six months you will move it to a computer named ftp2.noam.reskit.com, and you do not want your users to have to know about the change. You can just create an alias called
ftp.noam.reskit.com that points to ftp1.noam.reskit.com, and then when you move your computer, you need only change the CNAME record to point to ftp2.noam.reskit.com. For example, the following CNAME resource record creates an alias for ftp1.noam.reskit.com:
ftp.noam.reskit.com. IN CNAME ftp1.noam.reskit.com.
Once a DNS client queries for the A resource record for
ftp.noam.reskit.com, the DNS server finds the CNAME resource record, resolves the query for the A resource record for ftp1.noam.reskit.com, and returns both the A and CNAME resource records to the client.
A Resource Records
The address (A) resource record maps an FQDN to an IP address, so the resolvers can request the corresponding IP address for an FQDN. For example, the following A resource record, located in the zone noam.reskit.com, maps the FQDN of the server to its IP address:
noamdc1 IN A 172.16.48.1