27-Aug-2006

DNS trouble
I installed the latest patches on VMS, and rebooted. That caused severe problems with DNS, just the local data was accessable with TCPIP SHOW HOSTS - nothing that is stored in the BIND files:

$ tcpip sho host

LOCAL database

Host address Host name

192.168.0.200 3D_GROOTERS, CL_GROOTERS
192.168.0.33 CERBEROS
192.168.0.4 DAPHNE.INTRA.GROOTERSNET.NL, DAPHNE
192.168.0.2 DIANA.INTRA.GROOTERSNET.NL, DIANA, diana,
WWW.INTRA.GROOTERSNET.NL
192.168.0.251 LJ2100TN
127.0.0.1 LOCALHOST
193.172.141.34 MAIL.VXCOMPANY.COM
65.125.246.7 VMSPR2.PARSEC.COM
192.168.0.31 WIRELESS
192.168.0.30 charon.intra.grootersnet.nl
10.0.0.1 cl_diana, CL_DIANA
$

and that's it. Beacuse of that, the webserver was started on the only web available: the administration entry on the local IP address on port 82 (actually, that's what triggered the idea something was wrong). and indeed: this was the logfile:

$ type TCPIP$BIND_RUN.LOG
$ Set NoOn
$ VERIFY = F$VERIFY(F$TRNLNM("SYLOGIN_VERIFY"))
Sun 27 22:08:02 NOTICE: starting BIND 9.2.1
Sun 27 22:08:02 INFORMATIONAL: using 1 CPU
Sun 27 22:08:02 INFORMATIONAL: loading configuration from 'SYS$SPECIFIC:[TCPIP$BIND]TCPIP$BIND.CONF'
Sun 27 22:08:02 INFORMATIONAL: no IPv6 interfaces found
Sun 27 22:08:02 INFORMATIONAL: listening on IPv4 interface *, 0.0.0.0#53
Sun 27 22:08:02 INFORMATIONAL: listening on IPv4 interface LO0, 127.0.0.1#53
Sun 27 22:08:02 INFORMATIONAL: listening on IPv4 interface WE0, 192.168.0.2#53
Sun 27 22:08:02 INFORMATIONAL: listening on IPv4 interface WE0, 192.168.0.200#53
Sun 27 22:08:02 WARNING: zone INTRA.GROOTERSNET.NL' allows updates by IP address, which is insecure
Sun 27 22:08:02 WARNING: zone '0.168.192.IN-ADDR.ARPA' allows updates by IP address, which is insecure
Sun 27 22:08:02 ERROR: none:0: open: TCPIP$ETC:RNDC.KEY: file not found
Sun 27 22:08:02 NOTICE: couldn't add command channel 127.0.0.1#953: file not found
Sun 27 22:08:02 INFORMATIONAL: zone 0.0.127.IN-ADDR.ARPA/IN: loaded serial 42
Sun 27 22:08:02 INFORMATIONAL: zone 0.168.192.IN-ADDR.ARPA/IN: loaded serial 2006082701
Sun 27 22:08:02 INFORMATIONAL: zone LOCALHOST/IN: loaded serial 42
Sun 27 22:08:02
INFORMATIONAL: zone INTRA.GROOTERSNET.NL/IN: loaded serial 2006082701
Sun 27 22:08:02 INFORMATIONAL: running
Sun 27 22:08:02 INFORMATIONAL: zone 0.168.192.IN-ADDR.ARPA/IN: sending notifies(serial 2006082701)

Looking into the configuration, it shows that DNS was not running:

$ tcpip sho name

BIND Resolver Parameters

Local domain: INTRA.GROOTERSNET.NL

System

State: Started, Disabled

Transport: UDP
Domain:
Retry: Not defined
Timeout: Not defined
Servers: No values defined
Path: No values defined

Process

State: Disabled

Transport:
Domain:
Retry:
Timeout:
Servers:
Path:
$

but in the permanent configuration, it is defined:

$ tcpip sho config name

BIND Resolver Configuration

Transport: UDP
Domain: INTRA.GROOTERSNET.NL
Retry: 4
Timeout: 4
Servers: 127.0.0.1
Path: No values defined

Address 127.0.0.1 wasn't possible according the log, so I added a second one that IS valid: The machine's own address:

$ tcpip sho config name

BIND Resolver Configuration

Transport: UDP
Domain: INTRA.GROOTERSNET.NL
Retry: 4
Timeout: 4
Servers: 127.0.0.1, 192.168.0.200
Path: No values defined

but that didn't help either. Nor did re-configuring of DNS; that was suggested on the ITRC request (http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=1054911), although I found, in starting TPCIP, that it took ages to define the interfaces.
A bright idea, given on the output as shown above, had me decide to re-enable it accoring the permanent configuration:

$ TCPIP SET NAME -
/DOMAIN= INTRA.GROOTERSNET.NL/SERVER=127.0.0.1/RETRY=4/TIMEOUT=4
$ TCPIP SET NAME/DOMAIN= INTRA.GROOTERSNET.NL/SERVER=127.0.0.1 -
/RETRY=4/TIMEOUT=4/SYSTEM/ENABLE

That gave back the DNS data. It looked right since on the PC, I could access the internal and external webs.