[Bug 991308] Re: Dnsmasq fails to resolve if any upstream nameserver is unreachable
Appologies, this is no longer an issue for me in 12.10. -- 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/991308 Title: Dnsmasq fails to resolve if any upstream nameserver is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/991308/+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 991308] Re: Dnsmasq fails to resolve if any upstream nameserver is unreachable
I may need to look in logs, I'm not 100% it's lookup that's failing it. Just figured I'd mention it here. -- 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/991308 Title: Dnsmasq fails to resolve if any upstream nameserver is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/991308/+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 991308] Re: DNS Querying fails if any DNS server is unreachable
aparently I spoke to soon =( -- 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/991308 Title: DNS Querying fails if any DNS server is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/991308/+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 991308] Re: DNS Querying fails if any DNS server is unreachable
Yes, it happens with dnsmasq by itself. However it appears that dnsmasq is caching the result, so when it sees a good one it will keep serving it. Here is some example output from the syslog: Jun 22 13:42:18 archon dnsmasq[9635]: started, version 2.59 cachesize 150 Jun 22 13:42:18 archon dnsmasq[9635]: compile time options: IPv6 GNU-getopt DBus i18n DHCP TFTP conntrack IDN Jun 22 13:42:18 archon dnsmasq[9635]: reading /var/run/dnsmasq/resolv.conf Jun 22 13:42:18 archon dnsmasq[9635]: using nameserver 75.75.76.76#53 Jun 22 13:42:18 archon dnsmasq[9635]: using nameserver 75.75.75.75#53 Jun 22 13:42:18 archon dnsmasq[9635]: read /etc/hosts - 8 addresses Jun 22 13:42:18 archon dnsmasq[9635]: query[SOA] local from 127.0.0.1 Jun 22 13:42:18 archon dnsmasq[9635]: forwarded local to 75.75.75.75 Jun 22 13:42:18 archon dnsmasq[9635]: forwarded local to 75.75.76.76 Jun 22 13:42:18 archon dnsmasq[9635]: query[SOA] local from 127.0.0.1 Jun 22 13:42:18 archon dnsmasq[9635]: forwarded local to 75.75.75.75 .. Jun 22 13:43:09 archon dnsmasq[9635]: query[A] slashdot.org from 127.0.0.1 Jun 22 13:43:09 archon dnsmasq[9635]: forwarded slashdot.org to 75.75.75.75 Jun 22 13:43:09 archon dnsmasq[9635]: reply slashdot.org is 216.34.181.45 Jun 22 13:43:26 archon dnsmasq[9635]: query[A] slashdot.org from 127.0.0.1 Jun 22 13:43:26 archon dnsmasq[9635]: cached slashdot.org is 216.34.181.45 .. Jun 22 13:46:00 archon dnsmasq[9814]: query[A] gmail.com from 127.0.0.1 Jun 22 13:46:00 archon dnsmasq[9814]: forwarded gmail.com to 75.75.75.75 Jun 22 13:46:00 archon dnsmasq[9814]: forwarded gmail.com to 75.75.76.76 Jun 22 13:46:05 archon dnsmasq[9814]: query[A] gmail.com from 127.0.0.1 Jun 22 13:46:05 archon dnsmasq[9814]: forwarded gmail.com to 75.75.75.75 Jun 22 13:46:05 archon dnsmasq[9814]: forwarded gmail.com to 75.75.76.76 Jun 22 13:46:10 archon dnsmasq[9814]: query[A] gmail.com from 127.0.0.1 Jun 22 13:46:10 archon dnsmasq[9814]: forwarded gmail.com to 75.75.75.75 Jun 22 13:46:10 archon dnsmasq[9814]: forwarded gmail.com to 75.75.76.76 the last was generated by dig @localhost gmail.com -- 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/991308 Title: DNS Querying fails if any DNS server is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/991308/+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 991308] Re: DNS Querying fails if any DNS server is unreachable
Just noticed this as well: http://mydeviceinfo.comcast.net/device.php?tier=-1devid=298e=0d3=0s=nso=0sc=1546 To quote the red bit at top: Comcast has identified a software defect on the Arris TG852 and TG862, which may cause problems for a small number of users attempting to use third party DNS services. Arris and Comcast are working to correct this issue and will deploy updated device firmware to resolve the issue. If a customer does not wish to wait for the updated firmware, the customer may email us at we_can_h...@cable.comcast.com and a replacement device will be provided at no cost to the customer. Although I am using the default Comcast provided DNS servers of 75.75.75.75 and 75.75.76.76, so not sure this would affect it or not. -- 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/991308 Title: DNS Querying fails if any DNS server is unreachable To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/dnsmasq/+bug/991308/+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 542005] Re: faulty symlinks on mounted samba volumes
I checked, You're right. It confused me that this have been changed just like that in the next version (for me) . But the question is still there: Why can't unix extension and wide links work together? I know it a security hole, but I really need this option one way or another. -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 542005] Re: faulty symlinks on mounted samba volumes
I don't get it what example you're exactly expecting but here is the full story: I have 4 software raid arrays of 2 hard drives. (So md0 is the system's, md1 and md2 are storages, and md3 is for a kvm guest.) Symlinks already existed and newly created work properly on md1, only inside the partition despite who owns them. Symlinks pointed to somewhere on md0 or md2 just don't, not matter where they are or which user owns them. Linux clients don't see the owner (not even numbers) and the attributes so ls -l shows only ? marks for every details. Windows clients just say access denied. In case it matters the filesystems on the system is ext3, on the storages are ext4. As far as I know that md1 ain't different in any way. Only Samba's having trouble with symlinks... For now I've turned off unix extensions, I don't really need it. -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 542005] Re: faulty symlinks on mounted samba volumes
Of course, even more: smb.conf: http://pastebin.com/96W66mun Versions: libpam-smbpass 2:3.4.0-3ubuntu5.6 libsmbclient 2:3.4.0-3ubuntu5.6 libwbclient0 2:3.4.0-3ubuntu5.6 samba 2:3.4.0-3ubuntu5.6 samba-common 2:3.4.0-3ubuntu5.6 samba-common-bin 2:3.4.0-3ubuntu5.6 samba-doc 2:3.4.0-3ubuntu5.6 smbclient 2:3.4.0-3ubuntu5.6 smbfs 2:3.4.0-3ubuntu5.6 winbind 2:3.4.0-3ubuntu5.6 For mount I used mount.cifs (from fstab, and only with 'username' and 'password' options), also Nautilus and WinXP - Win7. None of them works. As I said before the weirdest thing is that symlinks on one particular filesystem/partition works but all the others don't get any details about symlinks (only) viasamba... -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 542005] Re: faulty symlinks on mounted samba volumes
** Changed in: samba (Ubuntu) Status: Incomplete = Confirmed -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 542005] Re: faulty symlinks on mounted samba volumes
I've experienced this (or something same) recently too on 9.10 server, Samba 3.4.0. I'm not sure since when is this lasting but I think upgrading the devicekit-* package today might caused it.? That was the last thing I did before noticed this bug... It only affects symlinks and only on certain filesystems with unix extensions enabled. Without unix extensions symlinks works everywhere, otherwise only on one of all my file systems. The file systems are on software raid arrays and the're ext4. -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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 542005] Re: faulty symlinks on mounted samba volumes
In my case wide links is disabled ever since I use Samba. The ordinary symlink doesn't work if unix extension is enabled at the same time. By doesn't work I mean they don't have any file permissions or even details just '?' marks instead. It's been working until yesterday... I'll be more specific: On the local system every symlink work. On the drive named md1 there is no sign of this bug via Samba either (unix extension enabled too). But on the drive md3 and sde1 symlinks don't work via Samba. I ran e2fsck (-f) and It found nothing. All of the mentioned drives has ext4 filesystem which were updated from ext3. I'm only guessing this is a Samba only bug... -- faulty symlinks on mounted samba volumes https://bugs.launchpad.net/bugs/542005 You received this bug notification because you are a member of Ubuntu Server Team, which is subscribed to samba in ubuntu. -- 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
