|
Home > Archive > Red Hat Configuration > March 2004 > Re: dhcp won't updated dns tables, RHEL, ES
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: dhcp won't updated dns tables, RHEL, ES
|
|
| Knute Snortum 2004-03-08, 1:35 pm |
|
"Nils O. Selåsdal" <noselasd@frisurf.no> wrote in message
news:slrnc4ob01.cg4.noselasd@utelsystems.dyndns.org...
> In article <yKP2c.85572$C65.32306@nwrddc01.gnilink.net>, Knute Snortum
wrote:
> Might be an indication the shared seckrets between dhcpd and named are
> wrong ?
*blush* That was indeed the case; not all the secret codes matched!
But even after I fixed that and the A and PTR records were being updated in
db.localhost, nothing is being updated in db.127.0.0. and "ping client_name"
still doesn't work.
This message is /var/log/messages intrigued me:
Mar 8 09:39:56 aon3 named[14238]: client 127.0.0.1#35117: updating zone
'somewhere.com/IN': update failed: 'name not in use' prerequisite not
satisfied (YXDOMAIN)
What's the 'name not in use' prerequisite?
Here's part of /var/log/messages:
***start messages
Mar 8 09:38:43 aon3 named[14238]: command channel listening on
127.0.0.1#953
Mar 8 09:38:43 aon3 named[14238]: zone 0.0.127.in-addr.arpa/IN: loaded
serial 2
Mar 8 09:38:43 aon3 named[14238]: zone somewhere.com/IN: loaded serial 99
Mar 8 09:38:43 aon3 named[14238]: running
Mar 8 09:38:43 aon3 named: named startup succeeded
Mar 8 09:38:50 aon3 dhcpd: dhcpd shutdown failed
Mar 8 09:38:50 aon3 dhcpd: Internet Software Consortium DHCP Server V3.0pl2
Mar 8 09:38:50 aon3 dhcpd: Copyright 1995-2003 Internet Software
Consortium.
Mar 8 09:38:50 aon3 dhcpd: All rights reserved.
Mar 8 09:38:50 aon3 dhcpd: For info, please visit
http://www.isc.org/products/DHCP
Mar 8 09:38:50 aon3 dhcpd: Internet Software Consortium DHCP Server V3.0pl2
Mar 8 09:38:50 aon3 dhcpd: Copyright 1995-2003 Internet Software
Consortium.
Mar 8 09:38:50 aon3 dhcpd: All rights reserved.
Mar 8 09:38:50 aon3 dhcpd: For info, please visit
http://www.isc.org/products/DHCP
Mar 8 09:38:50 aon3 dhcpd: Wrote 16 leases to leases file.
Mar 8 09:38:50 aon3 dhcpd: Wrote 16 leases to leases file.
Mar 8 09:38:50 aon3 dhcpd: Listening on
LPF/eth0/00:c0:9f:35:42:eb/192.168.197.0/24
Mar 8 09:38:50 aon3 dhcpd: Sending on
LPF/eth0/00:c0:9f:35:42:eb/192.168.197.0/24
Mar 8 09:38:50 aon3 dhcpd: Sending on Socket/fallback/fallback-net
Mar 8 09:38:50 aon3 dhcpd: Listening on
LPF/eth0/00:c0:9f:35:42:eb/192.168.197.0/24
Mar 8 09:38:50 aon3 dhcpd: Sending on
LPF/eth0/00:c0:9f:35:42:eb/192.168.197.0/24
Mar 8 09:38:50 aon3 dhcpd: Sending on Socket/fallback/fallback-net
Mar 8 09:38:50 aon3 dhcpd: dhcpd startup succeeded
Mar 8 09:39:55 aon3 dhcpd: DHCPDISCOVER from 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:39:56 aon3 dhcpd: DHCPOFFER on 192.168.197.184 to
00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:39:56 aon3 named[14238]: client 127.0.0.1#35117: updating zone
'somewhere.com/IN': update failed: 'name not in use' prerequisite not
satisfied (YXDOMAIN)
Mar 8 09:39:56 aon3 dhcpd: if IN A dell-3500xp.somewhere.com domain doesn't
exist add 300 IN A dell-3500xp.somewhere.com 192.168.197.184 add 300 IN TXT
dell-3500xp.somewhere.com "3127d023c94da9531f758dc03082e79b3b": domain
already exists.
Mar 8 09:39:56 aon3 named[14238]: client 127.0.0.1#35117: updating zone
'somewhere.com/IN': deleting an rrset
Mar 8 09:39:56 aon3 named[14238]: client 127.0.0.1#35117: updating zone
'somewhere.com/IN': adding an RR
Mar 8 09:39:56 aon3 dhcpd: if IN TXT dell-3500xp.somewhere.com
"3127d023c94da9531f758dc03082e79b3b" rrset exists delete IN A
dell-3500xp.somewhere.com add 300 IN A dell-3500xp.somewhere.com
192.168.197.184: success.
Mar 8 09:39:58 aon3 dhcpd: delete IN PTR 184.197.168.192.in-addr.arpa. add
300 IN PTR 184.197.168.192.in-addr.arpa. dell-3500xp.somewhere.com: timed
out.
Mar 8 09:39:58 aon3 dhcpd: DHCPREQUEST for 192.168.197.184
(192.168.197.203) from 00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:39:58 aon3 dhcpd: DHCPACK on 192.168.197.184 to 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:42:01 aon3 named[14238]: client 127.0.0.1#35122: updating zone
'somewhere.com/IN': deleting an RR
Mar 8 09:42:01 aon3 dhcpd: if IN TXT dell-3500xp.somewhere.com
"3127d023c94da9531f758dc03082e79b3b" rrset exists and IN A
dell-3500xp.somewhere.com 192.168.197.184 rrset exists delete IN A
dell-3500xp.somewhere.com 192.168.197.184: success.
Mar 8 09:42:01 aon3 named[14238]: client 127.0.0.1#35122: updating zone
'somewhere.com/IN': deleting an RR
Mar 8 09:42:01 aon3 dhcpd: if IN A dell-3500xp.somewhere.com rrset doesn't
exist delete IN TXT dell-3500xp.somewhere.com
"3127d023c94da9531f758dc03082e79b3b": success.
Mar 8 09:42:01 aon3 dhcpd: DHCPRELEASE of 192.168.197.184 from
00:50:04:5c:5c:bb (dell-3500xp) via eth0 (found)
Mar 8 09:42:08 aon3 dhcpd: DHCPDISCOVER from 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:42:09 aon3 dhcpd: DHCPOFFER on 192.168.197.184 to
00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:42:09 aon3 named[14238]: client 127.0.0.1#35122: updating zone
'somewhere.com/IN': adding an RR
Mar 8 09:42:09 aon3 named[14238]: client 127.0.0.1#35122: updating zone
'somewhere.com/IN': adding an RR
Mar 8 09:42:09 aon3 dhcpd: if IN A dell-3500xp.somewhere.com domain doesn't
exist add 300 IN A dell-3500xp.somewhere.com 192.168.197.184 add 300 IN TXT
dell-3500xp.somewhere.com "3127d023c94da9531f758dc03082e79b3b": success.
Mar 8 09:42:11 aon3 dhcpd: delete IN PTR 184.197.168.192.in-addr.arpa. add
300 IN PTR 184.197.168.192.in-addr.arpa. dell-3500xp.somewhere.com: timed
out.
Mar 8 09:42:11 aon3 dhcpd: DHCPREQUEST for 192.168.197.184
(192.168.197.203) from 00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:42:11 aon3 dhcpd: DHCPACK on 192.168.197.184 to 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:47:11 aon3 dhcpd: DHCPREQUEST for 192.168.197.184 from
00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:47:11 aon3 dhcpd: DHCPACK on 192.168.197.184 to 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:52:11 aon3 dhcpd: DHCPREQUEST for 192.168.197.184 from
00:50:04:5c:5c:bb (dell-3500xp) via eth0
Mar 8 09:52:11 aon3 dhcpd: DHCPACK on 192.168.197.184 to 00:50:04:5c:5c:bb
(dell-3500xp) via eth0
Mar 8 09:54:56 aon3 dhcpd: dhcpd shutdown succeeded
Mar 8 09:55:01 aon3 named[14238]: shutting down: flushing changes
Mar 8 09:55:01 aon3 named[14238]: stopping command channel on 127.0.0.1#953
Mar 8 09:55:01 aon3 named[14238]: no longer listening on 127.0.0.1#53
Mar 8 09:55:01 aon3 named[14238]: no longer listening on 192.168.197.203#53
Mar 8 09:55:01 aon3 named[14238]: exiting
Mar 8 09:55:01 aon3 named: succeeded
***end messages
| |
| Nils O. Selåsdal 2004-03-09, 5:34 am |
| In article <104pdfkdqj3n64@corp.supernews.com>, Knute Snortum wrote:
>
> "Nils O. Selåsdal" <noselasd@frisurf.no> wrote in message
> news:slrnc4ob01.cg4.noselasd@utelsystems.dyndns.org...
> wrote:
>
> *blush* That was indeed the case; not all the secret codes matched!
>
> But even after I fixed that and the A and PTR records were being updated in
> db.localhost, nothing is being updated in db.127.0.0. and "ping client_name"
> still doesn't work.
>
> This message is /var/log/messages intrigued me:
>
> Mar 8 09:39:56 aon3 named[14238]: client 127.0.0.1#35117: updating zone
> 'somewhere.com/IN': update failed: 'name not in use' prerequisite not
> satisfied (YXDOMAIN)
>
> What's the 'name not in use' prerequisite?
>
More strange, I think the bind or dhcpd mailing lists will be more helpful.
Just fyi, I've found ddns sometimes to go mickey. What fixes it, seems to be
1. stop everything. 2 remove all named .jnl files 3. remove the dhcpd server
lease file. 4. remove the ddns entries manually from the zone files.
5. start everything again.
|
|
|
|
|