And most of the domains never have working name servers at all. The
internic rules say you're supposed to have name service first. This
isn't always practical, but if speculative domains don't have DNS within
a few days, I'd think that'd be enough to wipe the allocations.
So many people keep harping on the point of having name servers first.
But that's a silly and moot point. The name servers may well be behind
a firewall and the use of the domain name is intended for internal use
and needs to be registered externally for the same reason one should use
allocated address space from ARIN instead of picking random addresses.
This is like telling people they have to be routed on the Internet to be
able to get an address allocation.
Actually, at this point I'd be happy to supply a credit card or a funded
InterNIC account number along with applications. Money up front may well
be the only way to clobber speculators.
This is a more reasonable way to begin to block those speculators that
are ripping off the system. There are a number of variations I am sure
InterNIC could do. Among them would be to expedite new domain requests
if the credit card payment, or established account authenticity, has
been included with the request. Other ideas include limiting the number
of outstanding requests per contact. If you have more than N unpaid
domains, you can't regiater any more on that contact until you either
pay up on some or delete some.
Another idea I have for InterNIC would be that when a domain is released
for non-payment, put it on "lockout" (just seeking a new term here) for
a random period of time. If during the lockout period, a new request
for it comes in, reject the request and extend the lockout for a new
random amount of time.
> And most of the domains never have working name servers at all. The
> internic rules say you're supposed to have name service first. This
> isn't always practical, but if speculative domains don't have DNS within
> a few days, I'd think that'd be enough to wipe the allocations.
So many people keep harping on the point of having name servers first.
But that's a silly and moot point. The name servers may well be behind
a firewall and the use of the domain name is intended for internal use
and needs to be registered externally for the same reason one should use
allocated address space from ARIN instead of picking random addresses.
If you are behind a firewall, you can use RFC 1918 addresses. You don't
need addresses from ARIN, and you don't need to pick at random.
Relaxing the requirements for name servers seems like an excellent way
of making the DNS even more broken than it already is. A number of TLDs
(.no being one of them) will *enforce* a minimum of two functioning name
servers for each domain. If you don't like this, you can of course take
your business elsewhere.
This is like telling people they have to be routed on the Internet to be
able to get an address allocation.
Sure. Why should they be allocated global addresses when RFC 1918 is
available?
I really can't understand why there'd be a problem with a pay-first policy.
If a registration is accompanied by CC#, check, etc., it's registered. If
two registrants want the same domain: first paid, first served.
Third party registrars (ISPs, other registries) could execute a "statement
of purpose"-type document with NSI that would allow them to register
without paying first. That privilege could be revoked if it's abused.
The typical spammer and/or speculator isn't going to sink his/her/it's
money into a throwaway domain name, and legit third-party registrants
aren't likely to deal with a speculator/abuser if their payment privilege
is at risk.
Simple, easy to put into effect, easy to police, solves most of these
problems without hurting service...all of which is, of course, why
InterNIC/NSI won't do it. At least, in the past they've avoided the simple
solution whenever possible...
Spammers should be investigated by Ken Starr!
Dean Robb
PC-EASY computer services
(757) 495-EASY [3279]
So many people keep harping on the point of having name servers first.
But that's a silly and moot point. The name servers may well be behind
a firewall and the use of the domain name is intended for internal use
and needs to be registered externally for the same reason one should use
allocated address space from ARIN instead of picking random addresses.
This is like telling people they have to be routed on the Internet to be
able to get an address allocation.
1) You should have domain servers for ANY domain you register that live in
NON-RFC1918 space. Otherwise, Why register the domain at all? If it's for
use behind the firewall, why not use internic.net or whitehouse.gov? You
say "Because they want to receive email at the domain!" Well, to receive
email, the rest of the world has to be able to find the mx records and to
do that, your domain servers have to live in NON-RFC space and we have now
completely and totally blown your first point out of the water and made it,
in your own words, "moot."
2) DNS servers that are behind a firewall are useless in the context you
describe above.
3) You should NEVER pick random addresses. Please refer to RFC1918.
4) If you don't intend to be routed on the global internet, you SHOULD be
required to use RFC1918 space. NOBODY should be allocate routable address
space for internal, off-net use.
been included with the request. Other ideas include limiting the number
of outstanding requests per contact. If you have more than N unpaid
domains, you can't regiater any more on that contact until you either
pay up on some or delete some.
This would be a moot effort. What is going to stop the speculators from
just generating random email addresses for admin, techincal and contact
addresses. It is very simple to route *@domain.com to a single email box.