TCPIP$BIND modification - VMS

This is a discussion on TCPIP$BIND modification - VMS ; When modifying the various db files is it necessary to manually bump the serial value? -- PL/I for OpenVMS www.kednos.com...

+ Reply to Thread
Results 1 to 11 of 11

Thread: TCPIP$BIND modification

  1. TCPIP$BIND modification

    When modifying the various db files is it necessary to manually bump the
    serial value?

    --
    PL/I for OpenVMS
    www.kednos.com

  2. Re: TCPIP$BIND modification

    Tom Linden wrote:
    > When modifying the various db files is it necessary to manually bump the
    > serial value?


    It is well advised to do so, but not necessary. Then, you need to TCPIP>
    SET NAME/INIT to get the bind server to reload the databases. Make sure
    you check the log file for any error message when it reloads it.

    However, if you have dynamic updates enabled (with DHCP server for
    instance), there are some issues with dynamic updates not being written
    and you need to use that dns server management utility (forget the name)
    to freeze the database , update it with your edit and unfreeze it) or
    something to that order.

  3. Re: TCPIP$BIND modification

    On Fri, 02 May 2008 18:30:01 -0700, JF Mezei
    wrote:

    > Tom Linden wrote:
    >> When modifying the various db files is it necessary to manually bump the
    >> serial value?

    >
    > It is well advised to do so, but not necessary. Then, you need to TCPIP>
    > SET NAME/INIT to get the bind server to reload the databases. Make sure
    > you check the log file for any error message when it reloads it.
    >
    > However, if you have dynamic updates enabled (with DHCP server for
    > instance), there are some issues with dynamic updates not being written
    > and you need to use that dns server management utility (forget the name)
    > to freeze the database , update it with your edit and unfreeze it) or
    > something to that order.



    Not using DHCP. I did not know about the SET NAME/INIT so I just did a
    TCPIP
    shutdown and start.



    --
    PL/I for OpenVMS
    www.kednos.com

  4. Re: TCPIP$BIND modification

    Tom Linden wrote:
    > On Fri, 02 May 2008 18:30:01 -0700, JF Mezei
    > wrote:
    >
    >> Tom Linden wrote:
    >>> When modifying the various db files is it necessary to manually bump the
    >>> serial value?

    >>
    >> It is well advised to do so, but not necessary. Then, you need to TCPIP>
    >> SET NAME/INIT to get the bind server to reload the databases. Make sure
    >> you check the log file for any error message when it reloads it.
    >>
    >> However, if you have dynamic updates enabled (with DHCP server for
    >> instance), there are some issues with dynamic updates not being written
    >> and you need to use that dns server management utility (forget the name)
    >> to freeze the database , update it with your edit and unfreeze it) or
    >> something to that order.

    >
    >
    > Not using DHCP. I did not know about the SET NAME/INIT so I just did a
    > TCPIP
    > shutdown and start.
    >
    >
    >

    $ @ SYS$MANAGER:TCPIP$BINDSETUP.COM

    has an option to restart the BIND server. Testing your changes
    will also restart the server. Or you could use

    $ @ SYS$STARTUP:TCPIP$BIND_SHUTDOWN.COM
    $ @ SYS$STARTUP:TCPIP$BIND_STARTUP.COM

    Jeff




    ----== Posted via Pronews.Com - Unlimited-Unrestricted-Secure Usenet News==----
    http://www.pronews.com The #1 Newsgroup Service in the World! >100,000 Newsgroups
    ---= - Total Privacy via Encryption =---

  5. Re: TCPIP$BIND modification

    On Fri, 02 May 2008 21:45:27 -0700, Jeff Campbell wrote:


    I can't seem to get it to work on one of my nodes. It likely is a typo
    but I can't see where. Does the following give any clues where to look?

    FREJA> @SYS$MANAGER:TCPIP$BINDSETUP
    TCPIP$BINDSETUP is initializing...
    ....
    6 - Test the BIND Server
    ....
    Enter domain :
    %TCPIP-W-NORECORD, information not found
    -TCPIP-E-BIND_NOSERVERS, default servers are not available

    Enter to continue:

    Executing:
    $MCR TCPIP$NSLOOKUP
    > server localhost
    > ls -d KEDNOS.COM.
    > exit


    Default Server: localhost
    Address: 127.0.0.1

    > Default Server: localhost

    Address: 127.0.0.1

    > [localhost]

    *** Can't list domain KEDNOS.COM: Unspecified error
    >



    In the config file have following entry

    zone "KEDNOS.COM" IN {
    type master;
    file "KEDNOS_COM.db";
    allow-update {
    127.0.0.1;
    208.85.204.75;
    };
    allow-transfer { any; };
    };

    and the references file is (I did bump the serial)

    ODIN> type KEDNOS_COM.db
    $ORIGIN .
    $TTL 10 ; 10 seconds
    KEDNOS.COM IN SOA KEDNOS.COM. POSTMASTER.KEDNOS.COM. (
    4499802 ; serial
    3600 ; refresh (1 hour)
    300 ; retry (5 minutes)
    172800 ; expire (2 days)
    43200 ; minimum (12 hours)
    )
    NS FREJA.KEDNOS.COM.
    A xxx.yy.zzz.75
    MX 100 FREJA.KEDNOS.COM.
    MX 200 ODIN.KEDNOS.COM.
    MX 200 HAFNER.KEDNOS.COM.
    $ORIGIN KEDNOS.COM.
    ODIN A xxx.yy.zzz.76
    HAFNER A xxx.yy.zzz.77
    ITANIC A xxx.yy.zzz.78
    MAIL CNAME KEDNOS.COM.
    WWW CNAME KEDNOS.COM.



    --
    PL/I for OpenVMS
    www.kednos.com

  6. Re: TCPIP$BIND modification

    Tom Linden wrote:

    > I can't seem to get it to work on one of my nodes. It likely is a typo
    > but I can't see where. Does the following give any clues where to look?




    look at TCPIP$BIND_COMMON:TCPIP$BIND_RUN.LOG it should give you some
    hints on what zones were loaded by the BIND SERVER




    > Enter domain :
    > %TCPIP-W-NORECORD, information not found
    > -TCPIP-E-BIND_NOSERVERS, default servers are not available


    This is different. It means that this particular host doesn't have a
    bind RESOLVER defined. (aka: client doesn't know which server to use).

    Easiest is to do the @TCPIP$CONFIG and setup the major parameters for
    the host, it insluce the list of DNS servers to use.

    Or, you can try with the TCPIP> interface.

    SET NAME defines the resolver parameters (except for /INIT which deals
    with the server)

    TCPIP> SET NAME/SYSTEM /DOMAIN=chocolate.ca/SERVER=chain

    (you may need a /ENABLE to it too). Once you know this works, you issue
    the SET CONF NAME command with the same parameters to make it permanent.


    You want something like this: (TCPIP> SHOW NAME )


    BIND Resolver Parameters

    Local domain: chocolate.ca

    System

    State: Started, Enabled

    Transport: UDP
    Domain: chocolate.ca
    Retry: 2
    Timeout: 5
    Servers: chain
    Path: No values defined

    Process

    State: Enabled

    Transport:
    Domain:
    Retry:
    Timeout:
    Servers:
    Path:
    TCPIP>


    And you need to SET HOST CHAIN /ADDRESS=
    (since the bind resolver must be able to locally resolve the name of the
    DNS server. For some reason, the TCPIP utility doesn't like you entering
    real IP addresses in the servers list.
    >
    > Enter to continue:
    >
    > Executing:
    > $MCR TCPIP$NSLOOKUP
    > > server localhost
    > > ls -d KEDNOS.COM.
    > > exit

    >
    > Default Server: localhost
    > Address: 127.0.0.1
    >
    >> Default Server: localhost

    > Address: 127.0.0.1
    >
    >> [localhost]

    > *** Can't list domain KEDNOS.COM: Unspecified error
    >>

    >
    >
    > In the config file have following entry
    >
    > zone "KEDNOS.COM" IN {
    > type master;
    > file "KEDNOS_COM.db";
    > allow-update {
    > 127.0.0.1;
    > 208.85.204.75;
    > };
    > allow-transfer { any; };
    > };
    >
    > and the references file is (I did bump the serial)
    >
    > ODIN> type KEDNOS_COM.db
    > $ORIGIN .
    > $TTL 10 ; 10 seconds
    > KEDNOS.COM IN SOA KEDNOS.COM. POSTMASTER.KEDNOS.COM. (
    > 4499802 ; serial
    > 3600 ; refresh (1 hour)
    > 300 ; retry (5 minutes)
    > 172800 ; expire (2 days)
    > 43200 ; minimum (12 hours)
    > )
    > NS FREJA.KEDNOS.COM.
    > A xxx.yy.zzz.75
    > MX 100 FREJA.KEDNOS.COM.
    > MX 200 ODIN.KEDNOS.COM.
    > MX 200 HAFNER.KEDNOS.COM.
    > $ORIGIN KEDNOS.COM.
    > ODIN A xxx.yy.zzz.76
    > HAFNER A xxx.yy.zzz.77
    > ITANIC A xxx.yy.zzz.78
    > MAIL CNAME KEDNOS.COM.
    > WWW CNAME KEDNOS.COM.
    >
    >
    >


  7. Re: TCPIP$BIND modification


    "Tom Linden" schreef in bericht
    newsp.uajw6pvzhv4qyg@murphus...
    > When modifying the various db files is it necessary to manually bump the
    > serial value?
    >
    > --
    > PL/I for OpenVMS
    > www.kednos.com


    I tend to forget to do that occasionally, with the result that BIND doesn't
    work properly.
    Hans



  8. Re: TCPIP$BIND modification

    In article <481ce8ea$0$7294$c3e8da3@news.astraweb.com>, JF Mezei writes:
    >And you need to SET HOST CHAIN /ADDRESS=
    >(since the bind resolver must be able to locally resolve the name of the
    >DNS server. For some reason, the TCPIP utility doesn't like you entering
    >real IP addresses in the servers list.


    Since when? I never had problems entering IP addresses as nameservers so far.

    --
    Peter "EPLAN" LANGSTOEGER
    Network and OpenVMS system specialist
    E-mail peter@langstoeger.at
    A-1030 VIENNA AUSTRIA I'm not a pessimist, I'm a realist

  9. Re: TCPIP$BIND modification

    Peter 'EPLAN' LANGSTOeGER wrote:
    >
    > Since when? I never had problems entering IP addresses as nameservers so far.
    >


    Remember that I live in a different universe :-)

    IP addresses seem fin in the TCPIP$CONFIG procedure, but if you do SET
    NAME in teh TCPIP utility, it seemed to really want a host name (or back
    translate it to a host name from the host database). Maybe it isn't a
    problem anymore, but when I set it up, I recall fighting to get an IP
    address in and giving up and allowing it to use a host name.

  10. Re: TCPIP$BIND modification

    On 4 mei, 11:40, "H Vlems" wrote:
    > "Tom Linden" schreef in berichtnewsp.uajw6pvzhv4qyg@murphus...
    >
    > > When modifying the various db files is it necessary to manually bump the
    > > serial value?

    >
    > > --
    > > PL/I for OpenVMS
    > >www.kednos.com

    >
    > I tend to forget to do that occasionally, with the result that BIND doesn't
    > work properly.
    > Hans


    If you do not bump the serial number of the zone file, slave servers
    will not pick up the change in the master database,
    unless you do tcpip$bind_shutdown, delete the .db files of the zone
    you have updated, and a tcpip$bind_startup
    on all slave servers, which is a pain. set server/init is as far as I
    know not the recommended method
    to restart the bind server on newer versions of tcpip.


  11. Re: TCPIP$BIND modification

    Jose Baars wrote:

    > on all slave servers, which is a pain. set server/init is as far as I
    > know not the recommended method
    > to restart the bind server on newer versions of tcpip.


    SET NAME/INIT does not restart the server per say. It causes it to
    re-initialise itself by rereading all config files and reloading the
    zone files from disk.

    The output continues to the same log file. (so you have to scroll down
    to see the results of the reload).

    I believe that SET NAME/INIT is the equivalent to

    rndc reload

    RNDC == "$SYS$SYSTEM:TCPIP$RNDC.EXE"

    typing rndc alone will give you a list of options to control the bind
    *server*.

+ Reply to Thread