At 2/14/01 5:00 PM, [EMAIL PROTECTED] wrote:

> Has anyone else had experiences like this where a domain just goes dead for
>no reason then comes back when it feels like with no changes on your end?

Your DNS servers aren't working:

$ dig 1295netnames.com NS @a.root-servers.net

; <<>> DiG 8.3 <<>> 1295netnames.com NS @a.root-servers.net 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 6
;; flags: qr rd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;;      1295netnames.com, type = NS, class = IN

;; ANSWER SECTION:
1295netnames.com.       2D IN NS        NS1.1295netnames.com.
1295netnames.com.       2D IN NS        NS2.1295netnames.com.

;; ADDITIONAL SECTION:
NS1.1295netnames.com.   2D IN A         216.87.159.197
NS2.1295netnames.com.   2D IN A         216.87.159.198


This tells us that the root servers know about your domain (although the 
two name servers are suspiciously close to each other in address -- we'll 
get to that in a minute). It's not an OpenSRS problem.

Next we try to contact your DNS servers:

$ dig 1295netnames.com NS @ns1.1295netnames.com

; <<>> DiG 8.3 <<>> 1295netnames.com NS @ns1.1295netnames.com 
; (1 server found)
;; res options: init recurs defnam dnsrch
;; res_nsend to server ns1.1295netnames.com  216.87.159.197: Connection 
timed out


The nameserver software at "ns1.1295netnames.com" is not responding. 
Further testing reveals that the same is true of "ns2.1295netnames.com", 
although both of them are reachable by traceroute (so it's not a routing 
or network problem).

So the problem is with your copy of BIND, or whatever DNS server software 
you're running on "ns1.1295names.com" and "ns2.1295names.com". It's 
probably crashed. (Or maybe your firewall is blocking packets to port 53 
or something.)

I'm guessing that even though you have two IP addresses for your name 
servers, they're attached to one machine running one copy of the 
software. That's a horrible idea, for exactly this reason. If that one 
piece of software crashes, both of your name servers (there's really only 
one) stop working.

The whole point of separate name servers is that if one stops working, 
the other doesn't. At the very least they should be running on separate 
computers and separate networks. Ideally they'd be on separate continents 
and the boxes would be running different software.

But start by moving your ns2 somewhere else; many companies will host 
offsite DNS records for you. Contact me offlist for more info if you need 
it.

--
Robert L Mathews, Tiger Technologies

Reply via email to