Locally DNS works finely but my provider cannot point to my name servers ! really need your feedback !!!

[G. Roderick Singleton]

Daniel Pope wrote:
> 
> Thank you very much for your kindness to answer me !
> I'm afraid that ns1.network-server.com and ns2.hosting-server.com are the
> names servers of my provider and he got the mentioned error messages
> when he tried to point them to my domain servers:  ns1.ticket2print.com
> and ns2.ticket2print.com.
>  Is there a method to check what's wrong, my settings (locally everyting
> works finely) or my provider forward to my servers ?
> Many thanks again !!!
> 
> -----Original Message-----
> From: Kevin Darcy <kcd at daimlerchrysler.com>
> To: comp-protocols-dns-bind at moderators.isc.org
> <comp-protocols-dns-bind at moderators.isc.org>
> Date: Tuesday, August 22, 2000 5:21 PM
> Subject: Re: Locally DNS works finely but my provider cannot point to my
> name servers ! really need your feedback !!!
> 
> >
> >According to the TLD servers, ticket2print.com is delegated to
> ns1.network-server.com and
> >ns2.hosting-server.com. Neither those servers nor the TLD servers appear to
> know anything about
> >ns1.ticket2print.com or ns2.ticket2print.com and of course therefore can't
> provide glue records for those
> >servers. You need to change the nameservers on your domain record, through
> your registrar, before this domain
> >can become functional.
> >
> >
> >- Kevin
> >
> >Daniel Pope wrote:
> >
> >> Hello,
> >> I'm sorry to disturb you again, but I need your help more than ever !!!
> >> I successfully  setup locally my name servers (I checked the log file and
> with nslookup).
> >> When my web provider who registered my  domain name tried to point to
> them he got the
> >> following messages:
> >>
> >> ***********
> >> Error Page
> >> <<Unable to update nameservers: Command failed: unable to verify
> existence of nameserver ns1.ticket2print.com
> >> *************
> >> I don't know what it is wrong !
> >>  Any help would be greatly appreciated !!!
> >>
> >> Here are  my settings :
> >>
> >> ; Zone file for ticket2print.com
> >> ;
> >> ; The full zone
> >> ;
> >> ticket2print.com.  IN  SOA  ns1.ticket2print.com.
> hostmaster.ticket2print.com. (
> >>    2000081607    ; serial number, today
> >>    10800         ;Refresh after 3 hours
> >>    3600          ;Retry after 1 hour
> >>    604800        ;expire after a week
> >>        86400 )       ;Minimum TTK of 1 day
> >> ;
> >> ;  Name servers
> >> ;
> >>
> >> ticket2print.com.          IN   NS  ns1.ticket2print.com.
> >> ticket2print.com.          IN   NS  ns2.ticket2print.com.
> >>
> >> ;
> >> ; Addresses for canonical names
> >> ;
> >>
> >> localhost.ticket2print.com.  IN    A   127.0.0.1
> >> hercules.ticket2print.com.   IN    A   64.232.5.110
> >> ns1.ticket2print.com.      IN    A   64.232.5.110
> >> ns2.ticket2print.com.      IN    A   64.232.5.111
> >> ;
> >> ; Aliases
> >> ;
> >>
> >> www.ticket2print.com. IN  A 64.232.5.110
> >> ticket2print.com.       IN  A   64.232.5.110
> >> ;www.ticket2print.com. IN  CNAME hercules.ticket2print.com.
> >>
> >> ;
> >> ;Mail routing;
> >>
> >> ticket2print.com.   IN   MX    10     mail.ticket2print.com.
> >
> >
> >
> >
> >
> >


Daniel,

Your registrar is where you register your nameservers just as I told you
on Sunday.  Here's an excerpt from the opensrs.org/Support_FAQ:

> 7.How do I define a nameserver that's based on a domain I registered with
> OpenSRS (i.e. ns1.myopensrsdomain.com)? 
> 
> If you want to create or modify a nameserver which is based on the
> domain you are modifying (i.e. ns1.mydomain.com) you can do this on the
> production environment Web interface: http://manage.opensrs.net/ 
> 
> Select "Manage Name Servers" and then select the link "If you want to
>  create or modify a nameserver which is based on foo.com" at the bottom
>  of that page. Note: this only works for domains registered through us! 
> 
> Please note that we do not maintain the database of nameservers, we
> merely have the ability to update the host file which is maintained by
> the Registry. RSPs need not have nameservers added through our system
> for any reason other than if they do not exist in the root host file. 
> 
> A few things to keep in mind about nameservers in general: A
> characteristic of DNS (as per the relevant RFCs) is that all nameservers
> must have a unique IP address. If you do a "whois host " with the IP
> address, that would query the root server to see if a nameserver is
> already associated with it. 
> 

I hope this clears things up for you.


-- 
________________________________________________________________________________
G. Roderick Singleton, <gsingleton at home.com> PATH tech,
71 Underhill Drive, Unit 159, Toronto, ON  M3A 2J8
Voice : 416-452-4583 Fax: 416-452-0036 Toll Free: 1-888-354-PATH
________________________________________________________________________________

*** Notice To Bulk Emailers: Attention!  Pursuant to US Code, Title 47,
Chapter 5, Subchapter II, 227, any & all unsolicited commercial e-mail
sent to this address is subject to a download and archival fee in the
amount of the $1500 US and copies will be forwarded to domain
administrators.  Emailing denotes acceptance of said terms!