1,234
edits
Changes
Created page with "= PART 1: REVIEW OF LAST WEEK = == Record types == * Use dig to find the A, NS, MX, and TXT records for lin1.yoursenecaid.ops, senecacollege.ca , and google.ca == DNS Autho..."
= PART 1: REVIEW OF LAST WEEK =
== Record types ==
* Use dig to find the A, NS, MX, and TXT records for lin1.yoursenecaid.ops, senecacollege.ca , and google.ca
== DNS Authority ==
* Use nslookup to see whether you're getting authoritative responses for lin1.yoursenecaid.ops, senecacollege.ca , and google.ca
* For results that are not authoritative, use the 'server' command in nslookup to query the authoritative servers directly.
= PART 2: REVERSE DNS =
Here's a quick overview on [https://simpledns.com/kb/153/what-is-reverse-dns-and-do-i-need-it simpledns.com]. The important thing to understand is that the registrar for your domain can't do reverse DNS registration for you.
We'll set up reverse DNS in our Bind server for our three machines we have so far:
* Configure bind to do reverse lookups by adding this to its main configuration file:<source>
zone "210.168.192.in-addr.arpa" IN {
type master;
file "reverse-mydb-for-yoursenecaid-ops";
};
</source>
* Create reverse lookup zone data in /var/named/:<source>
$TTL 1D
@ IN SOA lin2.yoursenecaid.ops. hostmaster.yoursenecaid.ops. (
20140520; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
IN NS lin2.yoursenecaid.ops.
11 IN PTR lin1.yoursenecaid.ops.
</source>
Set this up for all your hosts and test it with the host command.
== Record types ==
* Use dig to find the A, NS, MX, and TXT records for lin1.yoursenecaid.ops, senecacollege.ca , and google.ca
== DNS Authority ==
* Use nslookup to see whether you're getting authoritative responses for lin1.yoursenecaid.ops, senecacollege.ca , and google.ca
* For results that are not authoritative, use the 'server' command in nslookup to query the authoritative servers directly.
= PART 2: REVERSE DNS =
Here's a quick overview on [https://simpledns.com/kb/153/what-is-reverse-dns-and-do-i-need-it simpledns.com]. The important thing to understand is that the registrar for your domain can't do reverse DNS registration for you.
We'll set up reverse DNS in our Bind server for our three machines we have so far:
* Configure bind to do reverse lookups by adding this to its main configuration file:<source>
zone "210.168.192.in-addr.arpa" IN {
type master;
file "reverse-mydb-for-yoursenecaid-ops";
};
</source>
* Create reverse lookup zone data in /var/named/:<source>
$TTL 1D
@ IN SOA lin2.yoursenecaid.ops. hostmaster.yoursenecaid.ops. (
20140520; serial
1D ; refresh
1H ; retry
1W ; expire
3H ) ; minimum
IN NS lin2.yoursenecaid.ops.
11 IN PTR lin1.yoursenecaid.ops.
</source>
Set this up for all your hosts and test it with the host command.
