Getting local names to resolve (DNS) (named -…
2009-05-13 13:17:35来源:未知 阅读 ()
This article shows how to set up named, the DNS daemon. This version uses BIND 4. Eventually, I'll upgrade to BIND 8.
Resolve? What do you mean?
I have named my three machines, NT1, NT2, and FreeBSD.
It would be nice to be able to type ping NT2 instead of ping 10.0.0.2. The process of converting the name to an IP address is referred to as resolving.
How resolution works
There are two main ways of resolving a host name (e.g. NT2). One is a hosts file, the other is DNS. With a hosts file, you list all of the computers in a file and refer to it from there. Normally, each machine would contain a hosts file. With DNS, you list the hosts in a file on one computer, and all the other computers use the service on that computer. I've decided to use DNS.
During my installation of DNS, I got to the point where everything I wanted to do, worked just fine. But one thing didn't work. And that was qpopper. When my Pegasus mail client on NT1 connected to the POP server on FreeBSD, the following message would be displayed on the console:
unable to get canonical name of client
When
searching the mailing list archives
, I found a reference to the above message. There is also a semi-obscure reference to this situation within the man pages for qpopper, but no direct reference to this message. Basically, qpopper does a reverse DNS lookup on the IP address it it given when you try to read your mail. It then does a DNS lookup on that name to verify that the IP address matches. If it does not, it puts out the above message but continues to process the request. In that respect, the message is only a warning. Services can continue otherwise unhindered.
26 July 1998
I've received lots of help from a
FreeBSD Questions mailing list
person, who shall remain nameless until future notice. He suggested I send him my named files as a starting point. So off went the following files:
host.conf
named.boot
named.local
named.root
resolv.conf
My helper suggested sevearal changes to my DNS files. There were many glaring errors, which, when pointed out, were obvious even to me. Some of my reverse IP entries where totally incorrect.
27 July 1998
I implemented the changes as suggested by my helper. But no luck. It didn't work. I reported back the results.
28 July 1998
Tonight I received a very detailed reply from my helper. Much work had been carried out on my behalf. Specifically, my setup had been duplicated at his site. The files used for that duplication had been forwarded to me.
After implementing the changes, everything worked perfectly. I'll write up what I did at a later date.
标签:
版权申明:本站文章部分自网络,如有侵权,请联系:west999com@outlook.com
特别注意:本站所有转载文章言论不代表本站观点,本站所提供的摄影照片,插画,设计作品,如需使用,请与原作者联系,版权归原作者所有
- Freebsd oracle 10g 2009-05-13
- KDE/FreeBSD 测试 QT-4.5.1. 2009-05-13
- OpenBSD 4.5下安装Gnome 2.24成功! 2009-05-13
- OpenBSD 4.5 2009-05-13
- DragonFly BSD 2.2.1发布 2009-05-13
IDC资讯: 主机资讯 注册资讯 托管资讯 vps资讯 网站建设
网站运营: 建站经验 策划盈利 搜索优化 网站推广 免费资源
网络编程: Asp.Net编程 Asp编程 Php编程 Xml编程 Access Mssql Mysql 其它
服务器技术: Web服务器 Ftp服务器 Mail服务器 Dns服务器 安全防护
软件技巧: 其它软件 Word Excel Powerpoint Ghost Vista QQ空间 QQ FlashGet 迅雷
网页制作: FrontPages Dreamweaver Javascript css photoshop fireworks Flash