topic named in Operating System - HP-UX

named

Peter Brimacombe — Fri, 25 Oct 2002 20:06:04 GMT

My organization is renumbering its nodes from 142.61.xxx.xxx to 10.xxx.xxx.xxx so that it can segment the network traffic.

I have an HP-UX server with address 142.61.xx.28 , I want to set up and test named with the 10.xxx.xxx.xxx addresses without changing the host itself! Is this possible? I have tried it - named seems to be running but the command
nslookup 142.61.xx.28
says that the name server is not available

Re: named

John Dvorchak — Fri, 25 Oct 2002 20:26:34 GMT

Are you sure you have named setup correctly?
/etc/named.boot
/etc/named.db directory
/etc/named.db/ zone files
/etc/named.db/ arpa files

man named to get it going and also don't forget about the hpux utiliy hosts_to_named to create the zone files for you from the /etc/hosts file.

Also check /var/adm/syslog/syslog.log for named errors that might give you a hint.

Re: named

Adam J Markiewicz — Mon, 28 Oct 2002 10:46:58 GMT

As far as I know:

/etc/rc.config.d/netconf

find:
IP_ADDRESS[0]=142.61.xx.28

change to:
IP_ADDRESS[0]=10.xxx.xxx.xxx

reboot

Good luck

Adam

Re: named

Gerhard Roets — Mon, 28 Oct 2002 11:09:55 GMT

If you have your basic named config correct.

You must then just configure multiplexing.

In the /etc/rc.config.d/netconf file
add an extra interface

INTERFACE_NAME[1]=lan0:1
IP_ADDRESS[1]=10.xxx.xxx.xxx
SUBNET_MASK=255.yyy.yyy.yyy

reboot

[1]<-- is one above your current land card number.

now you can do a nslookup
and then at the > prompt
type "server 10.xxx.xxx.xxx" and test.

PS. This aught to work ... I am assuming you have a simple networking enviroment. Also make sure the machine that conmnects to the new IP has an IP in the 10.xxx.xxx.xxx range that matches with the subnet mask.

Regards
Gerhard

Re: named

Bob_Vance — Mon, 28 Oct 2002 19:11:13 GMT

Presumably, you added a secondary IP address with something like:

ifconfig lan0:5 10.1.1.1

But, did you stop/start named so it would find the new address and listen on it?

After doing a stop/start on 'named', execute:

netstat -an

You should see something like:

udp 0 0 10.120.212.53
udp 0 0 10.1.1.1.53
udp 0 0 127.0.0.1.53
udp 0 0 10.10.120.12.53

The above system has 3 aliases on the NIC:

netstat -ivn

Name Mtu ... Address
lan0 1500 ... 10.10.120.12
lan0:5 1500 ... 10.10.120.212
lan0:7 1500 ... 10.1.1.1

bv