DNS lookups for AWS failing with AirVPN DNS servers

[determined_weasel 0]

Hello,

 

DNS lookups to AWS seem to be failing for me, see below. It works with Google's DNS server but not using the AirVPN ones. Any ideas why?

 

DNS lookups to other websites seem to work fine.

 

:~$ nslookup sqs.eu-west-1.amazonaws.com 8.8.8.8
Server:        8.8.8.8
Address:    8.8.8.8#53

Non-authoritative answer:
sqs.eu-west-1.amazonaws.com    canonical name = eu-west-1.queue.amazonaws.com.
Name:    eu-west-1.queue.amazonaws.com
Address: 52.95.112.152

:~$ nslookup sqs.eu-west-1.amazonaws.com 10.9.100.1
Server:        10.9.100.1
Address:    10.9.100.1#53

** server can't find sqs.eu-west-1.amazonaws.com: SERVFAIL

:~$ nslookup sqs.eu-west-1.amazonaws.com 10.4.0.1
Server:        10.4.0.1
Address:    10.4.0.1#53

** server can't find sqs.eu-west-1.amazonaws.com: SERVFAIL

 

[OpenSourcerer 1435]

I think there are similarities to the IMDb case (also Amazon). I get the same error from Kitalpha. ISP resolves fine, though.

 

ViewDNS report outputs two problematic areas:

 

FAILED	Missing NS records at parent servers

Oops! It appears that the following nameserves listed at your local servers are not listed at the parent servers:

PDNS1.ultradns.net.
PDNS2.ultradns.net.
PDNS3.ultradns.org.

You should ensure that these nameservers are valid and working. If they are not, you will encounter connectivity issues with your domain.
---
FAILED	Missing NS records at local servers

Oops! It appears that the following nameserves listed at the parent servers are not listed at your local servers:

pdns1.ultradns.net.
pdns2.ultradns.net.
pdns3.ultradns.org.

You should ensure that these nameservers are valid and working. If they aren't, it can cause odd behaviour including some people not being able to access your domain.

[Staff 9973]

Hello,

 

the problem seems to be intermittently even worse: as you can see you often get SERVFAIL, i.e. a failure of the authoritative DNS servers. Normally a SERVFAIL means that the authoritative DNS server is down or refuses connections from our DNS servers, we will investigate.

 

Kind regards

[airer 0]

I have same intermittent SERVFAIL issue when trying to browse to www.amazon.com   (Other sites resolve without problems)
 

> www.amazon.com
;; Got SERVFAIL reply from 10.4.0.1, trying next server
Server:         10.4.0.1
Address:        10.4.0.1#53

** server can't find www.amazon.com: NXDOMAIN
 

> www.yahoo.com
Server:         10.4.0.1
Address:        10.4.0.1#53

Non-authoritative answer:
www.yahoo.com   canonical name = atsv2-fp-shed.wg1.b.yahoo.com.
Name:   atsv2-fp-shed.wg1.b.yahoo.com
Address: 87.248.98.8
Name:   atsv2-fp-shed.wg1.b.yahoo.com
Address: 87.248.98.7