On 19 Jul 2001 10:54:49 +0100, David Ryan wrote:
>> Hmm - peculiar. Let's start at the very beginning and see if we are
> assuming something or missing something.
>> Your machine starts up and does a DHCP request on the network asking if
> anyone out there will give it an address. On the assumption that you
> only have one DHCP server (check this) then it will reply to the request
> with an address at least and also other details such as default gateway,
> etc . . .
Yes there is only the one DHCP server. My network at home is completely
> Assuming that your single DHCP server receives the request it will
> process it against its rules and issue the address. So here's where the
> complication could come in. It could be a problem with your ruleset.
>> I note from your original mail that the hostname of the problem machine
> is 'acer.technobrat.net' and I also note that according to nslookup in
> the real world technobrat.net is delegated to ns.host4u.net - this may
> be part of your problem.
Ah, but it couldn't as my network at home is completely internal and
everything inside nslookup works fine.
lookups inside nslookup resolve just fine:
acer.technobrat.net resolves to 10.11.11.5
10.11.11.5 resolves to acer.technobrat.net
edge.technobrat.net resolves to 10.11.11.1
10.11.11.1 resolves to edge.technobrat.net
likewise for caffeine, air and other nodes.
and I have edge set up as the SOA for technobrat.net - as
this is completely internal I can't really see any conflicts
pings do not resolve for acer (10.11.11.5) but seem to for edge.
I haven't checked to see if ping resolves for any of the other
machines just yet.
> Have you recently tried to enable DDNS or
> anything like that ?
> Imagine this - your DHCP server wants to issue an
> address and a fixed hostname to your client, but before it does this it
> tries to update both the forward and reverse zones but isn't allowed to
> update the forward since presumably host4u.net have allow-update ACLs on
> their zones. As a result your DHCP server refuses to issue the address
> to your client. This is just a theory but it makes sense to me.
I don't think this scenario is at all likely - cin (completely internal
network) don'cha know B^)
> Try creating a dummy zone (which doesn't exist in the outside world) on
> your own machine and allow updates from 127.0.0.1 and then change the
> fixed host name to something in the dummy zone and see if that works.
This is pretty much the scenario at home, from one way of looking at it
- and it doesn't work.
> Otherwise try turning off DDNS if you have been playing with it and see
> if that helps.
Well I'm not using DDNS....thanks for all your help anyways David. B^)
Maintained by the ILUG website team. The aim of Linux.ie is to
support and help commercial and private users of Linux in Ireland. You can
display ILUG news in your own webpages, read backend
information to find out how. Networking services kindly provided by HEAnet, server kindly donated by
Dell. Linux is a trademark of Linus Torvalds,
used with permission. No penguins were harmed in the production or maintenance
of this highly praised website. Looking for the
Indian Linux Users' Group? Try here. If you've read all this and aren't a lawyer: you should be!