DHCP and DNS

[Willem Grooters]

VSM 7.3-2, TCPIP 5.4 ECO

The machine has been set up as both DHCP- and DNS server, where DHCP was allowed to update the DNS-files (same address in DNS configuration). So when I added PC's to the network, I would find their names and addressed in the DNS files, and tehse machiens will get the specified addresses again and again. These are a number of PC's - and a laptop. If that latter one is conected by copper, it will get the same address.
But now I have new machines, and wireless access.
DHCP will supply all with an IP address, DNS-server and gateway address, but the IP addresses change, and their names and momentary address do not show up in DNS.
AFAIK I didn't make a change in either configuration.
Any idea why this happens?
I'm not really concerned in changed IP-addresses, but would like to have the machines names listed in TCPIP SHO HOST - and now they're not, causing a problem to access these machines by their name using IP.

Willem

[Robert Gezelter]

Willem,

A first question: Is the OpenVMS box the ONLY DHCP server on the network.

Many Wireless Access Points are combined Access Points and Firewalls. In these configurations, the DHCP is done by the firewall, on the inside side of the firewall. In that situation, the OpenVMS box never sees the DHCP query. Your first step is to verify that the IP addresses handed out are handed out by the OpenVMS DHCP server.

- Bob Gezelter, http://www.rlgsc.com

[Willem Grooters]

It is, at least when all access points are swithed off. I have deliberately disabled DHCP on the access point, because I have this server available.
At this very moment, Access point is off power, the machine I'm working on got it's address and data - so that must have come from the DHCP server, but is NOT found in DNS.

[Antoniov. · Accepted solution]

Willem,
look carefully at TCPIP$BIND.CONF file in SYS$SPECIFIC:[TCPIP$BIND] you can find answer in it!

Antonio Vigliotti

[Robert Gezelter]

Willem,

Before we go any further, what is the information about the lease on the DHCP data your machine is using when it has been booted with the Access Point disabled?

- Bob Gezelter, http://www.rlgsc.com

[Willem Grooters]

Bob,

This is on my (new) machine:

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : intra.grootersnet.nl
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Network Connecti
on
Physical Address. . . . . . . . . : 00-11-D8-11-AE-C9
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.205
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.30
DHCP Server . . . . . . . . . . . : 192.168.0.200
DNS Servers . . . . . . . . . . . : 192.168.0.2
192.168.0.30
Primary WINS Server . . . . . . . : 192.168.0.2
Lease Obtained. . . . . . . . . . : zondag 10 april 2005 11:19:26
Lease Expires . . . . . . . . . . : maandag 11 april 2005 11:19:26

This is all correct.

Antonio,
I _may_ find it - and I did, at least, I think I have. The .DB files _should_ reside on SYS$SPECIFIC:[TCPIP$BIND] unless specified otherwise. I _thought_ I had, but the file does not hold such a statement - and the files DO reside elsewehere.
However, I find that nodes specified in these files DO show up and translate correctly.....

[Willem Grooters]

update: .CONF does contain option for chnage of directory, and files are correct. It has worked in the past.

[Antoniov.]

Willem,
the configuration of your new machine appears correct. Why IP address is x.x.x.205? Have you hundred hosts or else what is the range of your DCHP?
If x.x.x.205 is out of range, your DNS (that's the same machine of DHCP) couldn't recognize the new machine, I suppose.

Antonio Vigliotti

[Willem Grooters]

antonio,

range x.x.x.192 - x.x.x.254 ( where, I know, are at least 3 addresses in use but DHCP will locate that and mark the addresses unavailable - I found that in the log).

Log reveiled a few issues, but not why (but I can think of a reason - will check that later)

[Willem Grooters]

I _think_ I found it.
When I place the databasefiles on SYS$SPECIFIC:[TCPIP$BIND} and remove the directory option ftom BIND.CONF, it works.
Thinking a bit deeper: the location I put the files on, has READ access for both BIND and DHCP - but no WRITE access. And updating the DNS database will create a journal file!
I'll check that later (not at my machiens now)....
(It seems so obvious that this is not in the manuals....)

[Antoniov.]

Willem,
happy if you solve!
Because BIND and DHCP are system processes it's weird they can't write to it.

Antonio Viglotti

[Willem Grooters]

Not really system processes.
BIND and DHCP processes are by UIC [TCPIP$AUX,*], that is [3655,*]. Their home directories are owned by that group, so there is no a problem.
But the location I have my configuration in had no access first (I still wonder that DNS DID show my nodes from the database after reboot, including the "old" DHCP-added ones).
I added an ACE for BIND and DHCP, but forgot to add WRITE access...Will do that tonight and see whether it does the trick. If not, I'll have to revert to the "standard" solution (Cannot place a call at HP since I don't have a support contract! How STUPID)

Willem

[Willem Grooters]

WRITE access on the alternate location for both TCPIP$BIND and TCPIP$DHCP (the two I know being involved) has no effect....

Using the files on the standard location is no porblem: it simply works....

Kept it that way, for now

Willem

[Willem Grooters]

I'm not entrily satisfied, and having another thought.
Currently, the DNS files are on their default location, they are updated by DHCP as I would expect. But I want/need them on another disk (accessable by any node (like the autorisation files)) , and still have DHCP to update them.
I wonder: Since all translations are correct, one may assume DNS can find the files, so update should be possible as well. If DNS is 'triggered' by DHCP when a new address is supplied, there is something wrong in DNS.
Another, probably related matter: After lease-time has expired, not even after some time, even over reboot. The consequence can be that a "new" machine on the network gets an "old" name - one long removed from the network. It might be a configuration issue but I haven't found a description in the manual to change it.

Willem