> if I needed to be able to controll each office on site with local nameing ?
> running a dns at each site with each site managing its own dns ? but all
> under the one domain just broken up ? but looking back at the one site for
> any offsite connections ?
Then you do need subdomains.
> eg
>
>
> wstation1.office1.mydoman.com
> wstation2.office1.mydoman.com
> wstation3.office1.mydoman.com
> mail.office1.mydoman.com
>
> wstation1.office3.mydoman.com
> wstation2.office3.mydoman.com
> wstation3.office3.mydoman.com
> mail.office3.mydoman.com
>
> wstation1.mydoman.com
> wstation2.mydoman.com
> wstation3.mydoman.com
> mail.mydoman.com
In the named.conf on office2's DNS server, you would need
zone "mydomain.com" {
type master;
file "mydomain";
};
zone "office1.mydomain.com" {
type slave;
file "office1";
masters { 1.1.1.99; };
};
zone "office3.mydomain.com" {
type slave;
file "office3";
masters { 3.3.3.99; };
};
In the `mydomain' zone file, you would need something like:
@ IN SOA ns.mydomain.com. root.mydomain.com. (
1998091201 ; serial
10800 ; refresh
3600 ; retry
864000 ; expire
86400 ; minimum
)
IN NS ns.mydomain.com.
IN NS ns.office1.mydomain.com.
IN NS ns.office3.mydomain.com.
IN MX 0 mail.mydomain.com.
office1 IN NS ns.office1.mydomain.com.
IN NS ns.office3.mydomain.com.
IN NS ns.mydomain.com.
office3 IN NS ns.office3.mydomain.com.
IN NS ns.office1.mydomain.com.
IN NS ns.mydomain.com.
ns IN A 2.2.2.99
ns.office1 IN A 1.1.1.99
ns.office3 IN A 3.3.3.99
wstation1 IN A 2.2.2.1
wstation2 IN A 2.2.2.2
wstation3 IN A 2.2.2.3
mail IN A 2.2.2.10
In the named.conf on office1's DNS server, you would need
zone "mydomain.com" {
type slave;
file "mydomain";
masters { 2.2.2.99; };
};
zone "office1.mydomain.com" {
type master;
file "office1";
};
zone "office3.mydomain.com" {
type slave;
file "office3";
masters { 3.3.3.99; 2.2.2.99; };
};
In the `office1' zone file, you would need
@ IN SOA ns.office1.mydomain.com. root.mydomain.com. (
1998091201 ; serial
10800 ; refresh
3600 ; retry
864000 ; expire
86400 ; minimum
)
IN NS ns.office1.mydomain.com.
IN NS ns.office3.mydomain.com.
IN NS ns.mydomain.com.
IN MX 0 mail.office1.mydomain.com.
ns IN A 1.1.1.99
wstation1 IN A 1.1.1.1
wstation2 IN A 1.1.1.2
wstation3 IN A 1.1.1.3
mail IN A 1.1.1.10
Similarly for office3.
Then, each office's DNS server is authoritative for its part of the
domain, and acts as a slave for the other two servers.
-- Glynn Clements <glynn@sensei.co.uk> - To unsubscribe from this list: send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.rutgers.edu