Re: PTR not working...

2009-08-13 Thread Kevin Darcy
sers-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] De la part de Kevin Darcy Envoyé : 6 août 2009 16:06 À : bind-users@lists.isc.org Objet : Re: PTR not working... What you have would only work if you had the whole 70.25.115.0/24 and Bell Canada delegated all of 115.25.70.in-add

RE: PTR not working...

2009-08-13 Thread Ben Bridges
c.org] On Behalf Of > Alexandre Racine > Sent: Thursday, August 13, 2009 10:46 AM > To: bind-users@lists.isc.org > Subject: RE: PTR not working... > > Following all you good comments, I tried different things, > and can't get it to work properly yet. > > If my

RE: PTR not working...

2009-08-13 Thread Alexandre Racine
-- De : bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] De la part de Kevin Darcy Envoyé : 6 août 2009 16:06 À : bind-users@lists.isc.org Objet : Re: PTR not working... What you have would only work if you had the whole 70.25.115.0/24 and Bell Canada delegated all of 115.2

Re: PTR not working...

2009-08-06 Thread Mark Andrews
In message , Chris Hills writes: > Here I get a bad referral: > > 25.70.in-addr.arpa. 86400 IN NS TOROON63NSZP05.SRVR.BELL.CA. > 25.70.in-addr.arpa. 86400 IN NS TOROONDCNSZS05.SRVR.BELL.CA. > ;; Received 113 bytes from 192.35.51.32#53(dill.arin.net) in 173 ms > >

Re: PTR not working...

2009-08-06 Thread Chris Hills
Here I get a bad referral: 25.70.in-addr.arpa. 86400 IN NS TOROON63NSZP05.SRVR.BELL.CA. 25.70.in-addr.arpa. 86400 IN NS TOROONDCNSZS05.SRVR.BELL.CA. ;; Received 113 bytes from 192.35.51.32#53(dill.arin.net) in 173 ms . 360 IN NS

Re: PTR not working...

2009-08-06 Thread Justin Pryzby
On Thu, Aug 06, 2009 at 05:00:59PM -0400, Alexandre Racine wrote: > @Justin, you mean like a 3rd DNS server? I was thinking about that > since one recent RFC recommend that 3 DNS servers within 3 networks > should be present (primary, secondary, and third). Not for the same reason as having 2 or 3

Re: PTR not working...

2009-08-06 Thread Breno Silveira Soares
You have to configure your named.conf on servers ns{11,12}.bgrinformatique.com with zone "80-28.115.25.70.in-addr.arpa" IN {     type master;     file "master/db.80-28.115.25.70.in-addr.arpa"; }; An your zone file master/db.80-28.115.25.70.in-addr.arpa with: 80-28.115.25.70.in-addr

RE: PTR not working...

2009-08-06 Thread Alexandre Racine
d'origine- De : bind-users-boun...@lists.isc.org [mailto:bind-users-boun...@lists.isc.org] De la part de Kevin Darcy Envoyé : 6 août 2009 16:06 À : bind-users@lists.isc.org Objet : Re: PTR not working... What you have would only work if you had the whole 70.25.115.0/24 and Bell C

Re: PTR not working...

2009-08-06 Thread Justin Pryzby
On Thu, Aug 06, 2009 at 04:06:23PM -0400, Kevin Darcy wrote: > For good measure, you should probably also set yourself up to slave > 25.70.in-addr.arpa from Bell Canada so that you can still resolve your > own PTRs even if your link is down. And (per rfc) ask if Bell will slave your delegated z

Re: PTR not working...

2009-08-06 Thread Dan Farrell
On Thu, 6 Aug 2009 13:03:58 -0700 Daniel Ballenger wrote: > I could be blind, but I don't see the PTR record for that IP in the > zone file you pasted. Isn't this it? > On Thu, Aug 6, 2009 at 12:52 PM, Alexandre > Racine wrote: >> [...] >> 82.115.25.70.in-addr.arpa. IN PTR mail.bgrinformatiqu

Re: PTR not working...

2009-08-06 Thread Jeff Reasoner
The in-addr.arpa zone does not appear to be delegated to you. You'll either need to get that done, or have Bell Canada do it. dig +trace 80.115.25.70.in-addr.arpa ; <<>> DiG 9.4.3 <<>> +trace 80.115.25.70.in-addr.arpa ;; global options: printcmd . 513811 IN NS i.

Re: PTR not working...

2009-08-06 Thread Kevin Darcy
What you have would only work if you had the whole 70.25.115.0/24 and Bell Canada delegated all of 115.25.70.in-addr.arpa to you. But, it looks like you only have a /28 and Bell Canada is following some sort of RFC 2317 convention: ;; ANSWER SECTION: 82.115.25.70.in-addr.arpa. 86400 IN CNAME

Re: PTR not working...

2009-08-06 Thread Daniel Ballenger
On Thu, Aug 6, 2009 at 12:52 PM, Alexandre Racine wrote: > “No PTR records exist for 70.25.115.82. [Neg TTL=38400 seconds]” I could be blind, but I don't see the PTR record for that IP in the zone file you pasted. >    38400 ) > > 115.25.70.in-addr.arpa.

PTR not working...

2009-08-06 Thread Alexandre Racine
Hi all, I am trying to make my PTR work and it does not. Testing it with dnsstuff and other tools simply say that there are no records "No PTR records exist for 70.25.115.82. [Neg TTL=38400 seconds]" Looking up my config, I have this below. Is there something wrong? My other zones are working c