|
The
SOA doesn't have to exist in the domain in question. Put another way, the SOA
for domain.com doesn't have to be soa.domain.com, it could be
soa.someotherdomain.com
For
instance, look at my company's primary domain (inovis.com) -
bash-2.04$ dig in soa inovis.com
;
<<>> DiG 9.1.2 <<>> in soa inovis.com
;; global options: printcmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39141 ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0 ;;
QUESTION
SECTION:
;inovis.com. IN SOA ;;
ANSWER
SECTION:
inovis.com. 1800 IN SOA ns1.inovisinc.net. hostmaster.inovisinc.net. 2003121401 1800 600 604800 1800 The
SOA record for inovis.com lives in inovisinc.net. Therefore, it doesn't
necessarily make sense for the SOA to automatically populate with the suffix of
the domain in which it exists.
Roger
--------------------------------------------------------------
Roger D. Seielstad - MTS MCSE MS-MVP Sr. Systems Administrator Inovis Inc.
|
Title: Message
- [ActiveDir] DNS SOA entered incorrectly during installatio... Rich Milburn
- RE: [ActiveDir] DNS SOA entered incorrectly during in... deji Agba
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Roger Seielstad
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Roger Seielstad
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Rich Milburn
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Rich Milburn
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Roger Seielstad
- RE: [ActiveDir] DNS SOA entered incorrectly during in... Roger Seielstad
