[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
To add that, or any other, option to resolv.conf permanently, add the line options edns0 to the file /etc/resolvconf/resolv.conf.d/base and then resolvconf will include it in the resolv.conf that it generates. ** Changed in: dnsmasq (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
To add that, or any other, option to resolv.conf permanently, add the line options edns0 to the file /etc/resolvconf/resolv.conf.d/base and then resolvconf will include it in the resolv.conf that it generates. ** Changed in: dnsmasq (Ubuntu) Status: New = Invalid -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
Hi. I don't see how resolvconf could be responsible for this problem. Initial observation: it seems that dig gets the correct answer from dnsmasq when it supplies the additional option udp:1280, but the glibc resolver doesn't get the right answer from dnsmasq when it fails to supply that option. Reassigning to dnsmasq. ** Package changed: resolvconf (Ubuntu) = dnsmasq (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
Hi. I don't see how resolvconf could be responsible for this problem. Initial observation: it seems that dig gets the correct answer from dnsmasq when it supplies the additional option udp:1280, but the glibc resolver doesn't get the right answer from dnsmasq when it fails to supply that option. Reassigning to dnsmasq. ** Package changed: resolvconf (Ubuntu) = dnsmasq (Ubuntu) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
Thanks, I was hoping for some help to find the right place to report this. I poked around some more, and I found out what the problem was. First of all, my wireless router was confused. I rebooted it, and then everything started working again. I did some debugging before I rebooted it, though, and the reason for the partial failure situation was that EDNS0 wasn't specified in the queries sent by Ubuntu, but dig specifies it by default (as well as the AD flag, but I don't think that's relevant). A partial result should have been given by the DNS server (on the wireless router), or it should have truncated the reply to force a TCP retry by the client. (Now that everything works, it trims down the Additional section to fit the response.) To confirm, I ran dig like this, and these queries failed on my confused router: dig +noedns +noadflag @127.0.1.1 www.sciencedaily.com So if Ubuntu had in fact set EDNS0 in the query, it would have worked. Falling back to TCP presumably wasn't an option since no malformed/truncated result was received first. Feel free to close this issue if my router's behaviour was completely unacceptable and should cause failure on the client side. If it ought to have been handled better by Ubuntu, however, this may have been an interesting corner case for debugging. Let me know if you need anything else. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
Thanks, I was hoping for some help to find the right place to report this. I poked around some more, and I found out what the problem was. First of all, my wireless router was confused. I rebooted it, and then everything started working again. I did some debugging before I rebooted it, though, and the reason for the partial failure situation was that EDNS0 wasn't specified in the queries sent by Ubuntu, but dig specifies it by default (as well as the AD flag, but I don't think that's relevant). A partial result should have been given by the DNS server (on the wireless router), or it should have truncated the reply to force a TCP retry by the client. (Now that everything works, it trims down the Additional section to fit the response.) To confirm, I ran dig like this, and these queries failed on my confused router: dig +noedns +noadflag @127.0.1.1 www.sciencedaily.com So if Ubuntu had in fact set EDNS0 in the query, it would have worked. Falling back to TCP presumably wasn't an option since no malformed/truncated result was received first. Feel free to close this issue if my router's behaviour was completely unacceptable and should cause failure on the client side. If it ought to have been handled better by Ubuntu, however, this may have been an interesting corner case for debugging. Let me know if you need anything else. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
To get Ubuntu to send EDNS0 queries, I can set this in resolv.conf: options edns0 That might work around this bug in my router in the future. And in case anyone is interested, the wireless router is a Netgear WNR2000v5. I think this case can be closed. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 1466608] Re: Unable to resolve domains with large EDNS0 replies
To get Ubuntu to send EDNS0 queries, I can set this in resolv.conf: options edns0 That might work around this bug in my router in the future. And in case anyone is interested, the wireless router is a Netgear WNR2000v5. I think this case can be closed. -- You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to dnsmasq in Ubuntu. https://bugs.launchpad.net/bugs/1466608 Title: Unable to resolve domains with large EDNS0 replies To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/1466608/+subscriptions -- Ubuntu-server-bugs mailing list Ubuntu-server-bugs@lists.ubuntu.com Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/ubuntu-server-bugs
