Verisign Screws The World

External Since: Apr 29, 2004 Posts: 1010

"McWebber" <mcwebber.TakeThisOut@my-deja.com> wrote in message
news:x0qdnTfkc-fi-fqiU-KYuQ@comcast.com...
> "Bill Logan" <who.TakeThisOut@what.com> wrote in message news:3f675358@clear.net.nz...
  > >
  > > "McWebber" <mcwebber.TakeThisOut@my-deja.com> wrote in message
  > > news:LtednRyID9LHY_uiXTWJlg@comcast.com...
   > > > "Bill Logan" <who.TakeThisOut@what.com> wrote in message
> news:3f66a942@clear.net.nz...
   > > > >
   > > > > Verisign for all their evil do not control the dns.
   > > >
   > > > Yes, they control the root servers.
  > >
  > > Sionce when?
  > > They 'own' the .com and .net domains and control the dns for them but
the
  > > root servers???? Get on the planet and learn how dns works
>
> I never said they own the root servers.
You said they control them - well can you explain how they control the two
in Europe?

>
   > > > > As far as your mail is concerned, reject of non existance domains
will
   > > > still
   > > > > apply as they are a dns lookup function and that is not effected!
   > > >
   > > > Yes it is. The domain appears to exist because Verislime has an A
record
  > > for
   > > > every domain. The default action by RFC is when there is no MX to try
> the
  > > A
   > > > record, so now every domain appears to be valid.
   > > >
  > > Well now that is funny - when my bind queries the existance of a non
  > > Registered name I receive a name does not exist. - Perhaps your bind is
> not
  > > configured right? You do use bind, I assume??
>
> I'm looking up directly on the various root servers. Perhaps you're not
> querying the root servers and are running your own root server.
The root servers do not have the domain zone records! The root servers list
the NS for domains and are said to be authoritive for the NS
To get the correct info for any domain you need to query the NS that is
authoritive for the domain.
In the case of a domain, (.com and .net only), that is not registered you
will find that because of the wildcard A record for .com and .net as
inserted by Verisign, as is their right being the 'owners of record of .com
and .net, the Verisign NS is the authoritive ones.
When you do a NS lookup on their NS you will find there is no zone record
apart from the wildcard A record pointing to their IP# A complete query of
their NS will show the name is not registered. I.E. it does not exist - even
though there is a wildcard A record.

External Since: Apr 29, 2004 Posts: 1010

"McWebber" <mcwebber.TakeThisOut@my-deja.com> wrote in message
news:JDSdnTapltWA-PqiU-KYvg@comcast.com...
> "Bill Logan" <who.TakeThisOut@what.com> wrote in message news:3f6755e1@clear.net.nz...
   > > >
  > > B/S - you can, and a growing number of people do, by pass - not use -
the
  > > ISP's dns, which by default probably uses the root server network of dns
>
> Tell you what, you query a - m.gtld-servers.net for a domain that doesn't
> exist and see what they respond.
Trying Lookup for ymeccaa.net

DNS Query for = ymeccaa.net
Server Name = m.gtld-servers.net
Connection established.

Query results for ymeccaa.net:
Host Addresses
-------------------------

RR Type: A
RR Class: IN
TTL: 900
RDATA Octets: 4
RR lists an IP of [64.94.110.11]

Query results for ymeccaa.net:
Mail Routing Information
-------------------------

No answer for ymeccaa.net

Query results for ymeccaa.net:
Authoritative Servers
-------------------------

No answer for ymeccaa.net

Query results for ymeccaa.net:
Canonical Name of an Alias
-------------------------

No answer for ymeccaa.net

Query results for ymeccaa.net:
Start of Authority Zone
-------------------------

No answer for ymeccaa.net

As you can see, No answer - the name does not exist - there is no
authoritive name server

If your ISP's dns sends your browser to the IP# listed it is because your
ISP does not have their dns bind set up correctly!
If they did, it would identify that the name does not exist and return a
page not found!

Also, note the long ttl above - if you reduce the ttl in your own setup for
dns requests you wont get the IP returned and will end up with a page not
found!

>
  > >
  > > Anyone can use the available alternatives such as the alternate, (non
> ICANN)
  > > root servers. Such as installing bind on your own local machine and
  > > configuring it the way YOU want. etc, etc, etc.
>
> Yeah, and when you can convince the world to stop clicking on links in
spam
> that problem will be solved as well.
>
I dont understand what you are saying here, what has using alternative root
servers and dns got to do with clicking on spam links?