Can anybody help with the error I received from the co.za registrar concerning ns2.granitecanyon.com.
Michael
delegated - please can you do something about this. This e-mail will
be repeated every 8 hours until the request is 5 days old or it is
fixed. It will then be deleted.
-----------------------------------------------------------------------
Checking Nameservers for screenplay.co.za...
You have specified 2 Servers:-
ns1.granitecanyon.com, ns2.granitecanyon.com.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Contacting and examining info at "ns1.granitecanyon.com" (205.166.226.38)
Domain "screenplay.co.za." appears configured...
Serial_Number = 225304249
Domain_Origin = ns1.granitecanyon.com
Mail_Address = michae...@hotmail.com
The 2 NS Records are:-
ns2.granitecanyon.com, ns1.granitecanyon.com.
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
Contacting and examining info at "ns2.granitecanyon.com" (65.102.83.43)
ERROR: ***Reverse*** DNS not setup and running for 65.102.83.43
! You may have an SOA record - but I can't get to it with 'nslookup'
Host is unpingable
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
SUSPEND: 1 Errors were found in screenplay.co.za - request sleeping
--------------------------------------------------------------------
The co.za support team - sup...@co.za
Torsten Mueller
Michael schrieb:
>
> Your application for the following domain is still not correctly
> delegated - please can you do something about this. This e-mail will
> be repeated every 8 hours until the request is 5 days old or it is
> fixed. It will then be deleted.
>
> -----------------------------------------------------------------------
>
> Checking Nameservers for screenplay.co.za...
> You have specified 2 Servers:-
> ns1.granitecanyon.com, ns2.granitecanyon.com.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Contacting and examining info at "ns1.granitecanyon.com" (205.166.226.38)
>
> Domain "screenplay.co.za." appears configured...
> Serial_Number = 225304249
> Domain_Origin = ns1.granitecanyon.com
> Mail_Address = michae...@hotmail.com
> The 2 NS Records are:-
> ns2.granitecanyon.com, ns1.granitecanyon.com.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> Contacting and examining info at "ns2.granitecanyon.com" (65.102.83.43)
> ERROR: ***Reverse*** DNS not setup and running for 65.102.83.43
That's correct and should be fixed by the admin of ns1.uswest.net as
43.83.102.65.IN-ADDR.ARPA 86400 IN PTR
soa2.granitecanyon.com
which confuses your registrar.
> ! You may have an SOA record - but I can't get to it with 'nslookup'
>
> Host is unpingable
2 possible reasons for this: ns2.gc.com reloads and is that's why
"unreachabel".
However the message is unpingable is normal for the gc servers, as they
deny icmp
echos.
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> SUSPEND: 1 Errors were found in screenplay.co.za - request sleeping
> --------------------------------------------------------------------
>
> The co.za support team - sup...@co.za
Possible solution for your problem:
Look for another secondary server than ns2.gc.com
http://www.gratisdns.de/
http://www.xname.org/
http://www.twisted4life.com/
...
Edit your record at gc (exclude ns2 , insert your new secondary).
This is against the terms of use of GC, but i think, it's o.k.
in your case, as the PTR record for ns2.gc.com is "misconfigured".
Torsten
Fred Viles
<3d1f7ddd$0$85684$b9f6...@news.granitecanyon.com>:
>Michael schrieb:
>>...
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - Contacting and examining info at "ns2.granitecanyon.com"
>> (65.102.83.43) ERROR: ***Reverse*** DNS not setup and running
>> for 65.102.83.43
>
>That's correct and should be fixed by the admin of ns1.uswest.net
>as
>43.83.102.65.IN-ADDR.ARPA. IN PTR soa2.granitecanyon.com.
>which confuses your registrar.
I don't see a problem with the reverse DNS setup here. But I think
that the fact that the PTR name returns twp A records may be
confusing nslookup.
>> ! You may have an SOA record - but I can't get to it with
>> 'nslookup'
They should use dig, not nslookup.
>> Host is unpingable
>
>2 possible reasons for this: ns2.gc.com reloads and is that's why
>"unreachabel".
>However the message is unpingable is normal for the gc servers, as
>they deny icmp
>echos.
Right. However, at the moment NS2 seems to be down for other
reasons.
>> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>> - - SUSPEND: 1 Errors were found in screenplay.co.za - request
>> sleeping
>> -----------------------------------------------------------------
>> ---
>>
>> The co.za support team - sup...@co.za
>
>Possible solution for your problem:
>
>Look for another secondary server than ns2.gc.com
>...
>Edit your record at gc (exclude ns2 , insert your new secondary).
If you set up a Primary DNS type of account at GC, the web interface
will not let you omit either of the GC NS records.
- Fred
--
Want to know more?
Online documentation for BIND 8.x:
<http://www.isc.org/products/BIND/docs/index.html>
FAQ for the comp.protocols.tcp-ip.domains newsgroup:
<http://www.intac.com/~cdp/cptd-faq/>
Lots of great info and links at The DNS Resources Directory:
<http://www.dns.net/dnsrd/>
A great PC query tool: CyberKit (was at <http://www.cyberkit.net>)
To make DNS queries from the web: <http://www.epideme.com/digger/>
Torsten Mueller
Fred Viles schrieb:
>
> Torsten Mueller <tor...@archesoft.de> wrote in
> <3d1f7ddd$0$85684$b9f6...@news.granitecanyon.com>:
>
> >Michael schrieb:
> >>...
> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> - - Contacting and examining info at "ns2.granitecanyon.com"
> >> (65.102.83.43) ERROR: ***Reverse*** DNS not setup and running
> >> for 65.102.83.43
> >
> >That's correct and should be fixed by the admin of ns1.uswest.net
> >as
> >43.83.102.65.IN-ADDR.ARPA. IN PTR soa2.granitecanyon.com.
> >which confuses your registrar.
>
> I don't see a problem with the reverse DNS setup here. But I think
> that the fact that the PTR name returns twp A records may be
> confusing nslookup.
>
O.K. better the errormessage would be:
None of the PTR records found for 65.102.83.43 mapped back
to ns2.granitecanyon.com
The co.za registry seems to like that forward and reverse resolution
matches, which isn't the case for ns2.gc.com
ns2.gc.com -> 65.102.83.43
65.102.83.43 -> soa.gc.com
> >> ! You may have an SOA record - but I can't get to it with
> >> 'nslookup'
>
> They should use dig, not nslookup.
>
> >> Host is unpingable
> >
> >2 possible reasons for this: ns2.gc.com reloads and is that's why
> >"unreachabel".
> >However the message is unpingable is normal for the gc servers, as
> >they deny icmp
> >echos.
>
> Right. However, at the moment NS2 seems to be down for other
> reasons.
>
> >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
> >> - - SUSPEND: 1 Errors were found in screenplay.co.za - request
> >> sleeping
> >> -----------------------------------------------------------------
> >> ---
> >>
> >> The co.za support team - sup...@co.za
> >
> >Possible solution for your problem:
> >
> >Look for another secondary server than ns2.gc.com
> >...
> >Edit your record at gc (exclude ns2 , insert your new secondary).
>
> If you set up a Primary DNS type of account at GC, the web interface
> will not let you omit either of the GC NS records.
I didn't know that (i don't use gc as primary).
So, in time Michael has no chance using the GC servers for his zone as
i don't think that the co.za registry will change their checking script.
Some time ago i also had "trouble" with the co.za registry, as they
didn't
like my reverse setup (CIDR) for my net (possible as they use
nslookup in their scripts).
Torsten
Michael Brauer
I have had endless hassles with co.za registrations as they are not prepared
to accommodate anybody in any way it seems when it comes to their
registrations. I have had months of debacles between www.powerdns.com and
co.za to try and get this domain up on to dns, but neither were prepared to
budge, so the client once again suffers.
It seems that I have the same problem with GC, but I have a question - would
it not be possible to add another NS record to ns1.twisted4life.com as
secondary and send ns1.granitecanyon.com & ns1.twisted4life.com to the co.za
registry? Will GC allow this and is it DNS protocol?
Another question I have is why do you think GC has set-up ns1 & ns2 to
respond differently with nslookup.?
Thanks Again
Mike
"Torsten Mueller" <tor...@archesoft.de> wrote in message
news:3d20c787$0$85683$b9f6...@news.granitecanyon.com...
Torsten Mueller
Michael Brauer schrieb:
>
> Thanks for all your contributions so far.
>
> I have had endless hassles with co.za registrations as they are not prepared
> to accommodate anybody in any way it seems when it comes to their
> registrations. I have had months of debacles between www.powerdns.com and
> co.za to try and get this domain up on to dns, but neither were prepared to
> budge, so the client once again suffers.
>
> It seems that I have the same problem with GC, but I have a question - would
> it not be possible to add another NS record to ns1.twisted4life.com as
> secondary and send ns1.granitecanyon.com & ns1.twisted4life.com to the co.za
> registry? Will GC allow this and is it DNS protocol?
It seems, that the co.za registry checks the DNS servers. So they would
get
at a minimum ns1 and ns2 back (as Fred pointed out, that it is not
possible
in the Primary setup to delete ns2.gc.com from the NS records).
Your only way is to look for another primary server than GC. Than you
could
use gc as secondary (but only ns1.gc.com) and additional other servers
as
secondaries.
Maybe you find one, that suits your needs at:
https://dns.xtremeweb.de/htmllinks.html
> Another question I have is why do you think GC has set-up ns1 & ns2 to
> respond differently with nslookup.?
From the point of the co.za registry they are diffrent, as:
o.k.
ns1.gc.com -> 205.166.226.38
205.166.226.38 -> ns1.gc.com
not o.k.
ns2.gc.com -> 65.102.83.43
65.102.83.43 -> soa.gc.com
This has nothing to do nslookup, as 65.102.83.43 only has
1 PTR record (soa.gc.com).
The "nslookup thing" makes sometimes problems, if parts of a reverse
zones are "redelegated", which sometimes confuses nslookup.
Torsten