[an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive] (none) [an error occurred while processing this directive] [an error occurred while processing this directive] [an error occurred while processing this directive][an error occurred while processing this directive]
 
[an error occurred while processing this directive] [an error occurred while processing this directive]
Skåne Sjælland Linux User Group - http://www.sslug.dk Home   Subscribe   Mail Archive   Forum   Calendar   Search
MhonArc Date: [Date Prev] [Date Index] [Date Next]   Thread: [Date Prev] [Thread Index] [Date Next]   MhonArc
 

Re: [NETVAERK] Problemer med reverse lookup



Hej


Problemet er identificeret.

Vi skal selv oprette reverse-lookup records hos RIPE. Dette var så ikke 
gjort for de 2 segmenter (af ukendte årsager)



/Bjørn

"Bjørn" <sslug@sslug> skrev i en meddelelse 
news:sslug@sslug
> Hej alle i gode kloge (?) mennesker
>
> Jeg har nogle problemer med reverse lookup.
>
> Vi har et /19 netværk. X.Y.64.0 - X.Y.95.255
>
> Der er oprettet reverse zones for alle segmenter, men kun de første 30 
> virker.
> Reverse lookup virker på X.Y.64.0 - X.Y.93.255, f.eks:
> -----------------------------------------------------------------------------
> fe1:~# dig -x X.Y.74.142
>
> ; <<>> DiG 9.2.4 <<>> -x X.Y.74.142
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9856
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 3, ADDITIONAL: 3
>
> ;; QUESTION SECTION:
> ;142.74.Y.X.in-addr.arpa.    IN      PTR
>
> ;; ANSWER SECTION:
> 142.74.Y.X.in-addr.arpa. 86400 IN    PTR     X.Y.74.142.xxxxxx.dk.
>
> ;; AUTHORITY SECTION:
> 74.Y.X.in-addr.arpa. 86400   IN      NS      ns3.xxxxxx.dk.
> 74.Y.X.in-addr.arpa. 86400   IN      NS      ns1.xxxxxx.dk.
> 74.Y.X.in-addr.arpa. 86400   IN      NS      ns2.xxxxxx.dk.
>
> ;; ADDITIONAL SECTION:
> ns1.xxxxxx.dk.       12379   IN      A       X.Y.64.242
> ns2.xxxxxx.dk.       12379   IN      A       Z.V.235.19
> ns3.xxxxxx.dk.       12379   IN      A       X.Y.64.254
>
> ;; Query time: 40 msec
> ;; SERVER: 83.90.63.163#53(83.90.63.163)
> ;; WHEN: Wed Apr 25 08:16:24 2007
> ;; MSG SIZE  rcvd: 186
>
> -----------------------------------------------------------------------------
>
> men på adresser X.Y.94.0 - X.Y.95.255 for jeg følgende besked fra dig:
>
> -----------------------------------------------------------------------------
> fe1:~# dig -x X.Y.95.142
>
> ; <<>> DiG 9.2.4 <<>> -x X.Y.95.142
> ;; global options:  printcmd
> ;; Got answer:
> ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30373
> ;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
>
> ;; QUESTION SECTION:
> ;142.95.Y.X.in-addr.arpa.    IN      PTR
>
> ;; AUTHORITY SECTION:
> X.in-addr.arpa.        7200    IN      SOA     ns-pri.ripe.net. 
> ops.ripe.net. 2007042527 3600 7200 1209600 7200
>
> ;; Query time: 156 msec
> ;; SERVER: 83.90.63.163#53(83.90.63.163)
> ;; WHEN: Wed Apr 25 08:08:23 2007
> ;; MSG SIZE  rcvd: 99
>
> -----------------------------------------------------------------------------
>
> zonefil for X.Y.74 og X.Y.95 er sat ens op - selvfølgelig med de rigtige 
> netværks adresser.
>
>
> Det er lige som om, at når der skal traverseres (??) ned gennem 
> DNS-strukturen, så har root-serverene forkert (eller ingen) information om 
> netop de 2 fejlende segmenter.
>
> Er der nogen der kan forklare hvad og hvor det går galt ?
>
>
> -- 
>
> Venlig hilsen
>
> Bjørn
>
> ------------------------------------------
>
> On a clear disk, you can seek forever
> 




 
Home   Subscribe   Mail Archive   Index   Calendar   Search

 
 
Questions about the web-pages to <www_admin>. Last modified 2007-05-01, 02:01 CEST [an error occurred while processing this directive]
This page is maintained by [an error occurred while processing this directive]MHonArc [an error occurred while processing this directive] # [an error occurred while processing this directive] *