The hypothesis was that named started before dnsmasq, preventing dnsmasq
from binding port 53 on 127.0.0.1. But the hypothesis is false, since
you are not running named after all.
Returning to your dig output, it can be summarized as follows.
dig s4 -> FAILURE
dig @10.1.0.4 s4 -> FAILURE
dig @10
Thomas,
there is no local named on any notebook here.
dnsmasq does not interfere with named on any of my machines.
It should actually not even be possible. As far as I am concerned, the
bind() request should return false and give an EADDRINUSE if the socket
was already bound by something.
Unles
On the affected system when it is manifesting the problem you reported
(can't resolve names), is named running locally? (In your original
submission you said that bind was running.) What role does this named
play in your network? How is it configured? What happens if you stop
this named? And th
** Changed in: dnsmasq (Ubuntu)
Status: Invalid => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998712
Title:
dnsmasq integration into name resolution broken
To manage notificati
In fact my point of view is that I have submitted all information I could
provide in reasonable time.
Give me a bunch of experiments I have to carry out, I'll spend an afternoon to
help resolve the issue
>From my point of view, I have given you more than enough input to
localise the issue (see o
I'd just like to note here before leaving this issue that the submitter
originally said that he was running bind. If bind was set up to listen
on 127.0.0.1#53 but was not correctly set up to provide name service
then I imagine that this could have interfered with the NM-controlled
dnsmasq. Explori
> Please understand that I don't have the time
OK, marking this as invalid.
** Changed in: dnsmasq (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998712
My /var/run/nm-dns-dnsmasq.conf contained
server=10.1.0.4
server=10.1.0.254
server=195.202.128.3
wolf@mbp:~$ ps -elf | grep dnsmasq
4 S nobody 25661 25624 0 80 0 - 7579 poll_s 15:20 ?00:00:00
/usr/sbin/dnsmasq --no-resolv --keep-in-foreground --no-hosts --bind-interfaces
--pid-fi
Wolf: You list problems with dnsmasq. In this report (#998712) let's
continue to discuss the name resolution failure that you originally
reported. One of the other problems you listed is being discussed in
#1003842. For the remaining problems you listed, please submit your
information to bug rep
The /etc/resolv.conf held just a reference to 127.0.0.1
# Dynamic resolv.conf(5) file for glibc resolver(3) generated by resolvconf(8)
# DO NOT EDIT THIS FILE BY HAND -- YOUR CHANGES WILL BE OVERWRITTEN
nameserver 127.0.0.1
search rsb.intern rsb.at
I copied a working version over it:
# Dynam
Wolf: In #3 you post some output but I don't know how to interpret it.
You start with a "ping s4" which yields "unknown host". You end with
"ping s4" which successfully pings. What happened in the meantime to
change the results? Did you edit something?
--
You received this bug notification bec
Wolf: Please post the FULL contents of your /etc/resolv.conf file as it
is when the reported problem occurs.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998712
Title:
dnsmasq integration into name
On 17/05/12 10:19, Wolf Rogner wrote:
> I recreated the situation by restarting the network manager.
>
> resolv.conf contains link to 127.0.0.1
> /run/nm-dns-dnsmasq.conf contained my name server already.
>
> However, even dig does not resolv correctly. Here are the results (my
> network is 10.x.
I recreated the situation by restarting the network manager.
resolv.conf contains link to 127.0.0.1
/run/nm-dns-dnsmasq.conf contained my name server already.
However, even dig does not resolv correctly. Here are the results (my
network is 10.x.x.x actually)
wolf@mbp:~$ ping s4
ping: unknown hos
** Changed in: dnsmasq (Ubuntu)
Status: New => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998712
Title:
dnsmasq integration into name resolution broken
To manage notifications
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/998712
Title:
dnsmasq integration into name resolution broken
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/dn
16 matches
Mail list logo
