18.02.2014 Views

string

string

string

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

host1 IN MX 10 host2.domain1.<br />

This goes for all types of records, including HINFO and A records.<br />

Also, it is possible to get this error without explicitly setting the left hand side of a<br />

record. The DNS system defaults the left hand side to the last given left hand side.<br />

So you might have the following in a named database file:<br />

host1 IN A 123.124.125.126<br />

IN HINFO Sun Solaris<br />

alias1 IN CNAME host1.domain1.<br />

IN MX 10 host2.domain1.<br />

In this fragment, there is an implied alias1 in the left hand side of the MX record.<br />

If the alias was added after the database was in use for a while, the error would<br />

suddenly start showing up. Since the MX record was legal until the CNAME was added<br />

in front of it. This example could be fixed either by reversing the order of the MX and<br />

CNAME records, or explicitly giving the host1 in the lefthand side of the MX record.<br />

/net/<strong>string</strong>: No such file or directory<br />

Cause<br />

A user tried to change directory (for example with cd(1)) to a network partition on<br />

the system specified after /net/, but this host either does not exist or has not shared<br />

(exported) any filesystem.<br />

Action<br />

To gain access to files on this system, try rlogin(1).<br />

To export filesystems from the remote system, become superuser on that system and<br />

run the share(1M) command with the appropriate options. If that system is sharing<br />

filesystems for the first time, also run /etc/init.d/nfs.server start to begin<br />

NFS service.<br />

Alphabetical Message Listing 119

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!