Project

General

Profile

Actions
Copy link

Bug #3256

closed

dnsmasq replying with incorrect address

Added by Chris Craft over 11 years ago. Updated over 10 years ago.

Status:
Rejected
Priority:
High
Assignee:
-
Category:
DNS Forwarder
Target version:
-
Start date:
10/08/2013
Due date:
% Done:

0%

Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
2.1
Affected Architecture:
amd64

Description

Using nslookup from multiple windows 7 clients, got a reply of another DHCP client's address for multiple queries of two different other DHCP client names. (Example output in files) Restarting dnsmasq from Status:Services fixes the issue for a while. Trying to determine if the iPhone DHCP client tickles this bug.

Files

pfsense21dnsmasq-bug.txt (914 Bytes) pfsense21dnsmasq-bug.txt example before and after output of nslookup from a windows 7 machine Chris Craft, 10/08/2013 05:15 PM
Actions
Copy link
 #1

Updated by Chris Craft over 11 years ago

Not the iphone...

Actions
Copy link
 #2

Updated by Chris Craft over 11 years ago

Seems to go back to normal/proper responses after an unknown amount of time as well.

Actions
Copy link
 #3

Updated by Renato Botelho over 11 years ago

Is the issue still happening?

Actions
Copy link
 #4

Updated by Chris Buechler over 10 years ago

  • Status changed from New to Rejected

nothing to go on here, need a replicable scenario of where it's not working. It works fine in general.

Actions
Copy link

Also available in: Atom PDF