Bug 10436 – Funnies with ping and bogus nameservers at resolv.conf

Bug 10436 - Funnies with ping and bogus nameservers at resolv.conf

Summary:	Funnies with ping and bogus nameservers at resolv.conf

Status:	CLOSED NOTABUG

Aliases:	None

Product:	Red Hat Linux
Classification:	Retired
Component:	iputils (Show other bugs)
Sub Component:
Version:	6.2
Hardware:	i386 Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Crutcher Dunnavant
QA Contact:
Docs Contact:

URL:
Whiteboard:
Keywords:

Duplicates:	10659 11048 11700 16138 (view as bug list)
Depends On:
Blocks:	11313
	Show dependency tree / graph

Reported:	2000-03-30 06:15 EST by kauppi
Modified:	2008-05-01 11:37 EDT (History)
CC List:	0 users

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2000-03-31 11:32:52 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description kauppi 2000-03-30 06:15:37 EST

/etc/resolv.conf:
search somedomain.com
nameserver 1.2.3.4 (Some bogus address where bind isn't running)

eth0 is configured as 192.168.0.2/24, default gw 192.168.0.1

ping 192.168.0.1 reports no replies or each reply is delayed by 4 seconds
(first like 2 ms, next 4030, next 8030 etc) even though tcpdump shows
normal operation (echo request and echo reply right after request). ping -n
192.168.0.1 works normally and reports correct times.

Tested on i386 platform, iputils-20000121-2

Comment 1 Tim Waugh 2000-03-31 11:32:59 EST

This is as documented in the man page.  You've always needed to specify -n for
numeric output, modulo a bug in what the default was that is fixed in this
release.

(But yes, I preferred the old behaviour too.)

Comment 2 Tim Waugh 2000-06-14 13:19:31 EDT

*** Bug 10659 has been marked as a duplicate of this bug. ***

Comment 3 Tim Waugh 2000-06-14 13:20:37 EDT

*** Bug 11048 has been marked as a duplicate of this bug. ***

Comment 4 Tim Waugh 2000-06-14 13:21:09 EDT

*** Bug 11700 has been marked as a duplicate of this bug. ***

Comment 5 Bill Nottingham 2000-08-14 01:11:32 EDT

*** Bug 16138 has been marked as a duplicate of this bug. ***

Note You need to log in before you can comment on or make changes to this bug.