Avatar of George R. Kasica
George R. Kasica
Flag for United States of America asked on

RDNS File not loading with Out of range and NS and SOA Errors

Trying to get RDNS working on an Ubuntu 20.04LTS system. the files goes through named-checkzone just fine.

root@ntp1:/etc/bind/zones# ll
total 60
-rw-r--r-- 1 root bind  2377 Dec 27 20:56 db.224-27.25.49.47.in-addr.arpa -rw-r--r-- 1 root bind  4008 Dec 27 19:27 db.netwrx1.com -rw-r--r-- 1 root bind  1543 Dec 27 19:28 db.netwrx1.net -rw-r--r-- 1 root bind  2049 Dec 27 19:28 db.netwrx1.org -rwxr-xr-x 1 root bind 40108 Nov 20  2009 mkrdns-3_3 root@ntp1:/etc/bind/zones# named-checkzone 25.49.47.in-addr.arpa /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa zone 25.49.47.in-addr.arpa/IN: loaded serial 2021122701 OK When I try to load it into the program when I start the services I get these errors. I've looked at the syntax, done dos2unix to clean up the files, and converted all TABs to spaces in notepad++. I'm stumped. Dec 27 21:44:29 ntp1 named[5162]: listening on IPv4 interface eth0, 47.49.25.35#53
Dec 27 21:44:29 ntp1 named[5162]: generating session key for dynamic DNS
Dec 27 21:44:29 ntp1 named[5162]: sizing zone task pool based on 9 zones Dec 27 21:44:29 ntp1 named[5162]: none:106: 'max-cache-size 90%' - setting to 387MB (out of 430MB) Dec 27 21:44:29 ntp1 named[5162]: obtaining root key for view _default from '/etc/bind/bind.keys' Dec 27 21:44:29 ntp1 named[5162]: set up managed keys zone for view _default, file 'managed-keys.bind' Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 10.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 16.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 17.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 18.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 19.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 20.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 21.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 22.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 23.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 24.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 25.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 26.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 27.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 28.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 29.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 30.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 31.172.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 168.192.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 64.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 65.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 66.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 67.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 68.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 69.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 70.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 71.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 72.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 73.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 74.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 75.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 76.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 77.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 78.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 79.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 80.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 81.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 82.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 83.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 84.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 85.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 86.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 87.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 88.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 89.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 90.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 91.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 92.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 93.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 94.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 95.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 96.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 97.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 98.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 99.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 100.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 101.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 102.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 103.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 104.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 105.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 106.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 107.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 108.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 109.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 110.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 111.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 112.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 113.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 114.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 115.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 116.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 117.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 118.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 119.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 120.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 121.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 122.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 123.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 124.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 125.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 126.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 127.100.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 254.169.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 2.0.192.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 100.51.198.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 113.0.203.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 255.255.255.255.IN-ADDR.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: D.F.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 8.E.F.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 9.E.F.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: A.E.F.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: B.E.F.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: 8.B.D.0.1.0.0.2.IP6.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: EMPTY.AS112.ARPA Dec 27 21:44:29 ntp1 named[5162]: automatic empty zone: HOME.ARPA Dec 27 21:44:29 ntp1 named[5162]: none:106: 'max-cache-size 90%' - setting to 387MB (out of 430MB) Dec 27 21:44:29 ntp1 named[5162]: configuring command channel from '/etc/bind/rndc.key' Dec 27 21:44:29 ntp1 named[5162]: command channel listening on 127.0.0.1#953 Dec 27 21:44:29 ntp1 named[5162]: managed-keys-zone: journal file is out of date: removing journal file Dec 27 21:44:29 ntp1 named[5162]: managed-keys-zone: loaded serial 759 Dec 27 21:44:29 ntp1 named[5162]: zone 0.in-addr.arpa/IN: loaded serial 1 Dec 27 21:44:29 ntp1 named[5162]: zone localhost/IN: loaded serial 2 Dec 27 21:44:29 ntp1 named[5162]: zone 127.in-addr.arpa/IN: loaded serial 1 Dec 27 21:44:29 ntp1 named[5162]: zone 255.in-addr.arpa/IN: loaded serial 1 Dec 27 21:44:29 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:2: ignoring out-of-zone data (25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:13: ignoring out-of-zone data (34.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:14: ignoring out-of-zone data (35.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:15: ignoring out-of-zone data (36.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:16: ignoring out-of-zone data (37.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:17: ignoring out-of-zone data (38.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:18: ignoring out-of-zone data (39.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:19: ignoring out-of-zone data (40.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:20: ignoring out-of-zone data (41.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:21: ignoring out-of-zone data (42.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:22: ignoring out-of-zone data (43.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:23: ignoring out-of-zone data (44.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:24: ignoring out-of-zone data (45.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:25: ignoring out-of-zone data (46.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:26: ignoring out-of-zone data (47.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:27: ignoring out-of-zone data (48.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:28: ignoring out-of-zone data (49.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:29: ignoring out-of-zone data (50.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:30: ignoring out-of-zone data (51.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:31: ignoring out-of-zone data (52.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:32: ignoring out-of-zone data (53.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:33: ignoring out-of-zone data (54.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:34: ignoring out-of-zone data (55.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:35: ignoring out-of-zone data (56.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:36: ignoring out-of-zone data (57.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:37: ignoring out-of-zone data (58.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:38: ignoring out-of-zone data (59.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:39: ignoring out-of-zone data (60.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:40: ignoring out-of-zone data (61.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: /etc/bind/zones/db.224-27.25.49.47.in-addr.arpa:41: ignoring out-of-zone data (62.25.49.47.in-addr.arpa) Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: has 0 SOA records Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: has no NS records Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: not loaded due to errors. Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.org/IN: loaded serial 2021121901 Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.com/IN: loaded serial 2021121901 Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.net/IN: loaded serial 2021121901 Dec 27 21:44:30 ntp1 named[5162]: all zones loaded Dec 27 21:44:30 ntp1 named[5162]: running Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.net/IN: sending notifies (serial 2021121901) Dec 27 21:44:30 ntp1 systemd[1]: Started BIND Domain Name Server. Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.org/IN: sending notifies (serial 2021121901) Dec 27 21:44:30 ntp1 named[5162]: zone netwrx1.com/IN: sending notifies (serial 2021121901) Dec 27 21:44:30 ntp1 named[5162]: managed-keys-zone: Key 20326 for zone . acceptance timer complete: key now trusted Dec 27 21:44:30 ntp1 named[5162]: resolver priming query complete Dec 27 21:44:30 ntp1 named[5162]: checkhints: b.root-servers.net/A (199.9.14.201) missing from hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: b.root-servers.net/A (192.228.79.201) extra record in hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: h.root-servers.net/A (198.97.190.53) missing from hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: h.root-servers.net/A (128.63.2.53) extra record in hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: h.root-servers.net/AAAA (2001:500:1::53) missing from hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: h.root-servers.net/AAAA (2001:500:1::803f:235) extra record in hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: l.root-servers.net/AAAA (2001:500:9f::42) missing from hints Dec 27 21:44:30 ntp1 named[5162]: checkhints: l.root-servers.net/AAAA (2001:500:3::42) extra record in hints What am I doing wrong here? I'm stumped

Open in new window

UbuntuDNSLinuxLinux OS DevLinux Distributions

Avatar of undefined
Last Comment
George R. Kasica

8/22/2022 - Mon
David Favor

Unless you own the IP, you can't set a PTR record (if that's what you mean by RDNS).

You'll contact your hosting or provisioning company to set PTR records... as all PTR records are out of zone/range... unless you actually own the all PTR record IP ranges you're attempting to set... which is doubtful...
George R. Kasica

ASKER
Zone File attached

Spectrum is delegating the forward and reverse DNS - yes PTR records to me so in effect I guess I own them for as long as I’m a Spectrum  customer.
Duncan Roe

I don't see any attached zone file. The errors look genuine to me, e.g. 2nd error
34.25.49.47 does not belong in
27.25.49.47 zone file.
Your help has saved me hundreds of hours of internet surfing.
fblack61
Craig Beck

I'd start here...

Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: has 0 SOA records
Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: has no NS records
Dec 27 21:44:30 ntp1 named[5162]: zone db.224-27.25.49.47.in-addr.arpa/IN: not loaded due to errors.

Open in new window


George R. Kasica

ASKER
here's what spectrum allocated me 47.49.25.32/27. I'll get the zone file up once I get to my notebook can't attach in the app. I was sure I attached it earlier.
George R. Kasica

ASKER
Duncan what should the file name be?
⚡ FREE TRIAL OFFER
Try out a week of full access for free.
Find out why thousands trust the EE community with their toughest problems.
George R. Kasica

ASKER
Here's the Zone file. Also Craig thats the issue I'm trying to fix. Zone file attached.
db.224-32.25.49.47.in-addr.arpa
Craig Beck

What's in named.conf?
ASKER CERTIFIED SOLUTION
Craig Beck

THIS SOLUTION ONLY AVAILABLE TO MEMBERS.
View this solution by signing up for a free trial.
Members can start a 7-Day free trial and enjoy unlimited access to the platform.
See Pricing Options
Start Free Trial
GET A PERSONALIZED SOLUTION
Ask your own question & get feedback from real experts
Find out why thousands trust the EE community with their toughest problems.
George R. Kasica

ASKER
Craig:

Here's named.conf and what's included in it.

The zone file above worked perfectly and the primary and 2 slaves are up and running. What did I have wrong in my version? I looked and I don't see what I missed.
named.conf
named.conf.options
named.conf.local
named.conf.default-zones
All of life is about relationships, and EE has made a viirtual community a real community. It lifts everyone's boat
William Peck
Craig Beck

You had TTLs configured instead of IN for most of your entries.
George R. Kasica

ASKER
oops.