domains not resolving in Google DNS, but are elsewhere

[Johnny Cison]

Several domains are not resolving via 8.8.8.8 or 8.8.4.4, but are
resolving correctly via Level 3 and OpenDNS. The domains are as
follow:

gmdrives.com
stlouisgmcdealers.com
stlouisbuickdealers.com


Below are some of the lookups I've run:

> nslookup gmdrives.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find gmdrives.com: SERVFAIL


> nslookup stlouisgmcdealers.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find stlouisgmcdealers.com: SERVFAIL


> nslookup stlouisbuickdealers.com 8.8.8.8
Server: 8.8.8.8
Address: 8.8.8.8#53

** server can't find stlouisbuickdealers.com: SERVFAIL


> nslookup gmdrives.com 4.2.2.1
Server: 4.2.2.1
Address: 4.2.2.1#53

Non-authoritative answer:
Name: gmdrives.com
Address: 67.217.38.210


> nslookup stlouisgmcdealers.com 4.2.2.1
Server: 4.2.2.1
Address: 4.2.2.1#53

Non-authoritative answer:
Name: stlouisgmcdealers.com
Address: 67.217.38.219


> nslookup stlouisbuickdealers.com 4.2.2.1
Server: 4.2.2.1
Address: 4.2.2.1#53

Non-authoritative answer:
Name: stlouisbuickdealers.com
Address: 67.217.38.219


> nslookup gmdrives.com 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: gmdrives.com
Address: 67.217.38.210


> nslookup stlouisgmcdealers.com 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: stlouisgmcdealers.com
Address: 67.217.38.219


> nslookup stlouisbuickdealers.com 208.67.222.222
Server: 208.67.222.222
Address: 208.67.222.222#53

Non-authoritative answer:
Name: stlouisbuickdealers.com
Address: 67.217.38.219


> dig @8.8.8.8 gmdrives.com

; <<>> DiG 9.7.3-P3 <<>> @8.8.8.8 gmdrives.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2628
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;gmdrives.com. IN A

;; Query time: 1085 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Feb 20 15:44:32 2012
;; MSG SIZE rcvd: 30


> dig @208.67.222.222 gmdrives.com

; <<>> DiG 9.7.3-P3 <<>> @208.67.222.222 gmdrives.com
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 55917
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;gmdrives.com. IN A

;; ANSWER SECTION:
gmdrives.com. 14336 IN A 67.217.38.210

;; Query time: 20 msec
;; SERVER: 208.67.222.222#53(208.67.222.222)
;; WHEN: Mon Feb 20 15:44:40 2012
;; MSG SIZE rcvd: 46

Please let me know if you need any additional information!

[Paul S. R. Chisholm]

Thanks for the report, Johnny. These three domains are all served by
the same "pair" of nameservers:

$ dig +nocmd +noquestion +nostats @l.gtld-servers.net stlouisbuickdealers.com
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 53517
;; flags: qr rd; QUERY: 1, ANSWER: 0, AUTHORITY: 2, ADDITIONAL: 2
;; WARNING: recursion requested but not available

;; AUTHORITY SECTION:
stlouisbuickdealers.com. 172800 IN NS ns1.gmdrives.com.
stlouisbuickdealers.com. 172800 IN NS ns2.gmdrives.com.

;; ADDITIONAL SECTION:
ns1.gmdrives.com. 172800 IN A 67.217.38.203
ns2.gmdrives.com. 172800 IN A 67.217.38.203

The nameserver 67.217.38.203 has never responded to a query from
Google Public DNS's servers:

http://code.google.com/speed/public-dns/faq.html#locations

I'll contact the administrator for 67.217.38.203. If that's you,
please unblock the servers listed at the URL above.

Hope this resolves your problem quickly. --PSRC

[Dariusz Więckiewicz]

I have better situation.
In all DNS services my domain kasiek.art.pl has updated and latest dns
entry, but Google DNS has still entry from 2009!!!!
Sometimes it changes, but after couple days its back to entry from
year 2009!

How and where I need to complain to fix it?

[Paul S. R. Chisholm]

Thanks for your report, Dariusz.

kasiek.art.pl is served by four nameservers. Three of them return what
you probably consider the latest entry, but one of them returs what
you probably consider the old entry:

$ for i in fns1.42.pl fns2.42.pl ns0.xname.org ns1.xname.org; do echo
$i:::; dig @$i +norec +short kasiek.art.pl; done
fns1.42.pl:::
78.46.76.247
fns2.42.pl:::
78.46.76.247
ns0.xname.org:::
78.46.76.247
ns1.xname.org:::
78.131.152.140

Please talk to your DNS hoster, and ask them to either not list that
last nameserver, or have that last nameserver return the new entry.

Hope this helps. --PSRC

> --
> ========================================================
> You received this message because you are subscribed to the Google
> Groups "public-dns-discuss" group.
> To post to this group, send email to public-dn...@googlegroups.com
> To unsubscribe from this group, send email to
> public-dns-disc...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/public-dns-discuss?hl=en
> For more information on Google Public DNS, please visit
> http://code.google.com/speed/public-dns
> ========================================================

[Andrzej Swietek]

Dariusz,

Please see the following report about your domain:
http://www.intodns.com/kasiek.art.pl

Looks like your authoritative slave DNS servers are out of sync with master
server, hence discrepancy in DNS records when querying:

NSs have same SOA serial

Looks like your nameservers do not agree on the SOA serial. Ths SOA records
as reported by your nameservers:
178.33.255.252 -> 2009041302
79.98.145.34 -> 1329052323
195.80.237.194 -> 1329052323
195.234.42.1 -> 1329052323
This can cause some serious problems that is why you should fix this asap.

Hope this helps. --PSRC

On Tue, Feb 21, 2012 at 4:50 AM, Dariusz Wieckiewicz

[appdata...@gmail.com]

Hello,

This is a pretty old post but we got the same problem as Johnny had. Some of our domains are not resolving via Google. A few are:

schipperenco.com

neumannenvettin.com

vega-slim.com

vetimpleg.com

They all give a servFail as lookup error. 

Best Regards,

Marc Massar

Wijtec

Op maandag 20 februari 2012 21:48:09 UTC+1 schreef Johnny Cison:

[Yunhong Gu]

The names either do not exist or fail DNSSEC validation. Please use dnsviz.net and intodns.com to debug.

Thanks

Yunhong

--

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
 

---

You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

[appdata...@gmail.com]

Thanks for your fast response. I will check the DNSSEC validation.

Marc

Op vrijdag 23 augustus 2013 15:26:02 UTC+2 schreef Yunhong Gu:

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
 
---
You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-discuss+unsub...@googlegroups.com.

[ka...@shuckwebdesign.com]

I know this is an old thread but doesn't, but I couldn't find a good answer.  Google DNS can't resolve www.sugarshackcandles.com or sugarshackcandles.com  they get the following with an nslookup:

c:\>nslookup www.sugarshackcandles.com 8.8.4.4
Server:  google-public-dns-b.google.com
Address:  8.8.4.4

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.
*** Request to google-public-dns-b.google.com timed-out

I looked here to diagnose: 
http://www.whatsmydns.net/#A/sugarshackcandles.com
http://dnscheck.pingdom.com/?domain=sugarshackcandles.com
http://www.intodns.com/sugarshackcandles.com

I got one entry in intodns.com that said www couldn't be resolve, so I logged into my host and changed www from a CNAME to A record.   Otherwise most of the other entries were fine or about glue records.

Ironically the ISP of the company who owns the website, uses Google's public DNS servers for their DNS, so they could not get to their own website today. 

It is ONLY google's DNS that doesnt respond, level 3 works and other ISPs seem to work as well.  Any thoughts on this?

[MinJae Hwang]

sugarshackcandles.com is using Go Daddy nameservers. Google Public DNS is having on-going outage with Go Daddy nameservers. We are trying our best to solve this problem.

[alexandr...@gmail.com]

reg.entensys.com is not resolved at 8.8.8.8 if requested from Russia. It works correctly from other regions.

nslookup reg.entensys.com. 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find reg.entensys.com: SERVFAIL

Please check what this can be.

[alli...@gmail.com]

We have same issue with our domain reg.entensys.com 8.8.8.8 - resolve it rarely.

[Shen Wan]

Hi,

I just checked and all of our servers resolve the domain fine (into 46.137.76.46). Is this still an issue for you? If so, please follow https://developers.google.com/speed/public-dns/docs/using#troubleshooting to diagnose and provide us your result if you still need help.

Thanks!

[alli...@gmail.com]

it was a godaddy's issue. they suck pretty bad.
thanks for your answer anyway :)

четверг, 10 апреля 2014 г., 22:56:50 UTC+7 пользователь Shen Wan написал:

[josk...@gmail.com]

Hi,

I have a similar issue with one of our domains.  From time to time domain www.sexinpublic.ch (yes I know...)   is not resolvable from Spain, Finland and now Switzerland by 8.8.8.8.

All online tools are confirming that domain is properly set up.


Any help is appreciated..

[sa...@coins-e.com]

Hey Shen,

Can you take a look at www.Coins-e.com? It's not working on google DNS and I've contacted godaddy and they say the issue seems to be with google. 

[sa...@coins-e.com]

46.137.76.46 is an amazon dns... we are having issues with 8.8.8.8 and 8.8.4.4 - the domain is not being resolved. Please help this is an urgent issue for us :/

More info below:

diego ~ $ /usr/sbin/traceroute -n -w 2 -q 2 -m 30 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 52 byte packets

 1  192.168.2.1  4.318 ms  1.500 ms

 2  64.230.200.169  7.623 ms  7.890 ms

 3  64.230.107.144  6.197 ms  6.122 ms

 4  64.230.97.157  6.841 ms

    64.230.97.159  6.828 ms

 5  * *

 6  216.239.47.114  18.825 ms

    209.85.255.232  10.799 ms

 7  216.239.46.160  21.051 ms  19.069 ms

 8  72.14.238.104  38.724 ms

    209.85.241.22  31.991 ms

 9  216.239.43.217  39.152 ms

    216.239.46.191  31.842 ms

10  * *

11  8.8.8.8  50.107 ms  30.006 ms

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 coins-e.com.

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44511

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; Query time: 67 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Mon Jun  2 10:13:27 2014

;; MSG SIZE  rcvd: 29

dig @8.8.8.8 www.coins-e.com. +cd

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 www.coins-e.com. +cd

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30604

;; flags: qr rd ra cd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;www.coins-e.com. IN A

;; ANSWER SECTION:

www.coins-e.com. 3599 IN CNAME ghs-svc-https-c327.ghs-ssl.googlehosted.com.

ghs-svc-https-c327.ghs-ssl.googlehosted.com. 299 IN A 72.14.246.73

;; Query time: 113 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Mon Jun  2 10:14:02 2014

;; MSG SIZE  rcvd: 103

diego ~ $ dig coins-e.com. @4.2.2.1

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @4.2.2.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59266

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 138 msec

;; SERVER: 4.2.2.1#53(4.2.2.1)

;; WHEN: Mon Jun  2 10:15:14 2014

;; MSG SIZE  rcvd: 93

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @4.2.2.2

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59835

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 34 msec

;; SERVER: 4.2.2.2#53(4.2.2.2)

;; WHEN: Mon Jun  2 10:15:31 2014

;; MSG SIZE  rcvd: 93

diego ~ $ dig coins-e.com. @208.67.222.222

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @208.67.222.222

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44562

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 40 msec

;; SERVER: 208.67.222.222#53(208.67.222.222)

;; WHEN: Mon Jun  2 10:15:50 2014

;; MSG SIZE  rcvd: 93

diego ~ $ dig coins-e.com. @208.67.222.220

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @208.67.222.220

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59353

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 34 msec

;; SERVER: 208.67.222.220#53(208.67.222.220)

;; WHEN: Mon Jun  2 10:16:10 2014

;; MSG SIZE  rcvd: 93

On Thursday, April 10, 2014 11:56:50 AM UTC-4, Shen Wan wrote:

[sa...@coins-e.com]

Still a problem... Below is my diagnostic. Problem when trying to connect vis 8.8.8.8 and 8.8.4.4. Seems like an issue on googles end not resolving our DNS

[2014-06-02, 10:13:05 AM] Diego Dominguez: diego ~ $ /usr/sbin/traceroute -n -w 2 -q 2 -m 30 8.8.8.8

traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 52 byte packets

 1  192.168.2.1  4.318 ms  1.500 ms

 2  64.230.200.169  7.623 ms  7.890 ms

 3  64.230.107.144  6.197 ms  6.122 ms

 4  64.230.97.157  6.841 ms

    64.230.97.159  6.828 ms

 5  * *

 6  216.239.47.114  18.825 ms

    209.85.255.232  10.799 ms

 7  216.239.46.160  21.051 ms  19.069 ms

 8  72.14.238.104  38.724 ms

    209.85.241.22  31.991 ms

 9  216.239.43.217  39.152 ms

    216.239.46.191  31.842 ms

10  * *

11  8.8.8.8  50.107 ms  30.006 ms

[2014-06-02, 10:13:36 AM] Diego Dominguez: diego ~ $ dig @8.8.8.8 coins-e.com.

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 coins-e.com.

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 44511

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; Query time: 67 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Mon Jun  2 10:13:27 2014

;; MSG SIZE  rcvd: 29

[2014-06-02, 10:14:54 AM] Diego Dominguez: dig @8.8.8.8 www.coins-e.com. +cd

; <<>> DiG 9.8.3-P1 <<>> @8.8.8.8 www.coins-e.com. +cd

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 30604

;; flags: qr rd ra cd; QUERY: 1, ANSWER: 2, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;www.coins-e.com. IN A

;; ANSWER SECTION:

www.coins-e.com. 3599 IN CNAME ghs-svc-https-c327.ghs-ssl.googlehosted.com.

ghs-svc-https-c327.ghs-ssl.googlehosted.com. 299 IN A 72.14.246.73

;; Query time: 113 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Mon Jun  2 10:14:02 2014

;; MSG SIZE  rcvd: 103

[2014-06-02, 10:15:21 AM] Diego Dominguez: diego ~ $ dig coins-e.com. @4.2.2.1

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @4.2.2.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59266

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 138 msec

;; SERVER: 4.2.2.1#53(4.2.2.1)

;; WHEN: Mon Jun  2 10:15:14 2014

;; MSG SIZE  rcvd: 93

[2014-06-02, 10:15:39 AM] Diego Dominguez: diego ~ $ dig coins-e.com. @4.2.2.2

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @4.2.2.2

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59835

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 34 msec

;; SERVER: 4.2.2.2#53(4.2.2.2)

;; WHEN: Mon Jun  2 10:15:31 2014

;; MSG SIZE  rcvd: 93

[2014-06-02, 10:16:02 AM] Diego Dominguez: diego ~ $ dig coins-e.com. @208.67.222.222

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @208.67.222.222

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 44562

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 40 msec

;; SERVER: 208.67.222.222#53(208.67.222.222)

;; WHEN: Mon Jun  2 10:15:50 2014

;; MSG SIZE  rcvd: 93

[2014-06-02, 10:16:21 AM] Diego Dominguez: diego ~ $ dig coins-e.com. @208.67.222.220

; <<>> DiG 9.8.3-P1 <<>> coins-e.com. @208.67.222.220

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 59353

;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;coins-e.com. IN A

;; ANSWER SECTION:

coins-e.com. 600 IN A 216.239.32.21

coins-e.com. 600 IN A 216.239.34.21

coins-e.com. 600 IN A 216.239.36.21

coins-e.com. 600 IN A 216.239.38.21

;; Query time: 34 msec

;; SERVER: 208.67.222.220#53(208.67.222.220)

;; WHEN: Mon Jun  2 10:16:10 2014

;; MSG SIZE  rcvd: 93

On Thursday, April 10, 2014 11:56:50 AM UTC-4, Shen Wan wrote:

[Saif Altimimi]

The IP 46.137.76.46 points to amazon... am I mistaken? We're using 8.8.8.8 and 8.8.4.4 and it does not seem to be working.

--

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

---

You received this message because you are subscribed to a topic in the Google Groups "public-dns-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/public-dns-discuss/7Dd4pzBfpZA/unsubscribe.
To unsubscribe from this group and all its topics, send an email to public-dns-disc...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Shen Wan]

This is because the domain fails DNSSEC validation. Please enter your domain at dnsviz.net for an explanation: http://dnsviz.net/d/coins-e.com/dnssec/

On Monday, June 2, 2014 11:49:52 AM UTC-4, Saif Altimimi wrote:

The IP 46.137.76.46 points to amazon... am I mistaken? We're using 8.8.8.8 and 8.8.4.4 and it does not seem to be working.

On Mon, Jun 2, 2014 at 9:49 AM, <sa...@coins-e.com> wrote:

Hey Shen,

Can you take a look at www.Coins-e.com? It's not working on google DNS and I've contacted godaddy and they say the issue seems to be with google. 

On Thursday, April 10, 2014 11:56:50 AM UTC-4, Shen Wan wrote:

Hi,

I just checked and all of our servers resolve the domain fine (into 46.137.76.46). Is this still an issue for you? If so, please follow https://developers.google.com/speed/public-dns/docs/using#troubleshooting to diagnose and provide us your result if you still need help.

Thanks!

On Thursday, April 10, 2014 5:24:24 AM UTC-4, alli...@gmail.com wrote:

We have same issue with our domain reg.entensys.com 8.8.8.8 - resolve it rarely.

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.

To post to this group, send email to public-dns-discuss@googlegroups.com

To unsubscribe from this group, send email to

public-dns-discuss+unsub...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================

---
You received this message because you are subscribed to a topic in the Google Groups "public-dns-discuss" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/public-dns-discuss/7Dd4pzBfpZA/unsubscribe.

To unsubscribe from this group and all its topics, send an email to public-dns-discuss+unsub...@googlegroups.com.

[hack...@gmail.com]

I'm having the same issue. Tonight, for some unknown reason, all of a sudden I cannot resolve my website, zanview.com with google's DNS servers:

➜  ~  nslookup zanview.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find zanview.com: NXDOMAIN

 ➜  ~  nslookup zanview.com 8.8.4.4

Server: 8.8.4.4

Address: 8.8.4.4#53

** server can't find zanview.com: NXDOMAIN

But if I try with any other DNS server, including my ISP one, it works fine:

➜  ~  nslookup zanview.com 158.43.240.4

Server: 158.43.240.4

Address: 158.43.240.4#53

Non-authoritative answer:

Name: zanview.com

Address: 213.163.64.74

I have also asked people as far as Thailand to open the URL and there are no issues at all. Why won't my domain resolve with google's DNS servers?

[patrick...@gmail.com]

I am having a similar issue.  My wife's website, equuslibrium.com, is up, but google cannot resolve the A record, which seems to be causing some email issues.

Hermes-II:~ Patrick$ nslookup -q=mx equuslibrium.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find equuslibrium.com: SERVFAIL

Hermes-II:~ Patrick$ nslookup -q=mx equuslibrium.com

Server: 10.0.0.1

Address: 10.0.0.1#53

Non-authoritative answer:

equuslibrium.com mail exchanger = 10 aspmx2.googlemail.com.

equuslibrium.com mail exchanger = 5 alt2.aspmx.l.google.com.

equuslibrium.com mail exchanger = 1 aspmx.l.google.com.

equuslibrium.com mail exchanger = 10 aspmx3.googlemail.com.

equuslibrium.com mail exchanger = 5 alt1.aspmx.l.google.com.

Authoritative answers can be found from:

Hermes-II:~ Patrick$ nslookup equuslibrium.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find equuslibrium.com: SERVFAIL

Hermes-II:~ Patrick$ nslookup equuslibrium.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find equuslibrium.com: SERVFAIL

Hermes-II:~ Patrick$ nslookup equuslibrium.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find equuslibrium.com: SERVFAIL

Hermes-II:~ Patrick$ dig @8.8.8.8 equuslibrium.com +cd

; <<>> DiG 9.6-ESV-R4-P3 <<>> @8.8.8.8 equuslibrium.com +cd

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 28504

;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;equuslibrium.com. IN A

;; ANSWER SECTION:

equuslibrium.com. 300 IN A 184.154.68.250

;; Query time: 166 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Sat Feb 28 15:23:53 2015

;; MSG SIZE  rcvd: 50

Hermes-II:~ Patrick$ dig equuslibrium.com 4.2.2.1

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com 4.2.2.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 20383

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;equuslibrium.com. IN A

;; ANSWER SECTION:

equuslibrium.com. 301 IN A 184.154.68.250

;; Query time: 56 msec

;; SERVER: 10.0.0.1#53(10.0.0.1)

;; WHEN: Sat Feb 28 15:25:19 2015

;; MSG SIZE  rcvd: 50

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 47821

;; flags: qr aa rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;4.2.2.1. IN A

;; ANSWER SECTION:

4.2.2.1. 0 IN A 4.2.2.1

;; Query time: 5 msec

;; SERVER: 10.0.0.1#53(10.0.0.1)

;; WHEN: Sat Feb 28 15:25:19 2015

;; MSG SIZE  rcvd: 41

Hermes-II:~ Patrick$ dig equuslibrium.com @4.2.2.1

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @4.2.2.1

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61666

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;equuslibrium.com. IN A

;; ANSWER SECTION:

equuslibrium.com. 301 IN A 184.154.68.250

;; Query time: 304 msec

;; SERVER: 4.2.2.1#53(4.2.2.1)

;; WHEN: Sat Feb 28 15:25:32 2015

;; MSG SIZE  rcvd: 50

Hermes-II:~ Patrick$ dig equuslibrium.com @4.2.2.2

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @4.2.2.2

;; global options: +cmd

;; connection timed out; no servers could be reached

Hermes-II:~ Patrick$ dig equuslibrium.com @4.2.2.2

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @4.2.2.2

;; global options: +cmd

;; connection timed out; no servers could be reached

Hermes-II:~ Patrick$ dig equuslibrium.com @208.67.222.222

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @208.67.222.222

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 61484

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;equuslibrium.com. IN A

;; ANSWER SECTION:

equuslibrium.com. 301 IN A 184.154.68.250

;; Query time: 157 msec

;; SERVER: 208.67.222.222#53(208.67.222.222)

;; WHEN: Sat Feb 28 15:26:28 2015

;; MSG SIZE  rcvd: 50

Hermes-II:~ Patrick$ dig equuslibrium.com @208.67.220.220

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @208.67.220.220

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 43226

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;equuslibrium.com. IN A

;; ANSWER SECTION:

equuslibrium.com. 301 IN A 184.154.68.250

;; Query time: 152 msec

;; SERVER: 208.67.220.220#53(208.67.220.220)

;; WHEN: Sat Feb 28 15:26:34 2015

;; MSG SIZE  rcvd: 50

Hermes-II:~ Patrick$ dig equuslibrium.com @4.2.2.2

; <<>> DiG 9.6-ESV-R4-P3 <<>> equuslibrium.com @4.2.2.2

;; global options: +cmd

;; connection timed out; no servers could be reached

Hermes-II:~ Patrick$ nslookup equuslibrium.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find equuslibrium.com: SERVFAIL

Hermes-II:~ Patrick$ nslookup equuslibrium.com 4.2.2.1

Server: 4.2.2.1

Address: 4.2.2.1#53

Non-authoritative answer:

Name: equuslibrium.com

Address: 184.154.68.250

Hermes-II:~ Patrick$ nslookup equuslibrium.com 4.2.2.2

;; connection timed out; no servers could be reached

Hermes-II:~ Patrick$ 

[Grant Ridder]

DNSSEC issue for equuslibrium.com ... http://dnsviz.net/d/equuslibrium.com/dnssec/

--

--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.

To post to this group, send email to public-dn...@googlegroups.com

To unsubscribe from this group, send email to

public-dns-disc...@googlegroups.com

For more options, visit this group at
http://groups.google.com/group/public-dns-discuss?hl=en
For more information on Google Public DNS, please visit
http://code.google.com/speed/public-dns
========================================================
---

You received this message because you are subscribed to the Google Groups "public-dns-discuss" group.

To unsubscribe from this group and stop receiving emails from it, send an email to public-dns-disc...@googlegroups.com.

[David Phillips]

percelldance.com 23.236.62.147 not resolving

[Shen Wan]

I just checked and all of our servers resolve the domain fine. Is this still an issue for you? If so, please tell us which location do you experience trouble resolving this domain.

On Thursday, March 26, 2015 at 10:10:15 AM UTC-4, David Phillips wrote:

percelldance.com 23.236.62.147 not resolving

[Bryan Price]

On Wed, Mar 25, 2015 at 4:35 PM, David Phillips <da...@qxo.com> wrote:

percelldance.com 23.236.62.147 not resolving

Works for me....


c:\>nslookup percelldance.com 8.8.8.8
Non-authoritative answer:

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    percelldance.com
Address:  23.236.62.147


c:\>nslookup percelldance.com 114.114.114.114
Non-authoritative answer:

Server:  public1.114dns.com
Address:  114.114.114.114

Name:    percelldance.com
Address:  23.236.62.147


c:\>nslookup percelldance.com 75.75.75.75
Non-authoritative answer:

Server:  cdns01.comcast.net
Address:  75.75.75.75

Name:    percelldance.com
Address:  23.236.62.147


c:\>nslookup percelldance.com 4.2.2.1
Non-authoritative answer:

Server:  a.resolvers.level3.net
Address:  4.2.2.1

DNS request timed out.
    timeout was 2 seconds.
DNS request timed out.
    timeout was 2 seconds.

Name:    percelldance.com
Address:  23.236.62.147


c:\>f:\bind\dig @8.8.8.8 percelldance.com

; <<>> DiG 9.10.1 <<>> @8.8.8.8 percelldance.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 22843
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;percelldance.com.        IN    A

;; ANSWER SECTION:
percelldance.com.    3594    IN    A    23.236.62.147

;; Query time: 48 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Mar 26 10:22:26 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 61


c:\>f:\bind\dig @114.114.114.114 percelldance.com

; <<>> DiG 9.10.1 <<>> @114.114.114.114 percelldance.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9150
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;percelldance.com.        IN    A

;; ANSWER SECTION:
percelldance.com.    3553    IN    A    23.236.62.147

;; Query time: 47 msec
;; SERVER: 114.114.114.114#53(114.114.114.114)
;; WHEN: Thu Mar 26 10:22:26 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 61


c:\>f:\bind\dig @75.75.75.75 percelldance.com 

; <<>> DiG 9.10.1 <<>> @75.75.75.75 percelldance.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63562
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4000
;; QUESTION SECTION:
;percelldance.com.        IN    A

;; ANSWER SECTION:
percelldance.com.    3600    IN    A    23.236.62.147

;; Query time: 63 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Thu Mar 26 10:22:26 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 61


c:\>f:\bind\dig @4.2.2.1 percelldance.com

; <<>> DiG 9.10.1 <<>> @4.2.2.1 percelldance.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 9576
;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 4096
;; QUESTION SECTION:
;percelldance.com.        IN    A

;; ANSWER SECTION:
percelldance.com.    3553    IN    A    23.236.62.147

;; Query time: 24 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Thu Mar 26 10:22:26 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 61


From Florida, USA ISP Comcast

[David Phillips]

I appreciate all of you for checking this out. The problem turned out to be Admuncher. Not sure why or how, because after I disabled filtering, percelldance.com resolved fine. Then I reenabled filtering, and it still resolved okay.

Thank you!
  --David

[s.sp...@gmail.com]

Hi,

I have a domain that is resolved everywhere but Google DNS.

I am out of options. Could you check it out?

nowwemove.com

Thank you,

Svilen

[Bryan Price]

On Wed, Apr 15, 2015 at 9:53 AM, <s.sp...@gmail.com> wrote:

Hi,

I have a domain that is resolved everywhere but Google DNS.

I am out of options. Could you check it out?

nowwemove.com

Works for me.

c:\>nslookup nowwemove.com 8.8.8.8
Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Non-authoritative answer:
Name:    nowwemove.com
Address:  46.4.85.179


c:\>f:\bind\dig @8.8.8.8 nowwemove.com

; <<>> DiG 9.10.1 <<>> @8.8.8.8 nowwemove.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 39858

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;nowwemove.com.                 IN      A

;; ANSWER SECTION:
nowwemove.com.          3599    IN      A       46.4.85.179

;; Query time: 281 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Thu Apr 16 20:23:44 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 58

[koenig...@gmail.com]

Hi,

I have the same problem, Google DNS could not resolving my domain, i see the problem today:

$ dig @8.8.8.8 NAGG.RU a

; <<>> DiG 9.8.5-P1 <<>> @8.8.8.8 NAGG.RU a

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 55919

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;NAGG.RU. IN A

;; Query time: 44 msec

;; SERVER: 8.8.8.8#53(8.8.8.8)

;; WHEN: Thu Jun 18 20:29:09 CEST 2015

;; MSG SIZE  rcvd: 25

Other DNS work correct with my domain:

$ dig @77.88.8.8 NAGG.RU a

; <<>> DiG 9.8.5-P1 <<>> @77.88.8.8 NAGG.RU a

; (1 server found)

;; global options: +cmd

;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 4368

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;NAGG.RU. IN A

;; ANSWER SECTION:

NAGG.RU. 2227 IN A 195.242.142.41

;; Query time: 33 msec

;; SERVER: 77.88.8.8#53(77.88.8.8)

;; WHEN: Thu Jun 18 20:30:14 CEST 2015

;; MSG SIZE  rcvd: 41

Could you help and check it out?

Thank you.

четверг, 16 апреля 2015 г., 22:52:12 UTC+2 пользователь s.sp...@gmail.com написал:

[Bryan Price]

On Thu, Jun 18, 2015 at 2:31 PM, <koenig...@gmail.com> wrote:

Hi,

I have the same problem, Google DNS could not resolving my domain, i see the problem today:

$ dig @8.8.8.8 NAGG.RU a

Works for me.


c:\>nslookup nagg.ru 8.8.8.8

Non-authoritative answer:

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    nagg.ru
Address:  195.242.142.41


c:\>f:\bind\dig @8.8.8.8 nagg.ru

; <<>> DiG 9.10.1 <<>> @8.8.8.8 nagg.ru

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 21182

;; flags: qr rd ra; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;nagg.ru.            IN    A

;; ANSWER SECTION:
nagg.ru.        3390    IN    A    195.242.142.41

;; Query time: 32 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 19 22:39:57 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 52

From Florida, USA ISP Comcast

With the a dig option:
c:\>f:\bind\dig @8.8.8.8 nnagg.ru a

; <<>> DiG 9.10.1 <<>> @8.8.8.8 nnagg.ru a

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 13425
;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;nnagg.ru.                      IN      A

;; AUTHORITY SECTION:
ru.                     1799    IN      SOA     a.dns.ripn.net. hostmaster.ripn.net. 4023734 86400 14400 2592000 3600

;; Query time: 71 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Fri Jun 19 22:38:07 Eastern Daylight Time 2015
;; MSG SIZE  rcvd: 98

Which probably isn't what you were looking for.

[koenig...@gmail.com]

Yes, problem was on my side. Google DNS timed out to 195.242.143.2. I fix the problem.

All works. Thank you for your help!

суббота, 20 июня 2015 г., 4:42:38 UTC+2 пользователь bytehead написал:

[tfo...@gmail.com]

I have a similiar problem. My domain bulkfoward.com is not resolving properly with google or gmail it self.

Delivery to the following recipient failed permanently:

 

     ad...@bulkfoward.com

 

Technical details of permanent failure:

DNS Error: Address resolution of bulkfoward.com. failed: Domain name not found

 

----- Original message -----

 

DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;

        d=gmail.com; s=20120113;

        h=from:to:subject:date:message-id:mime-version:content-type

         :content-language:thread-index;

        bh=x3p810AMcrYqUq7DAxJHAosnQHvgfDRJIVPEEZ2C1U8=;

        b=oJupQmuN3GYnVlcN2VJlWqYuRQ3uQZOXWcaotRcEoATlp6OSmnBSVWcogrHZPWG/ZC

         Lhytr5nA5UTEM3U2J+dIUPGyOxiQXJOaT+to14ZZsiBB/zCumUp4LSaUNkUstkv7mf+S

         KUIQh7lTUOIXHjrnNmtURo2uYcInJZ86XErnRz24Z5YxJvuVvl1NVoREO7gCEO3cVehh

         Fwclb3NTWTGuVXdIWMv55AP5BGPXr4hDDJVuyI+wyd1dK+EfVZ1nsBIlkYgVhpxXbR/V

         8ePGcltsyvcoOHZTp9/c/n0zQEc5fMy01Ug8Q47nrZH/wBPUN6NJKKy+6QscYAzwo3eC

         jSPQ==

X-Received: by 10.31.130.71 with SMTP id e68mr15177922vkd.11.1445971122004;

        Tue, 27 Oct 2015 11:38:42 -0700 (PDT)

Return-Path: <tfo...@gmail.com>

Received: from pc ([2601:582:4007:100:6cfc:a961:ae4d:784a])

        by smtp.gmail.com with ESMTPSA id w14sm6748718vke.6.2015.10.27.11.38.40

        for <ad...@bulkfoward.com>

        (version=TLSv1.2 cipher=ECDHE-RSA-AES128-GCM-SHA256 bits=128/128);

        Tue, 27 Oct 2015 11:38:41 -0700 (PDT)

From: "Ariel" <tfo...@gmail.com>

To: <ad...@bulkfoward.com>

Subject: test

Date: Tue, 27 Oct 2015 14:38:40 -0400

Message-ID: <2bea01d110e6$b37d7080$1a785180$@gmail.com>

MIME-Version: 1.0

Content-Type: multipart/alternative;

              boundary="----=_NextPart_000_2BEB_01D110C5.2C6C45B0"

X-Mailer: Microsoft Outlook 16.0

Content-Language: en-us

thread-index: AdEQ5rJ7d1KI4Vo8TOSpABFpjW7klg==

 

test

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 2628

;; flags: qr rd ra; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:

;gmdrives.com.                        IN        A

;; Query time: 1085 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Feb 20 15:44:32 2012
;; MSG SIZE  rcvd: 30


> dig @208.67.222.222 gmdrives.com

; <<>> DiG 9.7.3-P3 <<>> @208.67.222.222 gmdrives.com

; (1 server found)
;; global options: +cmd
;; Got answer:

[jo...@neoserveis.com]

Same problem here. Google DNS doesn't resolve logisticsmasterspain.com

Can u fix it?
Tks

[Grant Ridder]

DNSSEC issue...

http://dnsviz.net/d/logisticsmasterspain.com/dnssec/

--
--
========================================================
You received this message because you are subscribed to the Google
Groups "public-dns-discuss" group.
To post to this group, send email to public-dn...@googlegroups.com
To unsubscribe from this group, send email to
public-dns-disc...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/public-dns-discuss

For more information on Google Public DNS, please visit

http://developers.google.com/speed/public-dns

[François]

Hi,

we seam to have the same issue with portfoliomanager.energystar.gov.

As this is not our domain we can´t modify anything that relates to it. We only face the issue that our servers can´t resolve the domain so that our system fails too.
what can be done to fix this?

best regards
François

http://www.intodns.com/portfoliomanager.energystar.gov
http://dnsviz.net/d/portfoliomanager.energystar.gov/dnssec/

www:~ # dig @8.8.8.8 portfoliomanager.energystar.gov. +cd

; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> @8.8.8.8 portfoliomanager.energystar.gov.                                                                                                                                                              +cd

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 3267
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 0, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:

;portfoliomanager.energystar.gov. IN    A

;; Query time: 4022 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Tue Dec 22 13:00:22 CET 2015
;; MSG SIZE  rcvd: 60

www:~ # dig @4.2.2.1 portfoliomanager.energystar.gov. +cd

; <<>> DiG 9.9.4-rpz2.13269.14-P2 <<>> @4.2.2.1 portfoliomanager.energystar.gov.                                                                                                                                                              +cd

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 56449
;; flags: qr rd ra cd; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 8192
;; QUESTION SECTION:
;portfoliomanager.energystar.gov. IN    A

;; ANSWER SECTION:
portfoliomanager.energystar.gov. 172800 IN A    128.121.47.114

;; Query time: 116 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Tue Dec 22 13:00:56 CET 2015
;; MSG SIZE  rcvd: 76

[Shen Wan]

These nameservers did not respond to our query: [2001:418:dc01:111:20c:29ff:fe61:3df9, 128.121.47.116, 2001:418:dc01:111:20c:29ff:fe7a:4341, 128.121.47.117]. If you can, please reach out to the nameserver owners to fix.

[fth...@gmail.com]

I think the administrator of an .gov domain/dns server is more likely to react on an message from google then from... me? what i wonder about is how other nameservers resolve this name. so it doesn´t seam to be a general issue to me.

[mohammed...@googlemail.com]

Hey guys. I have started my webshop recently and people who are using google dns cannot access it. The domain is

 

www.freevolution-wear.com 

It runs via strato server and when I try to access it from work (we use google dns there) I get the following error

DNS_PROBE_FINISHED_NXDOMAIN

I have called my host several times as well as google but no one can figure out what the problem is.

Can you please help me? I am losing customers because of it :( 

[Shen Wan]

Hi,

Please follow https://developers.google.com/speed/public-dns/docs/using#troubleshooting to diagnose and provide us your result if you still need help.

Thanks!

[Shen Wan]

This is because the domain fails DNSSEC validation. Please enter your domain at dnsviz.net for an explanation: http://dnsviz.net/d/www.freevolution-wear.com/dnssec/.

[ste...@thelocalcollaborative.com]

I'm experiencing the same problem with my domain thelocalcollaborative.com

nslookup thelocalcollaborative.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find thelocalcollaborative.com: SERVFAIL

nslookup thelocalcollaborative.com 208.67.222.222 

Server: 208.67.222.222

Address: 208.67.222.222#53

Non-authoritative answer:

Name: thelocalcollaborative.com

Address: 52.7.21.189

Using Amazon Route 53 for Nameservers, which don't appear to have DNSSEC support.  Wondering what I can do to get this worked out.

[Bryan Price]

On Sat, Apr 2, 2016 at 2:42 PM, <ste...@thelocalcollaborative.com> wrote:

I'm experiencing the same problem with my domain thelocalcollaborative.com

nslookup thelocalcollaborative.com 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find thelocalcollaborative.com: SERVFAIL

Works for me.

DNSSEC validated DNS only


C:\WINDOWS\system32>nslookup thelocalcollaborative.com 8.8.8.8

Non-authoritative answer:

Server:  google-public-dns-a.google.com
Address:  8.8.8.8

Name:    thelocalcollaborative.com
Address:  52.7.21.189


C:\WINDOWS\system32>f:\bind\dig @8.8.8.8 thelocalcollaborative.com

; <<>> DiG 9.10.1 <<>> @8.8.8.8 thelocalcollaborative.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 62945
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;thelocalcollaborative.com.    IN    A

;; ANSWER SECTION:
thelocalcollaborative.com. 3599    IN    A    52.7.21.189

;; Query time: 26 msec
;; SERVER: 8.8.8.8#53(8.8.8.8)
;; WHEN: Mon Apr 04 10:28:49 Eastern Daylight Time 2016
;; MSG SIZE  rcvd: 70


C:\WINDOWS\system32>nslookup thelocalcollaborative.com 75.75.75.75

Non-authoritative answer:

Server:  cdns01.comcast.net
Address:  75.75.75.75

Name:    thelocalcollaborative.com
Address:  52.7.21.189


C:\WINDOWS\system32>f:\bind\dig @75.75.75.75 thelocalcollaborative.com

; <<>> DiG 9.10.1 <<>> @75.75.75.75 thelocalcollaborative.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 41028
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags:; udp: 512
;; QUESTION SECTION:
;thelocalcollaborative.com.    IN    A

;; ANSWER SECTION:
thelocalcollaborative.com. 3520    IN    A    52.7.21.189

;; Query time: 17 msec
;; SERVER: 75.75.75.75#53(75.75.75.75)
;; WHEN: Mon Apr 04 10:28:50 Eastern Daylight Time 2016
;; MSG SIZE  rcvd: 70


C:\WINDOWS\system32>nslookup thelocalcollaborative.com 64.6.64.6
Non-authoritative answer:

Server:  recpubns1.nstld.net
Address:  64.6.64.6

Name:    thelocalcollaborative.com
Address:  52.7.21.189


C:\WINDOWS\system32>f:\bind\dig @64.6.64.6 thelocalcollaborative.com

; <<>> DiG 9.10.1 <<>> @64.6.64.6 thelocalcollaborative.com

; (1 server found)
;; global options: +cmd
;; Got answer:

;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51779
;; flags: qr rd ra ad; QUERY: 1, ANSWER: 1, AUTHORITY: 0, ADDITIONAL: 1

;; OPT PSEUDOSECTION:
; EDNS: version: 0, flags: do; udp: 4096
;; QUESTION SECTION:
;thelocalcollaborative.com.    IN    A

;; ANSWER SECTION:
thelocalcollaborative.com. 3520    IN    A    52.7.21.189

;; Query time: 53 msec
;; SERVER: 64.6.64.6#53(64.6.64.6)
;; WHEN: Mon Apr 04 10:28:50 Eastern Daylight Time 2016
;; MSG SIZE  rcvd: 70

From Florida, USA ISP Comcast

Also, you do have DNSSEC, and it's set correctly.

http://dnsviz.net/d/thelocalcollaborative.com/dnssec/

[ste...@thelocalcollaborative.com]

I moved to an alternative DNS provider that supports DNSSEC.

[casha...@gmail.com]

Any reason this domain hogeringoogle.com fails to resolve - other dns servers are fine:

[root@linweb13 ~]# host www.hogeringoogle.com 4.2.2.1
www.hogeringoogle.com has address 62.212.150.16

[root@linweb13 ~]# host www.hogeringoogle.com 8.8.8.8
Host www.hogeringoogle.com not found: 2(SERVFAIL)

[root@linweb13 ~]# host www.hogeringoogle.com 208.67.222.222
www.hogeringoogle.com has address 62.212.150.16

Thanks!

[Alex Dupuy]

$ checkdomain www.hogeringoogle.com

The 'hogeringoogle.com' zone has a DNSSEC misconfiguration.

The parent zone 'com' has a DS record for 'hogeringoogle'

but the 'hogeringoogle.com' zone has no DNSKEY record.

To fix this, remove the DS record for 'hogeringoogle.com'

in the 'com' zone.

Joker supports adding and removing DS records either through the web interface described at https://joker.com/faq/content/6/461/en/dnssec-support.html

or the API given at https://joker.com/faq/content/27/24/en/domain_modify.html.

'www.hogeringoogle.com' is in 'hogeringoogle.com' zone under .COM

'hogeringoogle.com' is failing DNSSEC validation, and has

2 nameservers in 'nedlook.com' (all are failing validation)

'hogeringoogle.com' is registered through 'Csl Computer Service Langenbach Gmbh D/B/A Joker.Com'

Name Server: ns1.nedlook.com

Name Server: ns2.nedlook.com

[umash...@playo.co]

Our domain is resolved in all the DNS servers except Google's. We dont use any DS records for our domain.

> nslookup playo.io 8.8.8.8

Server: 8.8.8.8

Address: 8.8.8.8#53

** server can't find playo.io: SERVFAIL

> nslookup playo.io 216.69.185.43

Server: 216.69.185.43

Address: 216.69.185.43#53

Name: playo.io

Address: 52.74.165.241

[Alex Dupuy]

The GoDaddy authoritative DNS servers were not responding to queries from our resolvers in Singapore and Taiwan, but that problem has been resolved.

See https://groups.google.com/d/msg/public-dns-discuss/l4ToXqoO-Eo/lT-EGRbfBAAJ for suggestions on what you can do to prevent these sorts of problems in the future.