reverse name resolution

2004-11-23 Thread Djalma Fadel Junior
Hi there, I'm using debian with bind 9 and itsn't reverse resolving. bind version: ii bind9 9.2.4-1 The problem is that I cannot resolve IPs. # host 200.247.36.2 Host 2.36.247.200.in-addr.arpa not found: 3(NXDOMAIN) # host helium.prodar.com.br helium.prodar.com.br has address

Re: reverse name resolution

2004-11-23 Thread Kilian Krause
Hi Djalma, my named.conf.local: zone 0/25.36.247.200.in-addr.arpa { i'd try making this read: zone 36.247.200.in-addr.arpa { for a start.. i.e. without the 0/25. -- Best regards, Kilian signature.asc Description: Dies ist ein digital signierter Nachrichtenteil

Re: reverse name resolution

2004-11-23 Thread Philipp Kern
On Tue, 2004-11-23 at 18:02, Djalma Fadel Junior wrote: my named.conf.local: zone 0/25.36.247.200.in-addr.arpa { 25 (if this is a direct delegation -- your value otherwise) $TTL 3D $ORIGIN 36.247.200.in-addr.arpa You need your nameserver in your resolv.conf or a proper rDNS

Re: reverse name resolution

2004-11-23 Thread Jacob S
On Tue, 23 Nov 2004 15:02:40 -0200 Djalma Fadel Junior [EMAIL PROTECTED] wrote: Hi there, I'm using debian with bind 9 and itsn't reverse resolving. bind version: ii bind9 9.2.4-1 The problem is that I cannot resolve IPs. # host 200.247.36.2 Host 2.36.247.200.in-addr.arpa

Re: reverse name resolution

2004-11-23 Thread Nate Duehr
Kilian Krause wrote: Hi Djalma, my named.conf.local: zone 0/25.36.247.200.in-addr.arpa { i'd try making this read: zone 36.247.200.in-addr.arpa { for a start.. i.e. without the 0/25. Yes, this would be problematic unless for some odd reason you had a directory named 0. The other

Re: reverse name resolution

2004-11-23 Thread Andrew Miehs
He can look at the problem later, at the moment It seems that his name server isn't working correctly... If he wants other people to see his reverse entries, he will have to go talk to his provider Andrew On Tue, 23 Nov 2004 18:53:16 +0100 andrew [EMAIL PROTECTED] wrote: Shouldnt this just be

Re: reverse name resolution

2004-11-23 Thread Djalma Fadel Junior
On Tue, 23 Nov 2004 18:52:38 +0100 Kilian Krause [EMAIL PROTECTED] wrote: Hi Djalma, my named.conf.local: zone 0/25.36.247.200.in-addr.arpa { i'd try making this read: zone 36.247.200.in-addr.arpa { you're right. Without 25/0 worked, but when I installed (some months ago), it was

Re: reverse name resolution

2004-11-23 Thread JB
name resolution Kilian Krause wrote: Hi Djalma, my named.conf.local: zone 0/25.36.247.200.in-addr.arpa { i'd try making this read: zone 36.247.200.in-addr.arpa { for a start.. i.e. without the 0/25. Yes, this would be problematic unless for some odd reason you had a directory named 0. The other

Re: reverse name resolution

2004-11-23 Thread Kilian Krause
Hi JB, Am Dienstag, den 23.11.2004, 14:39 -0700 schrieb JB: You are on the right track. Saying zone 0/25.36.247.200.in-addr.arpa has nothing to do with the file/directory. The file property inside the section deals with that. This is proper RFC2317 reverse delegation but Nate is right in

Re: reverse name resolution

2004-11-23 Thread Vector
then it would like like: 0/25.37.247.200.in-addr.arpa but if he had the upper 128 then it would be more like: 128/25.37.247.200.in-addr.arpa vec - Original Message - From: Kilian Krause [EMAIL PROTECTED] To: [EMAIL PROTECTED] Sent: Tuesday, November 23, 2004 5:18 PM Subject: Re: reverse name