On Sat, Mar 15, 2008 at 4:09 PM, McTim <[EMAIL PROTECTED]> wrote:
> On Sat, Mar 15, 2008 at 2:28 PM, Reinier Battenberg
> <[EMAIL PROTECTED]> wrote:
> >
> > absolutely brilliant!
>
> hmmm allows axfr for those domains who have closed axfr!
> > (and then I tried it for rw, to see what happened to the value of the
> verbose
> > parameter. And for rw this trick does not work. Mmmm, same for tz.
> >
> > McTim, who is in error here? tz & rw, or ug?
>
> Well if the idea is to deny axfr, then .ug needs to close this "loophole".
>
> It seems to me that ns.one2net.co.ug is giving up the zone, is that
> correct? (since it doesn't "REFUSE"):
*
WRONG!! **We have 7 name servers for .ug but look at this bit **last
nameserver probed is guess and its not Ugandan manned no one is immune
just need time :-)
{
Decided to use ns.ripe.net (193.0.0.193) for zone check
Checking whether ns.ripe.net knows an A record for its own name
Checking whether ns.ripe.net is able to reverse-map its own IP address
Checking connectivity with other nameservers
### Error: Unable to resolve www.ucw.cz: REFUSED
### Warning: ns.ripe.net is unable to resolve www.ucw.cz (maybe it's
non-recursive)
### Error: Unable to resolve atrey.karlin.mff.cuni.cz: REFUSED
### Warning: ns.ripe.net is unable to resolve
atrey.karlin.mff.cuni.cz(maybe it's non-recursive)
### Error: Unable to resolve www.google.com: REFUSED
### Warning: ns.ripe.net is unable to resolve www.google.com (maybe it's
non-recursive)
Checking mapping of localhost
### Error: Unable to resolve localhost: REFUSED
### Warning: ns.ripe.net is unable to resolve localhost [see
RFC1912:4.1<http://rfc.net/rfc1912.html#s4.1>for details]
Fetching zone data for ug
Parsing zone data
Checking consistency of zone records *
* ug. 3600 IN NS ns-ug.ripe.net.
ug. 3600 IN NS web.eahd.or.ug.
ug. 3600 IN NS ns.ripe.net.
ug. 3600 IN NS ns.one2net.co.ug.
ug. 14400 IN SOA web.eahd.or.ug. beg_g.eahd.or.ug. (
2008031312 ; Serial
86400 ; Refresh
3600 ; Retry
2592000 ; Expire
14400 ) ; Minimum TTL
*
*Hostmaster e-mail address is [EMAIL PROTECTED]
### Error: No MX record for eahd.or.ug
### Warning: Expire time should be between 2 and 4 weeks [see
RFC1912:2.2<http://rfc.net/rfc1912.html#s2.2>for details]
*
* ug. 3600 IN NS ns-ext.vix.com.
ug. 3600 IN NS ns.icann.org.
ug. 3600 IN NS demon.mtn.co.ug.
123.ug. 3600 IN NS pns.innterdns.net.
*
*
*
> *
> * *
> ug. 3600 IN NS ns.one2net.co.ug.
>
> *
> *### Error: Nameserver ns.one2net.co.ug doesn't have any valid A records
> * *
> ug. 14400 IN SOA web.eahd.or.ug. beg_g.eahd.or.ug. (
> 2008031312 ; Serial
> 86400 ; Refresh
> 3600 ; Retry
> 2592000 ; Expire
> 14400 ) ; Minimum TTL
>
> *
> *### Error: No A record for zone origin
> * *Hostmaster e-mail address is [EMAIL PROTECTED]
> ### Error: No MX record for eahd.or.ug
> *
> *### Warning: Expire time should be between 2 and 4 weeks [see
> RFC1912:2.2 for details]
> * *
> ug. 3600 IN NS ns-ext.vix.com.
>
> *
> *### Error: Unable to resolve ns-ext.vix.com: REFUSED
> ### Error: Nameserver ns-ext.vix.com doesn't have any valid A records
> * *
> ug. 3600 IN NS ns.icann.org.
>
> *
> *### Error: Unable to resolve ns.icann.org: REFUSED
> ### Error: Nameserver ns.icann.org doesn't have any valid A records
> * *
> ug. 3600 IN NS demon.mtn.co.ug.
>
> *
> *### Error: Nameserver demon.mtn.co.ug doesn't have any valid A records
> * *
> 123.ug. 3600 IN NS pns.innterdns.net.}*
>
Correct me if wrong
Ronny
> *
> *
>
>
> --
> Cheers,
>
> McTim
> $ whois -h whois.afrinic.net mctim
> _______________________________________________
> LUG mailing list
> [email protected]
> http://kym.net/mailman/listinfo/lug
> %LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
>
> The above comments and data are owned by whoever posted them (including
> attachments if any). The List's Host is not responsible for them in any way.
> ---------------------------------------
>
>
_______________________________________________
LUG mailing list
[email protected]
http://kym.net/mailman/listinfo/lug
%LUG is generously hosted by INFOCOM http://www.infocom.co.ug/
The above comments and data are owned by whoever posted them (including
attachments if any). The List's Host is not responsible for them in any way.
---------------------------------------
