[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Dns sometimes fails using Google DNS / automatic dnssec
- Subject: Dns sometimes fails using Google DNS / automatic dnssec
- From: david at mailplus.nl (MailPlus| David Hofstee)
- Date: Thu, 15 Nov 2012 15:12:23 +0100
We've been seeing automatic RRSIG records on Google DNS lately, the 184.108.40.206 en 220.127.116.11. They are not always provided. They cause problems for some of our customers in a weird way I cannot explain. For them these records do not resolve but I cannot reproduce it.
So when I run dig command
dig @18.104.22.168 m1.mailplus.nl
it often provides the RRSIG record (but e.g. the TXT record will not be signed). I've heard that DNS may fall back to TCP and/or may be filtered by firewalls if UDP is over 512 bytes. However, the request is not that long, about 200 bytes if I interpret the answer correctly.
Can someone come up with a good explanation why a tiny percentage of our customers cannot resolve (some of) our domains?
Btw, our nameservers (transip.nl) only provide DNSSEC records if explicitly asked. What is standard here?