On Sun, Jun 12, 2011 at 3:51 PM, Camaleón <noela...@gmail.com> wrote:
> On Sun, 12 Jun 2011 15:32:09 +0200, Christian Simo wrote: > > > On Sun, Jun 12, 2011 at 3:10 PM, Camaleón <noela...@gmail.com> wrote: > > >> > ! Whilst checking field 6a on the application form and whilst running > >> > a Reverse check... > >> > ! you specified that "41.134.19.90" would map to "ns1.kom.co.za", ! > >> > but DNS returned "41-134-19-90.dsl.mweb.co.za." > >> > >> What application is giving you that error? > >> > > There is not application that giving me the problem, it's a *.CO.ZA > > Domain registrations *http://www.coza.net.za > > Uh? You mean the domain name registrar? > > Yeah! > > when I tried to update the domain kom.co.za, their (A .CO.ZA Domain > > registry) server sent me an Invalid Nameserver errors > > > > Telling that my name server (n1.kom.co.za and n2.kom.co.za) that I > > indicated as a Primary and Slave servers FQDN are not pointing on > > 41.134.19.90 and 41.134.19.91 but pointing on > > "41-134-19-90.dsl.mweb.co.za" and " 41-134-19-91.dsl.mweb.co.za > > <http://41-134-19-90.dsl.mweb.co.za/>" > > > > I even emailed to my ISP the errors and still waiting for their > > responses. > > I'm afraid you will have to wait for their response. Or forget about this > setup and try with another one (e.g., use an external free DNS service to > resolve your domain, like DynDNS or such). > > On Monday, If not yet response, I much resend the mails to them, Before decide to switch to the external DNS services. > If I correctly read the error message, your registrar needs that you > domain name (n1.kom.co.za) is properly configured by the owner of the > IPs, that is, your ISP. > > > what make me so strange is that I never login on the Cisco router to > > really see how the configuration looks. > > That's not the usual setup in many countries and having the control of > your router is very useful as you don't need to wait a response from your > ISP for every change you want to do. > > I don't know why there are doing like that, I has been waiting for their response since yesterday, the thing that I know now is that the IPs 41.134.19.90 and 41.134.19.91 are pointing to their hostnames > is it something's wrong with my Debian machine configurations? > > Dunno, but one thing for sure: this is a complex setup. > I know! > > Greetings, > > -- > Camaleón > > > -- > To UNSUBSCRIBE, email to debian-user-requ...@lists.debian.org > with a subject of "unsubscribe". Trouble? Contact > listmas...@lists.debian.org > Archive: http://lists.debian.org/pan.2011.06.12.13.51...@gmail.com > >
