authoritive??!??

[Andris Kalnozols]

> 
>  The only error I see in the logs is that there is no ttl set (although its
> in there??) and it uses default. apart from that logs tell me no errors...
>  This has got me buggered :)
> Brad
> 
> Barry Margolin <barmar at bbnplanet.com> wrote in message
> news:YmnG4.11$cS2.507 at burlma1-snr2...
> > In article <8cc3c1$m6v$1 at bugstomper.ihug.com.au>,
> > Brad <bradk at aulink.net> wrote:
> > > I have a small problem....I am getting feedback from a site that is
> > > saying my nameserver is not authoritive for the domain...

I think I see the problem:
  1. Some site contacts you and says that one of your nameservers is
     not authoritative for your domain.  "Authoritative" is used in its
     broadest sense.
  2. You seek help in this forum.
  3. Experienced DNS administrators see "authoritative" in a more strict
     context, i.e., one or more misconfigured data files are preventing
     the nameserver from doing its job.  Suggestions and advice follow.
  4. Despite all this, the problem continues.  Frustration ensues.

What you have is network problem.  'name1.aulink.net' may in fact be a
a functioning authoritative nameserver from where you are (and possibly
for others on different networks) but it is unreachable from where I am.
This is probably what's affecting the site that originally reported the
problem to you as well.

; <<>> DiG 8.2 <<>> aulink.net ns @e.root-servers.net +norec
; (1 server found)
;; res options: init defnam dnsrch
;; got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 45918
;; flags: qr; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 2
;; QUERY SECTION:
;;      aulink.net, type = NS, class = IN

;; ANSWER SECTION:
aulink.net.             2D IN NS        NAME.aulink.net.
aulink.net.             2D IN NS        NAME1.aulink.net.

;; ADDITIONAL SECTION:
NAME.aulink.net.        2D IN A         203.42.220.209
NAME1.aulink.net.       2D IN A         203.42.220.212

traceroute to name.aulink.net (203.42.220.209), 30 hops max, 20 byte packets
 1 hpl-2l.hpl.hp.com (15.255.176.4)                2 ms    1 ms    1 ms
 2 palhgw19.hpl.hp.com (15.25.0.20)                1 ms    1 ms    1 ms
 3 paleagw6.cns.hp.com (15.1.200.36)               1 ms    1 ms    1 ms
 4 906.Hssi5-0.GW1.PAO1.ALTER.NET (157.130.192.117)    2 ms    2 ms    2 ms
 5 119.ATM2-0.XR1.PAO1.ALTER.NET (146.188.147.234)    2 ms    1 ms    2 ms
 6 189.ATM6-0.XR1.SFO4.ALTER.NET (146.188.146.210)    5 ms    4 ms    4 ms
 7 191.ATM9-0-0.GW5.SFO4.ALTER.NET (146.188.149.33)    5 ms    5 ms    6 ms
 8 att-gcs-gw.customer.ALTER.NET (157.130.197.78)    6 ms    5 ms    5 ms
 9 199.37.127.182 (199.37.127.182)                 6 ms    5 ms    5 ms
10 205.174.75.70 (205.174.75.70)                 254 ms  257 ms  254 ms
11 GigabitEthernet3-0.wel-core3.Perth.telstra.net (203.50.113.17)  253 ms
   254 ms  255 ms
12 Pos1-1.ken-core1.Sydney.telstra.net (203.50.6.89)  302 ms  301 ms  305 ms
13 Pos6-0-0.chw-core1.Sydney.telstra.net (203.50.6.26)  302 ms  302 ms  312 ms
14 Fddi0-1-0.chw11.Sydney.telstra.net (139.130.36.233)  308 ms  302 ms  309 ms
15 name.aulink.net (203.42.220.209)              444 ms  431 ms  429 ms

A traceroute to 'name1.aulink.net' only makes it as far as hop 14.

Hope this helps,

Andy