The lack of an SOA is another issue we're dealing with. It has to do with an apparent limitation of the appliance we're using to host the (A) records for these domains. The lack of an SOA shouldn't prevent name resolution from occurring, should it? 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.
- Sean On Wed, May 6, 2009 at 4:10 AM, Ben Scott <[email protected]> wrote: > On Tue, May 5, 2009 at 6:18 PM, Sean Martin <[email protected]> > wrote: > > So I setup the conditional forwarding for the domain "akusatitle.net" a > few > > hours ago. Performing NSLookup from external sources returns a response > of > > "Server Failed". > > For the <akusatitle.net.> domain, in the public DNS, the delegated > nameservers are not configured properly. They're not returning SOA or > NS records for the zone. (They are returning A records.) > > $ dig +noall +ans akusatitle.net. NS @a.gtld-servers.net. > akusatitle.net. 172800 IN NS ns1.alaskausa.org. > akusatitle.net. 172800 IN NS ns2.alaskausa.org. > $ dig +noall +ans akusatitle.net. ANY @ns1.alaskausa.org. > akusatitle.net. 15 IN A 208.69.197.102 > $ dig +noall +ans akusatitle.net. ANY @ns2.alaskausa.org. > akusatitle.net. 20 IN A 208.69.197.102 > $ > > -- Ben > > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ > ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ > ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~
