|
|
 |  |
Re: Panther, shared internet, and QDNSFrom: Men & Mice Support Date: Monday, December 29, 2003
Time: 12:41:13 pm>>>2) ERROR: One or more of the nameservers listed at the parent
>>>servers are not listed as NS records at your nameservers. The
>>>problem NS records are:
>>>ns2.one4allhosting.com.
>>
>>ns2.one4allhosting.com is the same IP as ns3.greenbuilder.com (or
>>should be... see above). The reason for the ns3 name is simply to
>>avoid confusing hosting clients.
>
>"zone data must match delegation data"
Yes, usually that's true. However, if you're careful, data mismatches
don't have to cause problems. In this case, I don't see a problem.
However, to avoid future problems, it may be best to simply remove
"ns2.one4allhosting.com" (the name, not the server) from the zone
registration. This way, the delegation records would look like this:
greenbuilder.com. 172800 IN NS ns1.greenbuilder.com.
greenbuilder.com. 172800 IN NS ns2.greenbuilder.com.
greenbuilder.com. 172800 IN NS ns3.greenbuilder.com.
ns1.greenbuilder.com. 172800 IN A 205.238.129.202
ns2.greenbuilder.com. 172800 IN A 205.238.129.194
ns3.greenbuilder.com. 172800 IN A 24.234.162.52
Of course, the zone's authority records should match this. They
currently don't:
greenbuilder.com. 86400 IN NS ns.greenbuilder.com.
greenbuilder.com. 86400 IN NS ns1.greenbuilder.com.
greenbuilder.com. 86400 IN NS ns2.greenbuilder.com.
greenbuilder.com. 86400 IN NS ns3.greenbuilder.com.
ns.greenbuilder.com. 86400 IN A 205.238.129.195
ns1.greenbuilder.com. 86400 IN A 205.238.129.202
ns2.greenbuilder.com. 86400 IN A 205.238.129.194
ns3.greenbuilder.com. 86400 IN A 24.234.162.52
The "ns" server isn't listed in the delegation. Not a serious
problem, but you (Bill) may want to address it at some point by
adding this server to the domain registration.
>and
>
>"SOA mname field must be in zone NS records"
No, not true at all. Think of the case of a hidden master server.
Besides, that's not the issue at hand.
>>If there is any actual problem with this practice (assuming the
>>host is properly defined, of course), please let me know.
>
>There are real and subtle problems, sooner or later, when your NS
>records do not meet the rules of thumb above.
Len, can you provide an example scenario that matches what Bill has
done? I mean, yes, I've seen some pretty subtle and annoying problems
caused by people ignoring these rules, but I've also seen things work
just fine without perfectly following the rules. In this case, I
can't see where any problem would arise from either of the two
conditions:
- A given server is mentioned twice, by different names, in the
delegation records. One of these names is not used in the authority
records.
- Another server is listed in the authority records but not the
delegation records.
____________________________________________________________________
Chris Buxton Men & Mice
Customer Support Specialist Making DNS Easy
|

Return to Digital Point Solutions' Home Page |