hello,
the domain trello.com could not be resolved ( "dig trello.com A" fail )
when I ask the authoritative nameservers directly I get answers with decreasing TTL values.
Also the authority section list a nameserver twice, but that shouldn't be the reason.
I could resolv www.trello.com which is a CNAME. (but that doesn't help my customer because the webserver www.trello.com redirect via http to trello.com :-/
Andreas
hello,
the domain trello.com could not be resolved ( “dig trello.com A” fail )
It’s working for me, via a 1.4.16 installation.
when I ask the authoritative nameservers directly I get answers with decreasing TTL values.
But that’s somewhat, umm, special…
Curiously their servers (operated by incapsula.com) also appear to strip the RD bit from replies, contrary to RFC 1035.
kind regards,
Ray
hello,
the domain trello.com<http://trello.com> could not be resolved ( "dig trello.com<http://trello.com> A" fail )
It’s working for me, via a 1.4.16 installation.
when I ask the authoritative nameservers directly I get answers with decreasing TTL values.
They are a webacceleration service and CDN. A webacceleration service is a sort of caching proxy for HTML-pages.
Maybe their DNS-service is also a proxy and they want fast/predictable changes, so they take the original ttl from the real server and decrease it.
Ray Bellis:
It’s working for me, via a 1.4.16 installation.
I assume you haven't "use-caps-for-id: yes" enabled?
Andreas
I can’t tell - I’m not operating or running that local resolver myself, it’s just one on our LAN.
Ray
I can confirm that trello.com has a problem with 0x20. We use a quick & dirty
woraround - forward zones sending the requests to google...
~# cat /etc/unbound/unbound.conf.d/forward_zones
forward-zone:
name: trello.com.
forward-addr: 8.8.8.8
forward-addr: 8.8.4.4
You have to include the file above to the main inbound config.
Ales