Secondary DNS question...
frnkblk at iname.com
Sun Jun 23 01:55:59 UTC 2013
stariononline.com has two NSes listed, ns1.starionhost.net [184.108.40.206]
and ns2.starionhost.net [220.127.116.11]. But the first one does not seem
to want to respond (http://goo.gl/s41wN and http://dnscheck.iis.se/ and
http://www.zonecut.net/dns/index.cgi are just a few examples) to a few of
the online checkers. I checked with some others and it looks like you have
no SOA set for for ns1.starionhost.net:
C:\>dig SOA starionline.com @ns1.starionhost.net
; <<>> DiG 9.8.0-P1 <<>> SOA starionline.com @ns1.starionhost.net
;; global options: +cmd
;; connection timed out; no servers could be reached
Though the second one has one:
C:\>dig SOA starionline.com @ns2.starionhost.net
; <<>> DiG 9.8.0-P1 <<>> SOA starionline.com @ns2.starionhost.net
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 7010
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available
;; QUESTION SECTION:
;starionline.com. IN SOA
;; ANSWER SECTION:
starionline.com. 86400 IN SOA ns1.starionhost.net.
info.starionhost.net. 2008 3600
;; AUTHORITY SECTION:
starionline.com. 86400 IN NS ns1.starionhost.net.
starionline.com. 86400 IN NS ns2.starionhost.net.
;; ADDITIONAL SECTION:
ns1.starionhost.net. 86400 IN A 18.104.22.168
ns2.starionhost.net. 86400 IN A 22.214.171.124
;; Query time: 74 msec
;; SERVER: 126.96.36.199#53(188.8.131.52)
;; WHEN: Sat Jun 22 20:51:12 2013
;; MSG SIZE rcvd: 157
And confirmed here:
From: bind-users-bounces+frnkblk=iname.com at lists.isc.org
[mailto:bind-users-bounces+frnkblk=iname.com at lists.isc.org] On Behalf Of SH
Sent: Thursday, June 20, 2013 10:03 PM
To: bind-users at lists.isc.org
Subject: Secondary DNS question...
Our secondary DNS machine went down (and unnoticed for 24 hours).
Today, we had multiple people calling about email that hadn't come in, and
trouble with outgoing emails not going out.
Our primary DNS was up the whole time. So my question is, why would my
secondary being down, and only my primary being up cause so many problems?
I thought the whole idea behind having two DNS servers on different networks
was to never have a failure like this.
My understanding was that when DNS is queried, the one that responds fastest
is the information that is used. If the secondary is down, then the primary
would by default always be fastest (and only).
I think I reasonably understand basic DNS and the setup, but this has me
thinking that something isn't set up right.
Can anyone shed any light on what might have happened here? Could my
primary not be responding as it should? All the tests I have run on it show
that it is responding normally.
Please visit https://lists.isc.org/mailman/listinfo/bind-users to
unsubscribe from this list
bind-users mailing list
bind-users at lists.isc.org
More information about the bind-users