nanog mailing list archives
Re: domainmonger.com with wildcard NS?
From: "Robert E. Seastrom" <rs () seastrom com>
Date: 14 Oct 2003 14:22:26 -0400
just me <matt () snark net> writes:
On 14 Oct 2003, Robert E. Seastrom wrote: just me <matt () snark net> writes: > In theory this doesnt break anything, since the nameservers in > question aren't providing recursive service to anyone. Any questions > they see are the result of a followed delegation. So I don't see why > this would cause problems anywhere. I'd sure hate to be the poor fellow having a zone being served from those nameservers when the inevitable configuration error causes the zone to get dropped on the floor (for instance an accidental removal from named.conf). NXDOMAIN or SERVFAIL sure beats a wildcard match going to the wrong place. I think (don't hold me to this, I might be wrong) the trick, when you're a registrar, is to not lose domains?
History demonstrates that registrars are human too. ---Rob
Current thread:
- domainmonger.com with wildcard NS? Rick Ernst (Oct 14)
- Re: domainmonger.com with wildcard NS? just me (Oct 14)
- Re: domainmonger.com with wildcard NS? Robert E. Seastrom (Oct 14)
- Re: domainmonger.com with wildcard NS? just me (Oct 14)
- Re: domainmonger.com with wildcard NS? Robert E. Seastrom (Oct 14)
- Re: domainmonger.com with wildcard NS? Robert E. Seastrom (Oct 14)
- Re: domainmonger.com with wildcard NS? just me (Oct 14)
- <Possible follow-ups>
- RE: domainmonger.com with wildcard NS? Mike Damm (Oct 14)