Reverse Lookup Question

[Kevin Darcy]

Gawie Marais wrote:

>i have two name servers on my network. forward requests work as well as 
>reverse lookup requests. i have been assigned part of a network class 
>from my service provider. however, when i register a new .co.za domain, 
>which is correctly setup on my systems, i get the following error 
>message back.
>
>maybe this means something to someone out there that could explain to me 
>what is happening here ::
>
>--------------
>error message follows here :: it's quite long, please bare with me here...
>
Why, I hardly even know you! Or, did you perhaps mean "bear" instead of 
"bare"....?

>>Primary Server  : ns1.asdn.co.za @ 196.25.223.132
>>Secondary 1     : ns2.asdn.co.za @ 196.25.223.133
>>There is no pre-existing SOA record for asdntest.co.za.
>>
>>CHECKING: Primary Server is ns1.asdn.co.za at 196.25.223.132
>>WARN: No PTR records?  - WARN: No A records?
>>
>>CHECKING: secondary 1 is ns2.asdn.co.za at 196.25.223.133
>>WARN: No PTR records?  - WARN: No A records?
>>!
>>! The message "No PTR records?" means that when your application was
>>! scanned, the program tried to convert the IP Number that you gave for
>>! you Nameserver (or Mail eXchange Server) into a "name" - but failed.
>>! This is usually because no one has set up any reverse domain
>>! information, ie the bit that converts numbers to names.  If this is
>>! not set up - then you may have trouble later on with security
>>! validation or when tring to use FTP to many sites - so its worth
>>! fixing...  If it has been set up - then it has NOT been successfully
>>! delegated to.  Ask your Internet Service Provider what this means.
>>! 
>>!
>>! The message "No A records?" means that when your application was
>>! scanned, the program tried to convert the "name" that you gave for
>>! you Nameserver (or Mail eXchange Server) into an "IP Number" - but
>>! failed.  This is usually because no one has registered the "domain"
>>! that the "name" is in.  This could well be because you are
>>! registering this "domain" right now - in which case you have no
>>! problem.  If it's not - you DO have a problem and should check it out.
>>! 
>>
>>Adding application
>>Checking quoted Nameservers....
>>
>>At "196.25.223.132" - Domain "asdntest.co.za." is configured 
>>(Ser No 901200304) with an origin of "ns1.asdn.co.za.asdntest.co.za." and
>>an e-mail contact of "dnsadmin\@asdn.co.za.asdntest.co.za."
>>The 2 NS Records are:- ns1.asdn.co.za., ns2.asdn.co.za..
>>
>>
>>At "196.25.223.133" - Domain "asdntest.co.za." is configured 
>>(Ser No 901200304) with an origin of "ns1.asdn.co.za.asdntest.co.za." and
>>an e-mail contact of "dnsadmin\@asdn.co.za.asdntest.co.za."
>>The 2 NS Records are:- ns1.asdn.co.za., ns2.asdn.co.za..
>>
>>ERROR: No valid nameservers found - rejecting request
>>!
>>! Something is perhaps terribly wrong.  Errors at this point are usually
>>! due to mismatching Nameservers between the infomation you supplied on
>>! the form and in your zone file.  Please try submitting again once
>>! you've done this.  The problem may well be that you have no reverse
>>! delegation set up for your primary Nameserver, ie your ISP has given
>>! you a partial class C address - and not set up a mapping of IP Number
>>! to Name conversion.
>>    
>>
It would appear that you forgot to dot-terminate the contents of the 
MNAME field ("origin") of your SOA record. While I can't be sure that 
this is the root cause of your problem, it's certainly not helping. Try 
dot-terminating the name and see if it works better.

                                                                        
                                        - Kevin