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 Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

Internal Network DNS Resolution Question...

Status
Not open for further replies.

spacebass5000

Programmer
Nov 26, 2000
144
US
I am having a weird problem with my internal network's name resolution. I have a name server set up to specifically deal with resolving all of our internal clients, printers, servers, etc... (I am using RedHat 7.2 and Win 98 for the majority of these machines by the way)

Let just say that on a given machine if I don't have a host file with the entry that corresponds to machineX and I ping machineX, I get this as output back from ping.

# ping machineX
PING machineX.mydomain.com (192.168.2.246) from 192.168.2.90 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.2.246: icmp_seq=0 ttl=128 time=429 usec
64 bytes from 192.168.2.246: icmp_seq=1 ttl=128 time=9.034 sec
64 bytes from 192.168.2.246: icmp_seq=2 ttl=128 time=18.060 sec
64 bytes from 192.168.2.246: icmp_seq=3 ttl=128 time=27.083 sec
64 bytes from 192.168.2.246: icmp_seq=4 ttl=128 time=36.108 sec
64 bytes from 192.168.2.246: icmp_seq=5 ttl=128 time=45.132 sec
64 bytes from 192.168.2.246: icmp_seq=6 ttl=128 time=54.157 sec
64 bytes from 192.168.2.246: icmp_seq=7 ttl=128 time=63.181 sec

(notice the pattern?)

Now when I have an entry that corresponds to machineX in my host file I receive this output:

# ping machineX
PING machineX (192.168.2.246) from 192.168.2.90 : 56(84) bytes of data.
Warning: time of day goes back, taking countermeasures.
64 bytes from machineX (192.168.2.246): icmp_seq=0 ttl=128 time=474 usec
64 bytes from machineX (192.168.2.246): icmp_seq=1 ttl=128 time=247 usec
64 bytes from machineX (192.168.2.246): icmp_seq=2 ttl=128 time=250 usec
64 bytes from machineX (192.168.2.246): icmp_seq=3 ttl=128 time=237 usec
64 bytes from machineX (192.168.2.246): icmp_seq=4 ttl=128 time=245 usec
64 bytes from machineX (192.168.2.246): icmp_seq=5 ttl=128 time=245 usec
64 bytes from machineX (192.168.2.246): icmp_seq=6 ttl=128 time=253 usec

(notice the beautiful pings?)

So basically, when I try to use a service that relies on my internal name server for name resolution I get horrible network performance. Is this a correct assumption? What does this mean to you?

I am not certain what to make of this and would love your help in the situation...

Thanks is advance!
 
That's weird. I've never seen ping times go up by nine because of name resolution.
Well do you have a DNS server on your network? If not, put one up and see how it goes.
I'm not too sure why the ping times would do that...its weird.
If anyone can answer or has a theory, please answer! ________________________________________
Check out
 
ok... this problem was indeed caused by an error in named.conf with the reverse zone info...

The person who configured the named.conf file before me had this in the file:

zone "0.2.168.192.in-addr.arpa" {
type master;
file "192.168.2.0.rev";
notify no;
};

This is incorrect! It should read like such:

zone "2.168.192.in-addr.arpa" {
type master;
file "192.168.2.0.rev";
notify no;
};

notice the 0 left off of the zone statement?
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top