Some time ago, when I configured the DNS for my company's intranet with sendmail mail server, I was too busy. I found all the information on the Internet. 6. configuration of Version x is followed by nslookup. server can find is always unavailable, and company leaders are pressing it, you have to deal with samba first (you only need to set the linux server configured with samba to the same group as the windows client ). After n times of debugging, I finally found a way to solve the DNS problem. The following is an introduction (welcome to your comments ):
(1) first enter the/etc directory, vi named. conf, and add the following lines to it:
Zone "x. x" IN {
Type master;
File "x. x ";
};
Zone "0.168.192.in-addr. arpa" IN {
Type master;
File "192.168.0 ";
};
(2) create a forward and reverse resolution file in the/var/named directory. The file is too complex and won't be created, right, this is a stupid method I have found. ls is there a localhost. the zone file is her, cp localhost. zone x. x, this is not enough. vi x. x has the following interface:
$ TTL 86400
$ ORIGIN localhost.
@ 1D in soa @ root (
42; serial (d. adams)
3 H; refresh
15 M; retry
1 W; expiry
1D); minimum
1D in ns @
1D in a 127.0.0.1
Change the file:
$ TTL 86400
$ Origin x. x.
@ 1D in SOA @ root (
42; Serial (D. Adams)
3 h; refresh
15 m; retry
1 W; expiry
1D); Minimum
1D in NS @
1D in a xxxx. xxxx
You can. Then, run the/etc/init. d/named restart command again. If yes, there is a forward resolution. If you don't believe it, use NSLookup to give it a try. You can use the named. Local file CP for reverse resolution. I will not talk about it here. If you try multiple times, NSLookup will be successful.