Re: TCPIP Configuration -TCPIP-E-BIND_NO_ZONEXFR, zone transfer was unsuccessful

stuie_norris@xxxxxxxxxxxx wrote:
$ tcpip show host

Host address Host name

127.0.0.1 LOCALHOST, localhost
192.168.1.12 ds10.DHCPPool
%TCPIP-W-NORECORD, information not found
-TCPIP-E-BIND_NO_ZONEXFR, zone transfer was unsuccessful

SHOW HOST asks the name server (TCPIP SHOW NAME) for all the hosts it
knowns about. If your name server refuses, then you get that message.

Now my domain is openvms not DHCPpool.
I can see from the logicals that TCPIP defines that my router is
sending the openvms domain name.

You might want to define it as openvms.xxx and see if it makes a
difference. The problem is that without your own name server, your fake
domain and host names may cause problems.

Where is the "TCPIP$INET_DOMAIN" = "DHCPPool" coming from.

Download the TCPIP Management manual, it will describe what logicals you
can define to cause the DHCP client to log its activity. This may give
you a good idea of what really happens.


"TCPIP$BIND_DOMAIN" = "openvms"

This is the default domain tagged on when you try to resolve a host.

"TCPIP$INET_DOMAIN" = "DHCPPool"
"TCPIP$INET_HOST" = "ds10"
"TCPIP$INET_HOSTADDR" = "192.168.1.12"

This is the actualy identity of your host.

$ tcpip show route

DYNAMIC

Type Destination Gateway

AN 0.0.0.0 192.168.1.1
AH 127.0.0.1 127.0.0.1
AN 192.168.1.0/24 192.168.1.12
AH 192.168.1.12 192.168.1.12

$ tcpip show route /perm
%TCPIP-E-ROUTEERROR, error accessing routes database (TCPIP$ROUTE)
-TCPIP-W-NORECORD, information not found


TCPIP CREATE ROUTE

This creates an empty permanent route file and should remove the above
error message.
.

Relevant Pages

  • Routing problem
    ... I am running a 5.4 box as a gateway server / firewall / mail relay at ... Example of a ping to another 5.4 box connected directly to one of the ... ping: sendto: No route to host ...
    (freebsd-questions)
  • Re: how to login port 22 with ssh behind a router.
    ... What can I do to login my server with ssh? ... A routing table is either proper for your host, therefore every traffic should work, or it is not proper and there is no route to your host AT ALL. ...
    (comp.unix.bsd.freebsd.misc)
  • Re: Open SSH client error
    ... connect to host 83.229.64.51 port 22: ... because I already disabled the firewall and the selinux on this server ... I assume the ssh route should go out through your default gateway. ...
    (Fedora)
  • Re: "No route to host" when trying to connect to FTP server on the Internet
    ... to host" when trying from my NAT workstation. ... route add default 192.168.187.1 ... It's just this one FTP server that it won't connect to. ... Also sshd didn't work to same remote host either. ...
    (freebsd-questions)
  • Re: No route to host
    ... a DNS problem however it intrigues me that the server has associated ... Which may show that DNS is not the culprit. ... So you have a route to the host, DNS resolves correctly (at least at my ...
    (comp.mail.sendmail)