• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 375
  • Last Modified:

NetWare 6 box can't ping internal addresses

When we ping any internal address from our NetWare 6 box, which is running DNS, the ping goes out to our website. We can do an nslookup of all of the hosts from the server no problem. The server can be pinged from anywhere internally. Where would it be pulling the setting that is sending EVERY ping from this server and this server only to an outside address?

0
sgeye
Asked:
sgeye
  • 3
  • 2
1 Solution
 
sgeyeAuthor Commented:
Just to be clear

Lets call the problematic server PROBLEM and our primary NetWare server NETWARE

From PROBLEM if you do nslookup NETWARE, it returns the correct address
From PROBLEM if you do ping NETWARE, it goes to a different address

The only DNS entry pointing to our website address is the WWW entry, but I don't see why that would come into play here...
0
 
ShineOnCommented:
Do you have two NICs, one public, one private, or are you multihoming private and public IP on the same NIC, or is it one NIC with only a private IP, or one NIC with only a public IP?

If you've got multiple interfaces, physical or not, the first one bound is likely to be the one that the PING is going out on.  If that's the case, you also need to look at how the rest of your networking configuration is set up - routing, filters, etc.
0
 
sgeyeAuthor Commented:
It only had 1 IP address, there was however a public IP NATed to it. We were able to get it working by rebooting the server without DNS turned on, then starting DNS manually.. not quite sure what caused it, and a plain reboot didn't make it go away..
0
 
ShineOnCommented:
It's NetWare, not Windoze - a reboot shouldn't have been necessary >at all<.

Question - is your internal domain the same as your public domain?   How is your DNS configured, both public and private, as regards DNS zone info, primary authoritative, zone transfer, etc?

It sounds like your server "problem" was getting its DNS info mixed up somehow, because if it works OK just by delaying load of NAMED.NLM, that makes me think maybe it had something incorrect in its internal DNS cache due to what it was getting or looking for during startup post-NAMED-load that's not getting into cache because of the delayed load of NAMED.

Often, WWW is equated with the domain in public DNS, so if you ping "mycompany.com" it'll resolve the same address as a ping of "www.mycompany.com."  If you're looking something up, you'll look for the name server for the domain.  If that's cached as the public "mycompany.com" instead of the internal name server, that's where it'll look.

If both the public DNS and your private DNS consider themselves primary authoritative for your "mycompany.com" zone, how things are defined in each or either can make a big difference, and an NSLOOKUP will, AFAIK, directly query the database, while PING might resolve using the DNS cache first.  Not sure on that, just a theory, but without seeing the code it's as reasonable as any. ;)

Hard to say more without knowing all the details of how your DNS is structured, but those are my thoughts based on what you've said so far.  

Also check your "sys:\etc\resolv.cfg" - it should have your domain, plus the server's own IP address listed first in the resolver order, followed by any secondary servers or forwarder resolvers.  It should look kinda like this:

domain mycompany.com
nameserver <IP.address.of.PROBLEM>
nameserver <IP.address.of.secondary/forwarder>

0
 
ShineOnCommented:
So, what was it?  I threw out so many possibilities there...
0

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now