Date: Mon, 28 Mar 2011 23:36:52 -0400 From: Tim Dunphy <bluethundr@gmail.com> To: freebsd-questions@freebsd.org Subject: Re: reverse dns in bind9 Message-ID: <AANLkTimVuSLaNKrQSSL29UnG2T2jD6z94D21LtTNTWTF@mail.gmail.com> In-Reply-To: <AANLkTinUU=jtWSW1vaTtSS=V7wy08hinL5GF1GF7dkTX@mail.gmail.com> References: <AANLkTik9mnTd_h7Yz7XBK8zpLcdoGjxyMHqfHJv1TVno@mail.gmail.com> <201103280506.p2S56S5i052834@mail.r-bonomi.com> <AANLkTim7qBzqFyaYHLn0stb7omimakU9mU_9Gg8eNU4n@mail.gmail.com> <AANLkTikU7AYiQMCjhaJ0noSf6cbiVGdz59Hny-X1c5Sy@mail.gmail.com> <AANLkTinUU=jtWSW1vaTtSS=V7wy08hinL5GF1GF7dkTX@mail.gmail.com>
next in thread | previous in thread | raw e-mail | index | archive | help
hello list,
I was able to make that correction:
zone "1.168.192.in-addr.arpa" { type master; file "master/summitnjhome-reve=
rse.d
b"; };
zone "summitnjhome.com" { type master; file "master/summitnjhome.db"; };
is now in named.conf. otherwise named.conf is identical to the way it
is higher up in the thread, and summitnjhome-reverse.db is untouched.
But as of now, forward lookups work, but reverse time out:
LBSD2# host sum1
sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
LCENT01.summitnjhome.com has address 192.168.1.42
LBSD2# nslookup sum1
Server: 192.168.1.44
Address: 192.168.1.44#53
sum1.summitnjhome.com canonical name =3D LCENT01.summitnjhome.com.
Name: LCENT01.summitnjhome.com
Address: 192.168.1.42
LBSD2# host 192.168.1.42
;; connection timed out; no servers could be reached
LBSD2# nslookup 192.168.1.42
;; Got SERVFAIL reply from 192.168.1.44, trying next server
;; connection timed out; no servers could be reached
Now I could probably understand it FAILING due to perhaps a type-o in
the config. But I am genuinely curious as to how forward lookups will
work and reverse lookups time out.
regards
tim
On Mon, Mar 28, 2011 at 9:36 AM, Tim Dunphy <bluethundr@gmail.com> wrote:
> Ok guys.. I totally get it now and sorry for the misunderstanding. I'm
> really looking forward to getting this working but might not get a
> chance to try this again until this evening. time. where does it go?
> don't know but I certainly appreciate yourst!
>
> On Mon, Mar 28, 2011 at 8:01 AM, Peter Andreev <andreev.peter@gmail.com> =
wrote:
>> 2011/3/28 Tim Dunphy <bluethundr@gmail.com>
>>
>>> Hello,
>>>
>>> =A0Thanks for your reply!
>>>
>>> =A0I took your advice and removed that line from resolv.conf and added
>>> it into /etc/named/named.conf
>>>
>>> =A0Now it looks like this
>>>
>>> =A0// RFC 1912
>>> zone "localhost" =A0 =A0 =A0 =A0{ type master; file "master/localhost-f=
orward.db";
>>> };
>>> zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.d=
b";
>>> };
>>> zone "255.in-addr.arpa" { type master; file "master/empty.db"; };
>>> zone "192.in-addr.arpa" { type master; file
>>> "master/summitjnhome-reverse.db"; };
>>>
>>
>> Robert said that you should replace 192.in-addr.arpa with
>> 1.168.192.in-addr.arpa in your named.conf.
>>
>> Your named.conf should be look like the following:
>>
>> zone "localhost" =A0 =A0 =A0 =A0{ type master; file "master/localhost-fo=
rward.db";
>> };
>> zone "127.in-addr.arpa" { type master; file "master/localhost-reverse.db=
";
>> };
>> zone "255.in-addr.arpa" { type master; file "master/empty.db"; };
>> zone "1.168.192.in-addr.arpa" { type master; file
>> "master/summitjnhome-reverse.db"; };
>>
>>
>>
>>> =A0And I did a restart of both network and named but the issue remains:
>>>
>>>
>>> LBSD2# host 192.168.1.44
>>> Host 44.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
>>>
>>>
>>> On Mon, Mar 28, 2011 at 1:06 AM, Robert Bonomi <bonomi@mail.r-bonomi.co=
m>
>>> wrote:
>>> >
>>> >> Date: Mon, 28 Mar 2011 00:19:26 -0400
>>> >> From: Tim Dunphy <bluethundr@gmail.com>
>>> >> Subject: reverse dns in bind9
>>> >>
>>> >> Hello,
>>> >>
>>> >> =A0I am attempting to setup reverse dns in bind 9 under freebsd... t=
his is
>>> >> =A0in an attempt to allow mysql to work a little easier with DNS
>>> >> =A0resolution.
>>> >>
>>> >> =A0In my /etc/named/named.conf file I have the following:
>>> >>
>>> >> // RFC 1912
>>> >> zone "localhost" =A0{ type master; file "master/localhost-forward.db=
"; };
>>> >> zone "127.in-addr.arpa" { type master; ile
>>> "master/localhost-reverse.db"; };
>>> >> zone "255.in-addr.arpa" { type master; file "master/empty.db"; };
>>> >> zone "192.in-addr.arpa" { type master; file
>>> "master/summitjnhome-reverse.db"; };
>>> >> zone "summitnjhome.com" { type master; file "master/summitnjhome.db"=
;
>>> };
>>> >>
>>> >>
>>> >> My master/summitnjhome.com looks like the following:
>>> >
>>> > For starters, this should be in "master/summitnjhome-reerse.db"
>>> >>
>>> >> $TTL 3D
>>> >> @ =A0 =A0 =A0 IN =A0 =A0 =A0SOA =A0 =A0 ns1.summitnjhome.com. blueth=
undr.gmail.com. (
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 201103271 ; Serial, =
todays date + todays serial
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 8H =A0 =A0 =A0; Refr=
esh
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 2H =A0 =A0 =A0; Retr=
y
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 4W =A0 =A0 =A0; Expi=
re
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 1D) =A0 =A0 ; Minimu=
m TTL
>>> >> =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 =A0 NS =A0 =A0 =A0ns1.su=
mmitnjhome.com.
>>> >>
>>> >> summitnjhome.com.
>>> >> 42 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LCENT01.summitnjhome.com.
>>> >> 43 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LCENT02.summitnjhome.com.
>>> >> 44 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LBSD2.summitnjhome.com.
>>> >> 45 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LCENT02.summitnjhome.com.
>>> >> 46 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LCENT03.summitnjhome.com.
>>> >> 47 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 LCENT04.summitnjhome.com.
>>> >> 23 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent01.summitnjhome.c=
om.
>>> >> 24 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent02.summitnjhome.c=
om.
>>> >> 21 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent03.summitnjhome.c=
om.
>>> >> 26 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent04.summitnjhome.c=
om.
>>> >> 27 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent05.summitnjhome.c=
om.
>>> >> 28 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent06.summitnjhome.c=
om.
>>> >> 29 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent07.summitnjhome.c=
om.
>>> >> 30 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent08.summitnjhome.c=
om.
>>> >> 31 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent09.summitnjhome.c=
om.
>>> >> 32 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent10.summitnjhome.c=
om.
>>> >> 33 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent11.summitnjhome.c=
om.
>>> >> 34 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent12.summitnjhome.c=
om.
>>> >> 35 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent13.summitnjhome.c=
om.
>>> >> 36 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent14.summitnjhome.c=
om.
>>> >> 37 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent15.summitnjhome.c=
om.
>>> >> 38 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent16.summitnjhome.c=
om.
>>> >> 39 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent17.summitnjhome.c=
om.
>>> >> 40 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent18.summitnjhome.c=
om.
>>> >> 41 =A0 =A0 =A0 =A0 =A0 =A0 =A0 PTR =A0 =A0 virtcent19.summitnjhome.c=
om.
>>> >>
>>> >>
>>> >> and my /etc/resolv.conf looks like this:
>>> >>
>>> >> domain =A0summitnjhome.com
>>> >> nameserver =A0 =A0 192.168.1.44
>>> >> nameserver =A0 =A0 4.2.2.2
>>> >>
>>> >> zone "1.168.192.in-addr.arpa" { type master; file
>>> >> "/etc/named/master/summitnjhome-reverse.db"
>>> >> };
>>> >
>>> > the 'zone' line =A0you show should *NOT* be in resolv.conf at all.
>>> > this line should be in the =A0named.conf file *instead* of the one fo=
r
>>> > the '192.in-addr.arpa' zone.
>>> >
>>> >> then I restart both named and the network service
>>> >>
>>> >> and yet if I were to try forward resolution:
>>> >>
>>> >> LBSD2# host sum1
>>> >> sum1.summitnjhome.com is an alias for LCENT01.summitnjhome.com.
>>> >> LCENT01.summitnjhome.com has address 192.168.1.42
>>> >>
>>> >>
>>> >> and then reverse resolution:
>>> >>
>>> >> LBSD2# host 192.168.1.42
>>> >> Host 42.1.168.192.in-addr.arpa. not found: 3(NXDOMAIN)
>>> >>
>>> >> I have no luck. Any thoughts on this?
>>> >
>>> > see above.
>>> >
>>> >
>>> >
>>> >
>>>
>>>
>>>
>>> --
>>> GPG me!!
>>>
>>> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>>> _______________________________________________
>>> freebsd-questions@freebsd.org mailing list
>>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>>> To unsubscribe, send any mail to "
>>> freebsd-questions-unsubscribe@freebsd.org"
>>>
>>
>>
>>
>> --
>> --
>> AP
>> _______________________________________________
>> freebsd-questions@freebsd.org mailing list
>> http://lists.freebsd.org/mailman/listinfo/freebsd-questions
>> To unsubscribe, send any mail to "freebsd-questions-unsubscribe@freebsd.=
org"
>>
>
>
>
> --
> GPG me!!
>
> gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
>
--=20
GPG me!!
gpg --keyserver pool.sks-keyservers.net --recv-keys F186197B
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?AANLkTimVuSLaNKrQSSL29UnG2T2jD6z94D21LtTNTWTF>