reverse name resolution
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 200.247.36.2
---
my named.conf.local:
zone 0/25.36.247.200.in-addr.arpa {
type master;
file /etc/bind/zones/200.247.36;
};
---
my 200.247.36 file:
$TTL 3D
@ IN SOA helium.prodar.com.br. hostmaster.prodar.com.br (
200411193
604800
86400
2419200
604800 )
IN NS helium.prodar.com.br.
1 IN PTR hydrogenium.prodar.com.br.
2 IN PTR helium.prodar.com.br.
---
can someone give me a light?
thanks in advance.
--
Djalma Fadel Junior
Diretor Técnico
Ferasoft Corporation Ltda
+55 (19) 3542-3490
[EMAIL PROTECTED]
Re: reverse name resolution
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
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 delegation
by your provider.
Regards,
Philipp Kern
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reverse name resolution
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 not found: 3(NXDOMAIN) # host helium.prodar.com.br helium.prodar.com.br has address 200.247.36.2 Are you sure that reverse dns has been delegated to you? Even the T1 provider we use at work won't give us a reverse delegation these days. You have to talk to them and get them to setup reverse dns to look like you want it to - even though name to ip resolution works normally. HTH, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reverse 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 comments about having to have your upstream ISP delegate the
reverses properly is important also - and they can't just do it and tell
you it's done. They have to provide you their naming convention for
the delegated zones so you can line yours up with theirs.
(I guess they *could* just tell you it's done and then you'd have to
use dig to figure out exactly how they did it, which is fine also...)
Nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reverse name resolution
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 zone 36.247.200.in-addr.apra i tried, but doesn't work. so I got the following error Host 2.36.247.200.in-addr.arpa not found: 2(SERVFAIL) what do you have in your /etc/resolv.conf? dns server resolv.conf file: search helium.prodar.com.br prodar.com.br nameserver 127.0.0.1 On 23.11.2004, at 19:04, Jacob S wrote: 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 not found: 3(NXDOMAIN) # host helium.prodar.com.br helium.prodar.com.br has address 200.247.36.2 Are you sure that reverse dns has been delegated to you? Even the T1 provider we use at work won't give us a reverse delegation these days. You have to talk to them and get them to setup reverse dns to look like you want it to - even though name to ip resolution works normally. HTH, Jacob -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED] -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reverse name resolution
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 working by that way, that is the way I read in BIND tutorial.
the server was upgraded recently.
do you know if this was changed in later versions?
is there some problem to keep zone 36.247.200.in-addr.arpa since I have set a
/25 mask from my ISP? (from 0 to 127).
thanks you all
--
Djalma Fadel Junior
Diretor Técnico
Ferasoft Corporation Ltda
+55 (19) 3542-3490
[EMAIL PROTECTED]
Re: reverse name resolution
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 that your ISP
must be on the same page with you when they do the delegation. A couple
years ago, I was working with an ISP in southern cal that was big enough to
hire a full time DNS administration staff and they were all incompetent. I
had to teach them how to do this so don't be surprised if you have to do the
same. Making it read like this:
zone 36.247.200.in-addr.arpa {...
is a dirty hack and should not be done. It also breaks reverse lookups for
the rest of the hosts in that class C for you.
vec
- Original Message -
From: Nate Duehr [EMAIL PROTECTED]
To: [EMAIL PROTECTED]
Sent: Tuesday, November 23, 2004 11:34 AM
Subject: Re: reverse 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 comments about having to have your upstream ISP delegate the
reverses properly is important also - and they can't just do it and tell
you it's done. They have to provide you their naming convention for the
delegated zones so you can line yours up with theirs.
(I guess they *could* just tell you it's done and then you'd have to use
dig to figure out exactly how they did it, which is fine also...)
Nate
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact
[EMAIL PROTECTED]
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
Re: reverse name resolution
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 that your ISP
must be on the same page with you when they do the delegation. A couple
years ago, I was working with an ISP in southern cal that was big enough to
hire a full time DNS administration staff and they were all incompetent. I
had to teach them how to do this so don't be surprised if you have to do the
same. Making it read like this:
zone 36.247.200.in-addr.arpa {...
is a dirty hack and should not be done. It also breaks reverse lookups for
the rest of the hosts in that class C for you.
well yes (though there was no notion of the /25 in the given config, so
how should i have known).. ;)
Assuming it's the inverse of the DNS it should be a
7/0.37.247.200.in-addr.arpa for a /25, right?
(as in 32-25=7)
--
Best regards,
Kilian
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
Re: reverse name resolution
I'm sorry I thought the given config had 0/25 in it. It has been a while since I was current on RFC2317 but I think it actually uses the netmask not the remaining bits that the network is on. So in the case of a /25 if you have the lower 128 addresses like the gentlemen who started the tread 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 resolution well yes (though there was no notion of the /25 in the given config, so how should i have known).. ;) Assuming it's the inverse of the DNS it should be a 7/0.37.247.200.in-addr.arpa for a /25, right? (as in 32-25=7) -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of unsubscribe. Trouble? Contact [EMAIL PROTECTED]
