Re: reverse dns in bind9
hey guys, ok I fixed the reverse zone file and now it's working perfectly! @ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. ( 2011032901 ;serial 14400 ;refresh 3600 ;retry 604800 ;expire 10800;minimum ) 1.168.192.in-addr.arpa.IN NS ns1.yournameserver.com. 42 IN PTR LCENT01.summitnjhome.com. 43 IN PTR LCENT03.summitnjhome.com. 44 IN PTR LBSD2.summitnjhome.com. LBSD2# host 192.168.1.42 42.1.168.192.in-addr.arpa domain name pointer LCENT01.summitnjhome.com. On Tue, Mar 29, 2011 at 12:25 AM, Jon Radel j...@radel.com wrote: On 3/29/11 12:05 AM, Tim Dunphy wrote: hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file Really? Judging from the line numbers in the log messages, you're missing about 3 lines that, I would hope, include something like IN SOA ns1.summitnjhome.com bluethunder.gmail.com ( 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. doesn't make much sense as data in this zone, error message 1 ^ Whoa, Nelly, where's the rest of this line? error message 2 Oh, never mind, I'm so out of here.ignore all that stuff below, messages 3 and 4 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. -- --Jon Radel j...@radel.com -- 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-unsubscr...@freebsd.org
Re: reverse dns in bind9
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.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 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db; };
And 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 bon...@mail.r-bonomi.com wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { 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
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
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-unsubscr...@freebsd.org
Re: reverse dns in bind9
On 3/28/11 7:21 AM, Tim Dunphy wrote:
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.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 192.in-addr.arpa { type master; file master/summitjnhome-reverse.db; };
And 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)
Nowhere do you mention that you moved all the PTR records into the
192.in-addr.arpa zone where they belong, as noted by Robert Bonomi. And
why did you change
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
to
zone 192.in-addr.arpa { type master; file
master/summitjnhome-reverse.db; };
when your PTR lines only give the last octet? Where do you expect the
168.1 to come from?
--Jon Radel
j...@radel.com
Re: reverse dns in bind9
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost{ type master; file master/localhost-forward.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 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{ type master; file master/localhost-forward.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; };
And 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 bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { 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
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
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-unsubscr...@freebsd.org
--
--
AP
Re: reverse dns in bind9
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.pe...@gmail.com wrote:
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost { type master; file master/localhost-forward.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 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 { type master; file master/localhost-forward.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; };
And 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 bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { 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
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
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
Re: reverse dns in bind9
hello list,
I was able to make that correction:
zone 1.168.192.in-addr.arpa { type master; file master/summitnjhome-reverse.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 = 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 bluethu...@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.pe...@gmail.com
wrote:
2011/3/28 Tim Dunphy bluethu...@gmail.com
Hello,
Thanks for your reply!
I took your advice and removed that line from resolv.conf and added
it into /etc/named/named.conf
Now it looks like this
// RFC 1912
zone localhost { type master; file master/localhost-forward.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 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 { type master; file master/localhost-forward.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; };
And 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 bon...@mail.r-bonomi.com
wrote:
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { 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
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR
Re: reverse dns in bind9
On 3/28/11 11:36 PM, Tim Dunphy wrote: 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. I would expect them to time out if your dns server knows nothing about the reverse zone; give or take how you connect to the rest of the DNS. What messages about zones loading did you get when you restarted bind? Where there any crabby comments in the log file about not loading master/summitnjhome-reverse.db due to error(s)? Was that file mentioned at all? --Jon Radel j...@radel.com
Re: reverse dns in bind9
hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. tim On Mon, Mar 28, 2011 at 11:54 PM, Jon Radel j...@radel.com wrote: On 3/28/11 11:36 PM, Tim Dunphy wrote: 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. I would expect them to time out if your dns server knows nothing about the reverse zone; give or take how you connect to the rest of the DNS. What messages about zones loading did you get when you restarted bind? Where there any crabby comments in the log file about not loading master/summitnjhome-reverse.db due to error(s)? Was that file mentioned at all? --Jon Radel j...@radel.com -- 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-unsubscr...@freebsd.org
Re: reverse dns in bind9
On 3/29/11 12:05 AM, Tim Dunphy wrote: hello no crabby comments on restart at all! LBSD2# /etc/rc.d/named restart Stopping named. Waiting for PIDS: 4970. Starting named. Ah but yes some complaints from the logs Mar 29 04:59:47 LBSD2 named[5469]: master/summitnjhome-reverse.db:10: ignoring out-of-zone data (summitnjhome.com) Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:11: unexpected end of line Mar 29 04:59:47 LBSD2 named[5469]: dns_master_load: master/summitnjhome-reverse.db:10: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: loading from master file master/summitnjhome-reverse.db failed: unexpected end of input Mar 29 04:59:47 LBSD2 named[5469]: zone 1.168.192.in-addr.arpa/IN: not loaded due to errors. Mar 29 04:59:47 LBSD2 named[5469]: running Tho I am not sure why it's complaining about unexpected end of input this is the whole file Really? Judging from the line numbers in the log messages, you're missing about 3 lines that, I would hope, include something like IN SOA ns1.summitnjhome.com bluethunder.gmail.com ( 201103271 ; Serial, todays date + todays serial 8H ; Refresh 2H ; Retry 4W ; Expire 1D) ; Minimum TTL NS ns1.summitnjhome.com. summitnjhome.com. doesn't make much sense as data in this zone, error message 1 ^ Whoa, Nelly, where's the rest of this line? error message 2 Oh, never mind, I'm so out of here.ignore all that stuff below, messages 3 and 4 42 PTR LCENT01.summitnjhome.com. 43 PTR LCENT02.summitnjhome.com. 44 PTR LBSD2.summitnjhome.com. 45 PTR LCENT02.summitnjhome.com. 46 PTR LCENT03.summitnjhome.com. 47 PTR LCENT04.summitnjhome.com. 23 PTR virtcent01.summitnjhome.com. 24 PTR virtcent02.summitnjhome.com. 21 PTR virtcent03.summitnjhome.com. 26 PTR virtcent04.summitnjhome.com. 27 PTR virtcent05.summitnjhome.com. 28 PTR virtcent06.summitnjhome.com. 29 PTR virtcent07.summitnjhome.com. 30 PTR virtcent08.summitnjhome.com. 31 PTR virtcent09.summitnjhome.com. 32 PTR virtcent10.summitnjhome.com. 33 PTR virtcent11.summitnjhome.com. 34 PTR virtcent12.summitnjhome.com. 35 PTR virtcent13.summitnjhome.com. 36 PTR virtcent14.summitnjhome.com. 37 PTR virtcent15.summitnjhome.com. 38 PTR virtcent16.summitnjhome.com. 39 PTR virtcent17.summitnjhome.com. 40 PTR virtcent18.summitnjhome.com. 41 PTR virtcent19.summitnjhome.com. -- --Jon Radel j...@radel.com
reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this
is in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost{ type master; file master/localhost-forward.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 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:
$TTL 3D
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa {
type master;
file /etc/named/master/summitnjhome-reverse.db
};
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?
thanks!
--
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-unsubscr...@freebsd.org
Re: reverse dns in bind9
Date: Mon, 28 Mar 2011 00:19:26 -0400
From: Tim Dunphy bluethu...@gmail.com
Subject: reverse dns in bind9
Hello,
I am attempting to setup reverse dns in bind 9 under freebsd... this is
in an attempt to allow mysql to work a little easier with DNS
resolution.
In my /etc/named/named.conf file I have the following:
// RFC 1912
zone localhost { 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
@ IN SOA ns1.summitnjhome.com. bluethundr.gmail.com. (
201103271 ; Serial, todays date + todays serial
8H ; Refresh
2H ; Retry
4W ; Expire
1D) ; Minimum TTL
NS ns1.summitnjhome.com.
summitnjhome.com.
42 PTR LCENT01.summitnjhome.com.
43 PTR LCENT02.summitnjhome.com.
44 PTR LBSD2.summitnjhome.com.
45 PTR LCENT02.summitnjhome.com.
46 PTR LCENT03.summitnjhome.com.
47 PTR LCENT04.summitnjhome.com.
23 PTR virtcent01.summitnjhome.com.
24 PTR virtcent02.summitnjhome.com.
21 PTR virtcent03.summitnjhome.com.
26 PTR virtcent04.summitnjhome.com.
27 PTR virtcent05.summitnjhome.com.
28 PTR virtcent06.summitnjhome.com.
29 PTR virtcent07.summitnjhome.com.
30 PTR virtcent08.summitnjhome.com.
31 PTR virtcent09.summitnjhome.com.
32 PTR virtcent10.summitnjhome.com.
33 PTR virtcent11.summitnjhome.com.
34 PTR virtcent12.summitnjhome.com.
35 PTR virtcent13.summitnjhome.com.
36 PTR virtcent14.summitnjhome.com.
37 PTR virtcent15.summitnjhome.com.
38 PTR virtcent16.summitnjhome.com.
39 PTR virtcent17.summitnjhome.com.
40 PTR virtcent18.summitnjhome.com.
41 PTR virtcent19.summitnjhome.com.
and my /etc/resolv.conf looks like this:
domain summitnjhome.com
nameserver 192.168.1.44
nameserver 4.2.2.2
zone 1.168.192.in-addr.arpa { type master; file
/etc/named/master/summitnjhome-reverse.db
};
the 'zone' line you show should *NOT* be in resolv.conf at all.
this line should be in the named.conf file *instead* of the one for
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.
___
freebsd-questions@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to freebsd-questions-unsubscr...@freebsd.org
