On Fri, Mar 29, 2013 at 10:02 AM, Steven Carr wrote:
> On 29 March 2013 14:57, Jim Bucks 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 dhcp-172-
On Fri, Mar 29, 2013 at 6:39 AM, Mark Elkins 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
com to 172.10.20.101: timed out
Mar 29 06:10:44 dns04 dhcpd: DHCPREQUEST for 172.10.20.101 (172.10.5.5)
from 00:0b:cd:33:b6:49 (proccilapxp) via eth1
Mar 29 06:10:44 dns04 dhcpd: DHCPACK on 172.10.20.101 to 00:0b:cd:33:b6:49
(proccilapxp) via eth1
On Thu, Mar 28, 2013 at 2:26 PM, Jim Bucks wrote:
>
172.10.20.51 172.10.20.254;
}
On Thu, Mar 28, 2013 at 2:00 PM, Jim Glassford wrote:
> 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 li
800 ; expire (1 week)
86400 ; minimum (1 day)
)
NSdns04.den.coloradostudios.com.
$ORIGIN 20.10.172.in-addr.arpa.
$TTL 3600; 1 hour
101PTRdhcp.coloradostudios.com.
[root@dns04 keys]#
On Thu, Mar 28, 2013 at 1:05 PM, Ji
e 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;
>> }
>
Either way, "network unreachable" is a
> big problem, even if it's from a minor typo in a notify-related clause in
> the config file.
>
> HtH,
>
> Len
>
> --
> *From:* Jim Bucks
> *To:* Niall O'Reilly ; bind-users@list
gt;
> best!
> jim
>
>
> On 3/28/2013 1:31 PM, Jim Bucks wrote:
>
> 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 / synta
710]: error (network unreachable)
resolving 'dns04.den.coloradostudios.com/A/IN': 2001:503:ba3e::2:30#53
Mar 28 11:38:30 dns04 named-sdb[3710]: error (network unreachable)
resolving './NS/IN': 2001:500:2d::d#53
Mar 28 11:38:30 dns04 named-sdb[3710]: error (network unrea
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 all sorts of things to get this working (to
> no avail). I'm still at t
the bare minimum
config into into it.
Attached are my configs.
Any ideas on what I've hosed up?
Thanks,
Jim
--
Jim Bucks - IT Director
Colorado Studios <http://www.coloradostudios.com>, Mobile TV
Group<http://www.mobiletvgroup.com>,
HDNet <http://www.hd.net>, AXS.tv &l
>#file "internal/db.172.10.20";
> }
>
> (and similar a change for the forward zone).
>
> Graham
>
> --
> Graham Clinch
> Systems Programmer,
> Information Systems Services,
> Lancaster University
>
>
--
Jim Bucks - IT Director
Colorado Stud
t;keys" to tell /
let dhcpd
update the DNS "zones" file, but I'll be 'derned if I can figure out what's
breaking.
Any pointers on what to look for in order to get this working would be
appreciated.
Thanks,
Jim
I've attached the current configs in the hopes th
13 matches
Mail list logo
