- Community Home
- >
- Servers and Operating Systems
- >
- Legacy
- >
- Operating System - Tru64 Unix
- >
- Tru64 BIND Client won't stay working
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 07:42 AM
тАО11-17-2009 07:42 AM
Tru64 BIND Client won't stay working
- Tags:
- bind
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 08:07 AM
тАО11-17-2009 08:07 AM
Re: Tru64 BIND Client won't stay working
> it fails [...]
Actual command? Actual results?
> hosts=local,bind,yp.
Are you using YP (NIS)?
> As far as I know, my routes are correct.
As a non-psychic with no information from
you, how can I argue?
> Could this me a matter of the route daemon
> not working?
Are you running routed (or whatever), or are
you using static routes?
> [...] I think there's something wrong with
> the routing. How do I check?
netstat -rn
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 08:21 AM
тАО11-17-2009 08:21 AM
Re: Tru64 BIND Client won't stay working
Node> nslookup something
*** Can't find server name for address 10.32.31.220: No response from server
*** Default servers are not available
> Are you using YP (NIS)?
No, I just accepted the defaults.
> Are you running routed (or whatever), or
> are you using static routes?
routed.
> netstat -rn
Node> netstat -rn
Routing tables
Destination Gateway Flags Refs Use Interface
Netmasks:
Inet 255.255.192.0
Inet 255.255.255.0
Route Tree for Protocol Family 2:
10.33/18 10.33.1.99 U 29 56257 tu0
127.0.0.1 127.0.0.1 UH 1 0 lo0
192.168.1/24 192.168.1.179 U 1 262 tu1
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 08:26 AM
тАО11-17-2009 08:26 AM
Re: Tru64 BIND Client won't stay working
net 10.0.0.0 gateway 10.33.0.11 metric 1 active
and this is in routes
default 10.33.0.11
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:08 AM
тАО11-17-2009 09:08 AM
Re: Tru64 BIND Client won't stay working
> [...]
Ok. And what are the addresses of the name
servers? (Do you have a route (or routes) to
them?)
> I don't see the default gateway [...]
I've never used routed, so I know nothing,
but I wouldn't bet that anyone looks at
/etc/gateways (or any other static route
stuff) if you use routed. Knowing nothing,
I'd need to look at the "rc" scripts to see
who does what when at system start-up.
> 10.33/18 10.33.1.99 U 29 56257 tu0
> default 10.33.0.11
And 10.33.1.99 is not 10.33.0.11.
Again, I've never tried mixing a static route
into a routed situation, but you might try
something like
route add default 10.33.0.11
(or whatever syntax "man route" suggests) to
see if that helps. (See if "netstat -rn"
actually changes, too.)
Do you have any other, similar (working)
systems? How are they configured?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-17-2009 09:26 AM
тАО11-17-2009 09:26 AM
Re: Tru64 BIND Client won't stay working
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
тАО11-18-2009 09:37 PM
тАО11-18-2009 09:37 PM
Re: Tru64 BIND Client won't stay working
I can see them now. I see no one looking at
"/etc/gateways":
urtx# pwd
/sbin/init.d
urtx# grep gateways *
urtx#
but "/sbin/init.d/routes" does seem to
consider "/etc/routes". Around here:
urtx# cat /etc/routes
default 10.0.0.1
urtx# cat /etc/gateways
urtx#
urtx# sizer -v
HP Tru64 UNIX V5.1B (Rev. 2650); Fri Mar 20 20:19:48 CDT 2009
Things may have been different in the old
days, of course.