Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations TouchToneTommy on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

NW DNS: cant resolve 2

Status
Not open for further replies.

summoner

Technical User
Sep 28, 2002
105
US
I am trying to timesync to an external NTP source with my NW6 server. I enter the server's DNS name and from the timesync debug screen, errors start popping up. So I try to ping the DNS name using ping.nlm and it returns this message:

"Could not understand (ntp server) as a host name or address. Please make sure NETDB.NLM is loaded and sys:/etc/resolve.cfg is configured correctly."

Pinging the ip address is successful. Netdb.nlm is loaded and resolve.cfg is empty. I have NAMED running on this server (it works)...do I have to tell NW to use NAMED as a DNS server or what? What can I do to make NW resolve its own DNS names?
 
I'm realitivly new to NetWare 6 but under NetWare 4.11 if the resolv.cfg is empty I would never be able to resolve host names.

the entry: domain yourdomain.com
nameserver 172.16.4.5

Could be that timesync does not use the local server as default but looks in the resolv.cfg file to point it to a DNS server.

I would add the entries in the resolv.cfg file and then see if it can then resolve the ntp server. I know under NetWare 4.11 we had to reboot for any changes in the resolv.cfg file to take affect. We are in the process of updating to NetWare 6 now but all my resolv.cfg files are already pointing to where they need to go. Not sure if a reboot for NetWare 6 is needed or not....



david e
*end users are just like computers, some you can work with...others just need a simple reBOOTing to fix their problems.*
 
Regardless of whether you have DNS setup, you could also just put the IP address of the NTP server into the TIMESYNC configuration instead of the DNS name. In the past, there have been various issues when trying to use DNS names in the timesync configuration.. This TID lists a few good sources and tells how to do it:
With that said, your server in general will be much easier to work with if you're running DNS. So i would work on getting that setup.

If you're new to NetWare, you probably don't know about INETCFG.NLM. This is a utility that is used to automate the NIC settings.. When you first install your server, all NIC commands will be in the AUTOEXEC.NCF. When you run INETCFG.NLM, it removes them from autoexec and puts the commands into it's configuration file. Then, by using INETCFG, you can manage the various configurations including the DNS settings, IP settings, routing configs, etc.

The cool thing about INETCFG is that you can then do a "REINITIALIZE SYSTEM" and implement all the changes on the fly, without restarting the server. very cool.

Marvin


Marvin Huffaker MCNE, CNE
Marvin Huffaker Consulting
 
Very cool stuff in inetcfg...also discovered filtcfg. Netware is probably still the best OS, other than *nix if you need to support old hardware or run old protocols. It looks like there still is full support for token-ring source route bridging, appletalk, of course IPX etc... Oh yeah, found the DNS resolver as well and now timesync works with DNS names. Thanks.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top