After working on this some more overnight.
I can add records interactively via nsupdate (as shown below). But, cannot
get the same results from an ipconfig /release /renew from a
workstation. I am totally stumped at this point.
Any ideas (and yes, I did do over the semicomplete URL
On 29 March 2013 12:19, Jim Bucks jbu...@coloradostudios.com wrote:
Any ideas (and yes, I did do over the semicomplete URL provided by
?Alex?). The only difference I can see is that I used a 512 bit key vs the
examples 128bit key. And, I'm using a slaves/ directory vs internal/
directory for
Try using a more simple MD5, short key.
Seem to remember that DHCP doesn't like non-MD5 keys (eg SHA)
There was also some sort of length bug? - try 128 bit length.
On Fri, 2013-03-29 at 06:19 -0600, Jim Bucks wrote:
After working on this some more overnight.
I can add records
On Fri, Mar 29, 2013 at 6:39 AM, Mark Elkins m...@posix.co.za wrote:
Try using a more simple MD5, short key.
Seem to remember that DHCP doesn't like non-MD5 keys (eg SHA)
There was also some sort of length bug? - try 128 bit length.
On Fri, 2013-03-29 at 06:19 -0600, Jim Bucks wrote:
On Fri, Mar 29, 2013 at 10:02 AM, Steven Carr sjc...@gmail.com wrote:
On 29 March 2013 14:57, Jim Bucks jbu...@coloradostudios.com wrote:
I just noticed (has been there all along), that the subdomain is not
showing
up in the automated unable to line.
I want it to add
Hi Mark, Graham, others.
I've spent the last day trying all sorts of things to get this working (to
no avail). I'm still at the stage of DHCP offering the lease IP address,
but the DNS is not automatically updating the two zones files with the
newly leased addresses.
Here is a grief summary of
Apparently the DHCP server tries to put the change into BIND but times
out. What does the named log tell about this?
Either it did see the request or it will have an explanation why it
won't do it.
On 28/03/13 18:18, Jim Bucks wrote:
Hi Mark, Graham, others.
I've spent the last day trying
Hi Sten,
Thanks for the response, I only dabble in DNS setups every 5 years (or
so). I really thought this would be a no brainer, and most likely have
some simple command / syntax error causing all of this.
From /var/log/messages
Mar 28 11:22:57 dns04 dhcpd: DHCPOFFER on 172.10.20.101 to
Hi Jim,
Lost track but have you tried using the IP address of the server for the
primary, 172.10.20.101 instead of 127.0.0.1?
zone dhcp.coloradostudios.com. {
primary 172.10.20.101; - change from
127.0.0.1
key DHCP_UPDATER;
}
best!
jim
On 3/28/2013 1:31
Here's from a recent re-start of the named service. There were no
additional log entries when the dhcp service granted the lease and failed
to update the zones files.
Mar 28 11:38:15 dns04 named-sdb[3493]: received control channel command
'stop'
Mar 28 11:38:15 dns04 named-sdb[3493]: shutting
No I have not tried that, but .101 is a leased IP address for a Windows
workstation.
I'm willing to try it, but it seems like that would mean I would need a
zone like this for all of my leased addresses???
Jim
On Thu, Mar 28, 2013 at 11:42 AM, Jim Glassford jmgl...@iup.edu wrote:
Hi Jim,
I'm completely unable to fix the top-post/body comments here, so my comments
are at the bottom:
On Mar 28, 2013, at 1:52 PM, Jim Bucks jbu...@coloradostudios.com wrote:
No I have not tried that, but .101 is a leased IP address for a Windows
workstation.
I'm willing to try it, but it seems
Hi Jim,
No, sorry, wrong IP address, the real IP address of the dns server, not
the client.
zone dhcp.coloradostudios.com http://dhcp.coloradostudios.com. {
primary your_dns_server_IP_address; - change from 127.0.0.1
key DHCP_UPDATER;
}
Also do you have a /var/log/named.log file or
Hi All (sorry for the top-posting)
Alan - thanks for the link. I'll be checking it out / looking it over.
Jim,
Based on the nsupdate output (below), it looks like I've hosed up something
in my key. I used the key string from the .private key file (I've found
some search results that say
Hi All,
Alan, I looked that doc over and the only thing I found different than what
I used the key string from the .private key file.
Jim, thanks for the nsupdate pointer. I've never had to delve into that
level of debugging.
When using nsupdate, I was able to update the forward and reverse
Hi Jim,
Looking at your config files, believe the keys do not match in
named.conf and dhcpd.conf but maybe they were adjusted for the posting
to the list. Alan Clegg's link shows creating the key and adding it to
the files and also some nsupdate examples.
Would want like the following,
Hi Jim,
Shouldn't there be quotes around the key string in the named .conf file? I
have quotes around mine in named.conf. I do not have quotes around the key
string in the dhcpd.conf.
If this is correct, I've made sure they match (I was trying to genericize
the key string before), but not any
Problem.
===
I'm working on getting a DHCP / Bind / DDNS server set up. When a client
receives
an IP address lease, I want the forward / reverese zones files updated
so
name lookups behave appropriately / as expected.
After a couple of
Hi Jim,
I'm getting either of the following errors:
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to
proccilapxp.dhcp.coloradostudios.com
http://proccilapxp.dhcp.coloradostudios.com: bad DNS key
dhcpd: unable to add reverse map from 51.20.10.172.in-addr.arpa. to
Thanks Graham,
I appreciate the hints. However, I'm still having problems (after finding
a few more how-to's). Any other pointers / tips on what to look for?
Jim
Mar 26 14:18:24 dns04 dhcpd: DHCPRELEASE of 172.10.20.51 from
00:0b:cd:33:b6:49 (proccilapxp) via eth1 (found)
Mar 26 14:18:31
In message camz8b4edupzje_uqespzqvs-oqwpy6hj2wasz9el397gen0...@mail.gmail.com
, Jim Bucks writes:
Thanks Graham,
I appreciate the hints. However, I'm still having problems (after finding
a few more how-to's). Any other pointers / tips on what to look for?
Jim
Fix the view to
21 matches
Mail list logo
