On Wed, May 6, 2009 at 11:23 AM, Sean Martin <[email protected]> wrote: > The lack of an SOA shouldn't prevent name resolution from > occurring, should it?
It depends. Zones must have NS and SOA records to be compliant with the standards. There are valid technical reasons why a resolver might request or expect them. The NS records in particular -- technically, out-of-zone NS records at the GTLD servers are a referral, so resolvers are likely to expect to get authoritative NS records from the delegate nameserver. When it doesn't get them, it could consider that a lame delegation, decide there aren't any valid nameservers, and fail the query. To borrow a phrase, in this situation, DNS may make demons fly out of your nose. Fix what you already know is broken before you go looking for other causes. :) If your vendor is telling you that they don't need to serve an SOA record, tell them their stuff is broken and you want to return it and you'll be going to a competitor's whose stuff isn't broken. > I'm trying to nail down why, after setting up conditional forwarding for the > domain akusatitle.net (or www.akusatitle.net), we are unable to access > the website from anywhere outside of our network. "unable to access the website" is a vague problem description. Computers thrive on precision. :) Using the PING.EXE that comes with Windows, or the one on my Linux box at home, I can't resolve <akusatitle.net> to an IP address. So it's not a website problem at all, it's a problem with DNS resolution. Which leads us back to the first problem. -- Ben ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
