Todd,
You are so very right. One thing I have found. During my phase of
getting a .biz domain to be accepted as a nameserver, and moving our
domains away from Netsol (I may have well been the first .biz namserver)
Calling your agent helps. I've found the people at these smaller
resellers to be very helpful. It's also amazing how when they contact
Networks without Solutions things happen... fast too. So don't hesitate
to call and be polite.... works wonders.
Oh and about pachell... yep know what you mean. 2 years with pacbell
234 days down time (9 months free service too!) 9 months with ATT cable
in my new apt. TOTAL downtime 35 minutes. (other than the @Home fiasco)
....
James
On Fri, 28 Jun 2002 23:42:52 -0500
"J. Craig Woods" <[EMAIL PROTECTED]> said with temporary authority
> Todd Lyons wrote:
> >
> > I try to pick one at random. If I always pick a, and everybody who
> > does things like me always picks a, this could create artificial
> > load on a. I'm more or less trying to be "environmentally friendly"
>
> Hmmm, I like that kind of thinking. We need more like you out here.
>
> > Everything works as expected, EXCEPT the ns1.mrball.net entry. If I
> > manually query the register.com domain name servers, I get the
> > correct IP. But everything else will be using the root name
> > servers. The root name servers see the original host record and use
> > that.
> >
> > The problem is simple: NSI won't remove a host record from their
> > registry:
> > 1) If it's pointed at by another domain.
> > 2) If you didn't register it with them.
> > 3) Even if you fix #1 and #2, they still won't remove it. :((((
>
> Yep, you are right on. This is my situation completely. Since the gtld
> servers list my dns server as last in the "AUTHORITY SECTION" entry, I
> think I should be okay even if they have the wrong ip address for my
> dns server. What do you think? If I read you correctly, you are saying
> that even if I remove my personal dns server from the AUTHORITY
> SECTION that the dns servers at Register.com maintain, this info will
> not be changed in the Global Top Level Domain name servers. Man, this
> does not sounds good. So far my web server and email server still work
> as they should but doesn't this spell trouble down the road?
>
> Thanks for your insight on this ToddMeister.
>
> drjung
>
> --
> J. Craig Woods
> UNIX/NT Network/System Administration
> http://www.trismegistus.net/resume.html
> Character is built upon the debris of despair --Emerson
>
>
Want to buy your Pack or Services from MandrakeSoft?
Go to http://www.mandrakestore.com
