This can be caused by upstream resolvers using DNSSEC whilst the client
doesn't. I've just dealt with a user facing this issue.
The solution was to use DNSSEC with dig:
dig +dnssec host
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: glibc (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/327364
Title:
DNS
The same problem resolving host vk.com
DNS server is bind9 from Debian squeeze.
All configuration files are available to read and edit.
Some kind of similar issue, but is was fixed long ago
https://bugzilla.redhat.com/show_bug.cgi?id=161181
** Bug watch added: Red Hat Bugzilla #161181
Sorry, in my case it was an wrong firewall configuration
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/327364
Title:
DNS lookup fails if there are too many records records (e.g.
I have same bug. All applications can not resolve some DNS names. only
'dig' with '+ignore' can resolve such DNS names:
$ dig vkontakte.ru
;; Truncated, retrying in TCP mode.
;; Connection to 10.10.10.2#53(10.10.10.2) for vkontakte.ru failed: connection
refused.
$dig +ignore vkontakte.ru
;
A workaround for this problem is to append the lines:
nameserver 208.67.222.222
nameserver 208.67.220.220
To your /etc/resolv.conf
These are the domain servers from the openDNS free dns servers
--
DNS lookup fails if there are too many records records (e.g.
smtp.googlemail.com)
I believe I have the same problem, but its not happening with
smtp.google.com, but with www.google.com. I have this output for dig:
pa...@warifaifa:~$dig www.google.com
;; Truncated, retrying in TCP mode.
;; Connection to 192.168.0.1#53(192.168.0.1) for www.google.com failed:
connection refused.
