Should be dnsreport.com

Re: Should be dnsreport.com

From:

Date:

Time:

>That's odd. Your very own product (DNS Expert 1.6) had this to say in its
>analysis report of goya.com.au:
>
>>Errors
>>----------------------------------------------------------------------
>>o Unable to resolve the name "mail.goya.com.au." because glue data
>> for the domain "goya.com.au." is missing

ok, here's where we lose 95% of the lurkers!! :))

The problem is that while the com.au NSs don't have any glue for .net
domains (normal), they erroneously don't have any glue at for goya.com.au,
which is an error by the com.au, NOT a fault in DNS operation. See this
query:

# dig @au2ld.CSIRO.au. goya.com.au any

; <<>> DiG 9.2.3rc3 <<>> @au2ld.CSIRO.au. goya.com.au any
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 18271
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;goya.com.au. IN ANY

;; AUTHORITY SECTION:
goya.com.au. 3600 IN NS mail.goya.com.au.
goya.com.au. 3600 IN NS ns1.telstra.net.

and if you ask explicitly for the A record for mail.goya.com.au (which is
should/could have as being in the same .au domain), it doesn't have it:

# dig @au2ld.CSIRO.au. mail.goya.com.au a

; <<>> DiG 9.2.3rc3 <<>> @au2ld.CSIRO.au. mail.goya.com.au a
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 36725
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 0

;; QUESTION SECTION:
;mail.goya.com.au. IN A

... and it should have that A record.

The registrant for goya.com.au needs to take this error up with his
registrar, who should take it up with com.au registry.

However, this admin error (leaving out a glue record) by the com.au NSs has
nothing to do with "missing glue" when parent NSs are setup correctly.

>> The delegation data for "goya.com.au." indicates that the host
>> "mail.goya.com.au." contains authoritative data for the zone, but
>> there is not enough data available to locate "mail.goya.com.au.".

DNSExpert is correct in noting the error in the setup of the com.au server
for the goya.com.au domain.

>Now what were you saying about misleading missing glue alerts?

Nothing has changed in my evaluation of the misleading "missing glue" BS at
DNSReports.

>Then you are also saying that your own $495 product is inaccurate....yes?
>DNS Expert also had this _error_:

DNS Expert failed to resolve the glue/A record for mail.goya.com.au at the
all of the .com.au parent NSs because the A record does not exist in
.com.au NSs, and it should.

btw, I have never seen DNS Expert complain about cannot resolve glue
records, and I've been using DNS Expert for years on l000's of domains. An
NS not having glue THAT SHOULD BE PRESENT is extremely rare, ime.

>My my...better put those rocks down.

my, my, you better get up a LOT earlier in the morning if you want to beat
me on DNS issues. :))

nope, my complaints about "missing glue" BS from DNSReports are not
invalidated by an error in the com.au server. But I don't expect you, or
anybody else here, to appreciate the differences without this explanation:

1. My complaint is: DNSReport WARNs about ALL correctly missing "missing
glue" at any NS that should not, and will never have such glue, and is
"missing" such glue for perfectly valid reasons.

2. DNSExpert has detected an ERROR by the .com.au NSs because they are
missing .com.au glue THAT THEY SHOULD HAVE.

Does everybody here not understand the differences between points 1. and 2. ?

So, while you think you "got" me and you "got" DNS Expert screwing up, both
of us have identified a serious error, not warning, in the com.au. NSs.

And my complaint about the "missing glue" BS from DNSReport remains valid.

Len

Sales:
888/4-DPOINT

Support:
858/452-3696