Another Lame NameServer Question

[Jeff Reasoner]

There's nothing lame per se about these servers. The problem is probably
ns2 itself. It's not authoritative for ssainc.com (possibly other
domains as well) It doesn't appear to have a zone loaded. (Didn't
actually need the +norec here ;-)

[jeff at zephyr jeff]$ dig +norec soa ssainc.com @ns2.ssainc.com
 
; <<>> DiG 9.3.2 <<>> +norec soa ssainc.com @ns2.ssainc.com
; (1 server found)
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 9190
;; flags: qr; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0
 
;; QUESTION SECTION:
;ssainc.com.                    IN      SOA
 
;; Query time: 162 msec
;; SERVER: 70.150.152.34#53(70.150.152.34)
;; WHEN: Mon Mar 20 17:14:18 2006
;; MSG SIZE  rcvd: 28

Pure speculation here, but my guess is that this is due to the fact that
you're running your public nameservers behind a NAT and NOTIFY is not
working. I'd suggest searching the archives of this list to fix that.
To get some lookup consistency in the interrim, you could take ns2
offline.

On Mon, 2006-03-20 at 12:44, Kenny Houston wrote:
> I like some have actually read and read to the point I'm comfused.
> Could someone please help me resolve my Lame Name server.  I'm not sure
> exactly what you need, but here is a start.
> 
> Domain name:   ssainc.com
> ns1                  ns1.ssainc.com - (Public) 70.150.152.33 -
> (Private) 172.16.1.223
> ns2                  ns2.ssainc.com - (Public) 70.150.152.34 -
> (Private) 172.16.1.224
> 
> 
> Thanks
> 
> Kenny
> 
>