7 Apr
2015
7 Apr
'15
1:33 p.m.
Hi,
Assume that:
1) You're a user of BitFolk's secondary DNS service.
2) One or more of your zones have been unreachable from our
secondary servers for so long that they have expired.
How long would you expect BitFolk to continue serving SERVFAIL for
your zone(s) before removing them from the configuration (and
thereafter serving NOERROR/REFUSED as for any name they're not
authoritative for)?
If any of you use other similar services where you provide the
primary DNS server, what do they do in that circumstance?
Is there a difference in behaviour in typical Internet protocols
that encounter SERVFAIL vs NOERROR? e.g. would a mail server
consider SERVFAIL to be a temporary failure but NOERROR to be a
permanent one?
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
7 Apr
7 Apr
1:42 p.m.
Hi,
Assume that:
1) You're a user of BitFolk's secondary DNS service.
2) One or more of your zones have been unreachable from our
secondary servers for so long that they have expired.
How long would you expect BitFolk to continue serving SERVFAIL for
your zone(s) before removing them from the configuration (and
thereafter serving NOERROR/REFUSED as for any name they're not
authoritative for)?
If this happens would the owner automatically get a ticket?
Can you tell from whois or elsewhere whether you're still listed as an
auth server?
If any of you use other similar services where you
provide the
primary DNS server, what do they do in that circumstance?
Is there a difference in behaviour in typical Internet protocols
that encounter SERVFAIL vs NOERROR? e.g. would a mail server
consider SERVFAIL to be a temporary failure but NOERROR to be a
permanent one?
These are things I don't know and haven't really thought much about. :-(
It'd be an interesting thing to know tho'...
Regards,
@ndy
--
andyjpb(a)ashurst.eu.org
http://www.ashurst.eu.org/
0290 DA75 E982 7D99 A51F E46A 387A 7695 7EBA 75FF
2:27 p.m.
Hi Andy,
On Tue, Apr 07, 2015 at 02:42:10PM +0100, Andy Bennett wrote:
No, but Nagios would send email alerts.
If it's just the time since last refresh of the zone:
- Starts sending WARNING alert when 1.5x refresh time is
reached.
- Start sending CRITICAL alert when 0.5x expire time is reached.
- Sends these every 6 hours.
If it's a more serious problem like DNS server can't be reached at
all then the above won't happen. Instead:
- Starts sending CRITICAL alerts about DNS server being broken.
- Sends these every 4 hours.
If the entire host appears down then the above won't happen.
Instead:
- Starts sending CRITICAL alerts about host being down.
- Sends these every hour.
So you'd clearly have to ignore or not receive a large quantity of
email alerts.
How long would
you expect BitFolk to continue serving SERVFAIL for
your zone(s) before removing them from the configuration (and
thereafter serving NOERROR/REFUSED as for any name they're not
authoritative for)?
If this happens would the owner automatically get a ticket? Can you tell from whois or elsewhere whether
you're still listed as an
auth server?
Good point which I should have mentioned. When zones break I check
if they are still delegated to BitFolk and if they aren't then I
just disable them. So yes, the zones are still delegated to
BitFolk.
Cheers,
Andy
--
http://bitfolk.com/ -- No-nonsense VPS hosting
3300
days inactive
3300
days old
2 comments
2 participants
participants (2)
-
Andy Bennett -
Andy Smith