[ga] Re: webhosting.pn completely broken (Was: the further evolution of...

["kidsearch" <kidsearch@xxxxxxxxxxxxx>]

Stephanie, I've never claimed to be a tech expert. Thats why I asked the
question. There is a lot I do know about that you do not. We each have our
own areas of expertise.

Your smartass remark tells me your social skills reazlly suck. I asked a
question. If you don't know the answer, try not answering it instead of
trying to tell everyone that you think you have a high IQ. We already know
by your remarks that is not the case.

Maybe you need to get out more, socialize. People might even learn to like
you if you get away from your computer long enough to find out. But with
that attitude it's highly doubtful.

As for getting off the list, did you think this was the IETF mailing list?
No. It's for individuals, including me, who wish to be on the list. So
before giving any advice, why don't you take a long look at yourself, that
is if you have kept mirrors in your home to do so, which in your case might
not be advisable.

Maybe you should get off the list until you learn some social and people
skills. You didn't even understand that it is not a hosting company I own.
Gosh and you wanted to be right so bad, too.

Chris McElroy

----- Original Message ----- 
From: "Stephane Bortzmeyer" <bortzmeyer@xxxxxx>
To: "kidsearch" <kidsearch@xxxxxxxxxxxxx>
Cc: <ga@xxxxxxxxxxxxxx>
Sent: Monday, April 10, 2006 2:57 AM
Subject: webhosting.pn completely broken (Was: the further evolution of...


> On Sun, Apr 09, 2006 at 06:05:38PM -0400,
>  kidsearch <kidsearch@xxxxxxxxxxxxx> wrote
>  a message of 80 lines which said:
>
> > I have a question. My new hosting company is webhosting.pn and the
> > nameservers are ns1.webhosting.pn and ns2.webhosting.pn
>
> BTW, they are ORN (Open Recursive Nameserver), which is very bad.
>
> Also, they do not know their own IP addresses:
>
> % dig @69.16.204.23 A ns2.webhosting.pn
>
> ; <<>> DiG 9.2.4 <<>> @69.16.204.23 A ns2.webhosting.pn
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 22398
> ;; flags: qr aa rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;ns2.webhosting.pn.             IN      A
>
> ;; AUTHORITY SECTION:
> webhosting.pn.          86400   IN      SOA     ns1.webhosting.pn.
webmaster.magicanswers.com. 2006040401 86400 7200 3600000 86400
>
> ;; Query time: 131 msec
> ;; SERVER: 69.16.204.23#53(69.16.204.23)
> ;; WHEN: Mon Apr 10 08:55:15 2006
> ;; MSG SIZE  rcvd: 101
>
> > Any insight as to what the problem is and why would be helpful. Are
> > ccTLDs like second class citizens?
>
> Or may be, as indicated by your many, many postings, you are not as
> knowledgeable as you think? If your customers read this mailing list,
> I would suggest that you spend a few months without posting and
> learning the DNS.