18.07.2013 Views

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

Sidewinder G2 6.1.2 Administration Guide - Glossary of Technical ...

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 11: DNS (Domain Name System)<br />

About mail exchanger records<br />

About mail<br />

exchanger<br />

records<br />

314<br />

Listed below are some additional points about running DNS on your<br />

<strong>Sidewinder</strong> <strong>G2</strong>:<br />

• <strong>Sidewinder</strong> <strong>G2</strong> uses Berkeley Internet Name Domain (BIND 9).<br />

• The boot files for the unbound and the Internet name servers are<br />

/etc/named.conf.u and /etc/named.conf.i, respectively. The boot files<br />

specify corresponding directories: /etc/namedb.u and<br />

/etc/namedb.i. When you boot your <strong>Sidewinder</strong> <strong>G2</strong>, the name server<br />

daemon (named) is started. The /etc/named.conf.u and<br />

/etc/named.conf.i files specify whether the <strong>Sidewinder</strong> <strong>G2</strong> is a master or a<br />

slave name server and list the names <strong>of</strong> the files that contain the DNS<br />

database records.<br />

• If you choose to configure the <strong>Sidewinder</strong> <strong>G2</strong> as a master name server on<br />

either the unbound (internal) or Internet (external) side, you can modify the<br />

/etc/namedb.u/domain-name.db and /etc/namedb.i/domain-name.db files<br />

(where domain-name = your site’s domain name). You can add the default<br />

information that is being advertised for these zones.<br />

• The <strong>Sidewinder</strong> <strong>G2</strong> contains a non-blocking DNS resolver to support<br />

reverse IP address look-ups in the active proxy rule group, and name-toaddress<br />

look-ups in the http proxy. The relevant resolver library calls are<br />

gethostbyname() and gethostbyaddr(). The non-blocking DNS resolver<br />

provides a small number <strong>of</strong> DNS resolver daemons (nbresd) that are<br />

handed queries to resolve on behalf <strong>of</strong> the client.<br />

When you set up <strong>Sidewinder</strong> hosted DNS services for your site, you need to<br />

create mail exchanger (MX) records. MX records advertise that you are<br />

accepting mail for a specific domain(s). If you do not create an MX record for<br />

your domain, name servers and users on the Internet will not know how to<br />

send e-mail to you. When an e-mail message is sent from a site on the<br />

Internet, a DNS query is made in order to find the correct mail exchange (MX)<br />

host for the destination domain. The sender’s mail process then sends the email<br />

to the MX host. The <strong>Sidewinder</strong> <strong>G2</strong>, through the use <strong>of</strong> mailertables, will<br />

forward the mail to the internal mail process, which in turn will forward it to the<br />

internal mail host. See “Editing the mail configuration files” on page 354 for<br />

more information on mailertables.<br />

Consider the example shown in Figure 140. Someone in the Internet, Lloyd,<br />

wants to send one <strong>of</strong> your users, Sharon, an e-mail message, but all Lloyd<br />

knows is Sharon’s e-mail address: sharon@foo.com. The mailer at Lloyd’s site<br />

uses DNS to find the MX record <strong>of</strong> foo.com. Lloyd’s message for Sharon is<br />

then sent to the mailhost listed in the MX record for Sharon’s site.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!