DNS resolution problem for www domain?
103 views
Skip to first unread message
Gregor Hochmuth
May 13, 2008, 5:47:17 PM5/13/08
to Google App Engine
Hello,
I'm getting reports from *some* users that they cannot resolve the
primary www domain of the service I published (www.laterloop.com). The
DNS information is hosted with EveryDNS.net and the www domain points
to ghs.google.com via a CNAME record. The www domain is also
registered in the Google App Engine service panel on Google Apps for
Your Domain.
Has anyone had this issue? Unfortuantely, I can't verify it myself
because the DNS resolution is working for me and on several other
remote servers that I tested.
Any feedback would be much appreciated? Thanks!
Greg
I'm getting reports from *some* users that they cannot resolve the
primary www domain of the service I published (www.laterloop.com). The
DNS information is hosted with EveryDNS.net and the www domain points
to ghs.google.com via a CNAME record. The www domain is also
registered in the Google App Engine service panel on Google Apps for
Your Domain.
Has anyone had this issue? Unfortuantely, I can't verify it myself
because the DNS resolution is working for me and on several other
remote servers that I tested.
Any feedback would be much appreciated? Thanks!
Greg
Barry Hunter
May 13, 2008, 6:38:32 PM5/13/08
to google-a...@googlegroups.com
I'm not a total DNS expert, but I beleive the everyDNS servers are
returning incorrect results...
returning incorrect results...
------------8<-----------
#dig www.laterloop.com @ns4.everydns.net
; <<>> DiG 9.3.4-P1 <<>> www.laterloop.com @ns4.everydns.net
; (1 server found)
;; global options: printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53756
;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
;; QUESTION SECTION:
;www.laterloop.com. IN A
;; ANSWER SECTION:
www.laterloop.com. 3600 IN CNAME ghs.google.com.
;; AUTHORITY SECTION:
google.com. 360 IN SOA ns1.everydns.net.
hostmaster.google.com. 1210710007 3600 900 1209600 3600
;; Query time: 158 msec
;; SERVER: 64.158.219.3#53(64.158.219.3)
;; WHEN: Tue May 13 23:29:10 2008
;; MSG SIZE rcvd: 123
----------->8------------------
That SOA record in there is VERY suspicisous...
"The SOA resource record indicates that this DNS name server is the
best source of information for the data within this DNS domain."
http://support.microsoft.com/kb/163971
... which clearly isnt the case. Google dont host their DNS at everyDNS.
You even get inconsistant results from the different everyDNS servers,
eg @ns2.everydns.net gets it right and makes no such (false) claim -
therefore your computer will then refer (correctly) to Googles NS
servers and get it right.
IF you have been to another appspot or Google domain (as I have so I
get it right too on my main connection) then I have the correct Google
details, meaning the incorrect SOA is ignored.
Anyway I would chase it up with everyDNS - the last time I had a
problem with them, they delt quickly.
--
Barry
Liam Chasteen
May 13, 2008, 8:32:23 PM5/13/08
to google-a...@googlegroups.com
I use everyDNS as well and have been seeing the same problem, but didn't know what the cause was. Thanks for the fine sleuth work Barry.
Regards,
Liam
Regards,
Liam
Gregor Hochmuth
May 15, 2008, 6:39:31 PM5/15/08
to Google App Engine
Thanks a lot, Barry! I would have never known how to uncover this.
I got in touch with EveryDNS -- when I know more, I'll add it to this
thread.
Thanks again,
Greg.
On May 14, 2:32 am, "Liam Chasteen" <liam.chast...@gmail.com> wrote:
> I use everyDNS as well and have been seeing the same problem, but didn't
> know what the cause was. Thanks for the fine sleuth work Barry.
>
> Regards,
> Liam
>
> On Tue, May 13, 2008 at 3:38 PM, Barry Hunter <barrybhun...@googlemail.com>
>
> > ; <<>> DiG 9.3.4-P1 <<>>www.late...@ns4.everydns.net
I got in touch with EveryDNS -- when I know more, I'll add it to this
thread.
Thanks again,
Greg.
On May 14, 2:32 am, "Liam Chasteen" <liam.chast...@gmail.com> wrote:
> I use everyDNS as well and have been seeing the same problem, but didn't
> know what the cause was. Thanks for the fine sleuth work Barry.
>
> Regards,
> Liam
>
> wrote:
>
>
>
> > I'm not a total DNS expert, but I beleive the everyDNS servers are
> > returning incorrect results...
>
> > ------------8<-----------
> > #digwww.lat...@ns4.everydns.net
>
>
>
> > I'm not a total DNS expert, but I beleive the everyDNS servers are
> > returning incorrect results...
>
> > ------------8<-----------
>
> > ; <<>> DiG 9.3.4-P1 <<>>www.late...@ns4.everydns.net
> > ; (1 server found)
> > ;; global options: printcmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53756
> > ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
>
> > ;; QUESTION SECTION:
> > ;www.laterloop.com. IN A
>
> > ;; ANSWER SECTION:
> >www.laterloop.com. 3600 IN CNAME ghs.google.com.
>
> > ;; AUTHORITY SECTION:
> > google.com. 360 IN SOA ns1.everydns.net.
> > hostmaster.google.com. 1210710007 3600 900 1209600 3600
>
> > ;; Query time: 158 msec
> > ;; SERVER: 64.158.219.3#53(64.158.219.3)<http://64.158.219.3#53%2864.158.219.3%29>
> > ;; global options: printcmd
> > ;; Got answer:
> > ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 53756
> > ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0
>
> > ;; QUESTION SECTION:
> > ;www.laterloop.com. IN A
>
> > ;; ANSWER SECTION:
> >www.laterloop.com. 3600 IN CNAME ghs.google.com.
>
> > ;; AUTHORITY SECTION:
> > google.com. 360 IN SOA ns1.everydns.net.
> > hostmaster.google.com. 1210710007 3600 900 1209600 3600
>
> > ;; Query time: 158 msec
> > ;; WHEN: Tue May 13 23:29:10 2008
> > ;; MSG SIZE rcvd: 123
> > ----------->8------------------
>
> > That SOA record in there is VERY suspicisous...
>
> > "The SOA resource record indicates that this DNS name server is the
> > best source of information for the data within this DNS domain."
> >http://support.microsoft.com/kb/163971
>
> > ... which clearly isnt the case. Google dont host their DNS at everyDNS.
>
> > You even get inconsistant results from the different everyDNS servers,
> > eg @ns2.everydns.net gets it right and makes no such (false) claim -
> > therefore your computer will then refer (correctly) to Googles NS
> > servers and get it right.
>
> > IF you have been to another appspot or Google domain (as I have so I
> > get it right too on my main connection) then I have the correct Google
> > details, meaning the incorrect SOA is ignored.
>
> > Anyway I would chase it up with everyDNS - the last time I had a
> > problem with them, they delt quickly.
>
> > On Tue, May 13, 2008 at 10:47 PM, Gregor Hochmuth <ghochm...@gmail.com>
> > ;; MSG SIZE rcvd: 123
> > ----------->8------------------
>
> > That SOA record in there is VERY suspicisous...
>
> > "The SOA resource record indicates that this DNS name server is the
> > best source of information for the data within this DNS domain."
> >http://support.microsoft.com/kb/163971
>
> > ... which clearly isnt the case. Google dont host their DNS at everyDNS.
>
> > You even get inconsistant results from the different everyDNS servers,
> > eg @ns2.everydns.net gets it right and makes no such (false) claim -
> > therefore your computer will then refer (correctly) to Googles NS
> > servers and get it right.
>
> > IF you have been to another appspot or Google domain (as I have so I
> > get it right too on my main connection) then I have the correct Google
> > details, meaning the incorrect SOA is ignored.
>
> > Anyway I would chase it up with everyDNS - the last time I had a
> > problem with them, they delt quickly.
>
Janusz Skonieczny
Sep 24, 2011, 6:10:36 AM9/24/11
to google-a...@googlegroups.com
I have a similar problem, my www.dziennik.edu.pl is not reachable by some people, can you help me diagnose this?
; <<>> DiG 9.6.-ESV-R5 <<>> app.dziennik.edu.pl @ns10.az.pl ;; global options: +cmd ;; Got answer: ;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 30298 ;; flags: qr aa rd; QUERY: 1, ANSWER: 1, AUTHORITY: 1, ADDITIONAL: 0 ;; WARNING: recursion requested but not available ;; QUESTION SECTION: ;app.dziennik.edu.pl. IN A ;; ANSWER SECTION: app.dziennik.edu.pl. 3600 IN CNAME ghs.google.com. ;; AUTHORITY SECTION: . 3600 IN SOA ns10.az.pl. admin.az.pl. 2011072100 10800 3600 604800 3600 ;; Query time: 143 msec ;; SERVER: 62.146.113.3#53(62.146.113.3) ;; WHEN: Sat Sep 24 05:08:12 2011 ;; MSG SIZE rcvd: 114
Brandon Wirtz
Sep 24, 2011, 6:44:51 AM9/24/11
to google-a...@googlegroups.com
Who is it not reachable for? Where are they Physically who is their provider? You are Up for me from 23 locations I have access to on 3 continents.
--
You received this message because you are subscribed to the Google Groups "Google App Engine" group.
To view this discussion on the web visit https://groups.google.com/d/msg/google-appengine/-/8LKdYXnlFKcJ.
To post to this group, send email to google-a...@googlegroups.com.
To unsubscribe from this group, send email to google-appengi...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/google-appengine?hl=en.
Janusz Skonieczny
Sep 24, 2011, 10:21:33 AM9/24/11
to google-a...@googlegroups.com
All of them in Poland, here is some info i have collected. I'm sorry in advance for the quality of it I'm a network newbe, and I do not have physical to those machines, I asked some people to run a couple commands on their boxes.
##### ##### ping dziennik.edu.pl ##### Pinging dziennik.edu.pl [62.146.68.215] with 32 bytes of data: Reply from 62.146.68.215: bytes=32 time=66ms TTL=48 Reply from 62.146.68.215: bytes=32 time=66ms TTL=48 Reply from 62.146.68.215: bytes=32 time=65ms TTL=48 Reply from 62.146.68.215: bytes=32 time=65ms TTL=48 Ping statistics for 62.146.68.215: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 65ms, Maximum = 66ms, Average = 65ms ##### ##### ping app.dziennik.edu.pl ##### Ping request could not find host app.dziennik.edu.pl. Please check the name and try again. ##### ##### ping ghs.google.com ##### Pinging ghs.l.google.com [74.125.79.121] with 32 bytes of data: Reply from 74.125.79.121: bytes=32 time=40ms TTL=51 Reply from 74.125.79.121: bytes=32 time=41ms TTL=52 Reply from 74.125.79.121: bytes=32 time=42ms TTL=52 Reply from 74.125.79.121: bytes=32 time=41ms TTL=52 Ping statistics for 74.125.79.121: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 40ms, Maximum = 42ms, Average = 41ms ##### ##### ipconfig /all ##### Windows IP Configuration Host Name . . . . . . . . . . . . : Home1 Primary Dns Suffix . . . . . . . : Node Type . . . . . . . . . . . . : Hybrid IP Routing Enabled. . . . . . . . : No WINS Proxy Enabled. . . . . . . . : No DNS Suffix Search List. . . . . . : chello.pl Ethernet adapter Local Area Connection 2: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : TAP-Win32 Adapter V9 Physical Address. . . . . . . . . : 00-FF-E6-93-7F-5F DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : chello.pl Description . . . . . . . . . . . : Realtek PCIe GBE Family Controller Physical Address. . . . . . . . . : E0-CB-4E-81-94-81 DHCP Enabled. . . . . . . . . . . : Yes Autoconfiguration Enabled . . . . : Yes Link-local IPv6 Address . . . . . : fe80::29ea:ea5b:c308:5fb3%11(Preferred) IPv4 Address. . . . . . . . . . . : 87.207.162.187(Preferred) Subnet Mask . . . . . . . . . . . : 255.255.254.0 Lease Obtained. . . . . . . . . . : 24 wrze˜nia 2011 09:33:25 Lease Expires . . . . . . . . . . : 30 wrze˜nia 2011 06:09:11 Default Gateway . . . . . . . . . : 87.207.162.1 DHCP Server . . . . . . . . . . . : 10.131.40.1 DHCPv6 IAID . . . . . . . . . . . : 249613134 DHCPv6 Client DUID. . . . . . . . : 00-01-00-01-13-77-89-56-E0-CB-4E-81-94-81 DNS Servers . . . . . . . . . . . : 62.179.1.63 62.179.1.62 NetBIOS over Tcpip. . . . . . . . : Enabled Tunnel adapter isatap.chello.pl: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : chello.pl Description . . . . . . . . . . . : Microsoft ISATAP Adapter Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes Tunnel adapter Teredo Tunneling Pseudo-Interface: Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2001:0:5ef5:79fd:14aa:2509:a830:5d44(Preferred) Link-local IPv6 Address . . . . . : fe80::14aa:2509:a830:5d44%12(Preferred) Default Gateway . . . . . . . . . : NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter Reusable Microsoft 6To4 Adapter: Connection-specific DNS Suffix . : chello.pl Description . . . . . . . . . . . : Microsoft 6to4 Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes IPv6 Address. . . . . . . . . . . : 2002:57cf:a2bb::57cf:a2bb(Preferred) Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301 DNS Servers . . . . . . . . . . . : 62.179.1.63 62.179.1.62 NetBIOS over Tcpip. . . . . . . . : Disabled Tunnel adapter isatap.{E6937F5F-F54B-452B-81C8-ED551FB63D45}: Media State . . . . . . . . . . . : Media disconnected Connection-specific DNS Suffix . : Description . . . . . . . . . . . : Microsoft ISATAP Adapter #2 Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP Enabled. . . . . . . . . . . : No Autoconfiguration Enabled . . . . : Yes ##### ##### ipconfig /flushdns ##### Windows IP Configuration Successfully flushed the DNS Resolver Cache. ##### ##### ping app.dziennik.edu.pl ##### Ping request could not find host app.dziennik.edu.pl. Please check the name and try again. ##### ##### ipconfig /displaydns ##### Windows IP Configuration 1.0.0.127.in-addr.arpa ---------------------------------------- Record Name . . . . . : 1.0.0.127.in-addr.arpa. Record Type . . . . . : 12 Time To Live . . . . : 86400 Data Length . . . . . : 8 Section . . . . . . . : Answer PTR Record . . . . . : activate.adobe.com activate.adobe.com ---------------------------------------- Record Name . . . . . : activate.adobe.com Record Type . . . . . : 1 Time To Live . . . . : 86400 Data Length . . . . . : 4 Section . . . . . . . : Answer A (Host) Record . . . : 127.0.0.1 activate.adobe.com ---------------------------------------- No records of type AAAA app.dziennik.edu.pl ---------------------------------------- Name does not exist. ##### ##### ping ghs.google.com ##### Pinging ghs.l.google.com [74.125.79.121] with 32 bytes of data: Reply from 74.125.79.121: bytes=32 time=40ms TTL=52 Reply from 74.125.79.121: bytes=32 time=41ms TTL=51 Reply from 74.125.79.121: bytes=32 time=39ms TTL=51 Reply from 74.125.79.121: bytes=32 time=41ms TTL=52 Ping statistics for 74.125.79.121: Packets: Sent = 4, Received = 4, Lost = 0 (0% loss), Approximate round trip times in milli-seconds: Minimum = 39ms, Maximum = 41ms, Average = 40ms ##### ##### ipconfig /displaydns ##### Windows IP Configuration 1.0.0.127.in-addr.arpa ---------------------------------------- Record Name . . . . . : 1.0.0.127.in-addr.arpa. Record Type . . . . . : 12 Time To Live . . . . : 86400 Data Length . . . . . : 8 Section . . . . . . . : Answer PTR Record . . . . . : activate.adobe.com ghs.google.com ---------------------------------------- Record Name . . . . . : ghs.google.com Record Type . . . . . : 5 Time To Live . . . . : 296 Data Length . . . . . : 8 Section . . . . . . . : Answer CNAME Record . . . . : ghs.l.google.com activate.adobe.com ---------------------------------------- Record Name . . . . . : activate.adobe.com Record Type . . . . . : 1 Time To Live . . . . : 86400 Data Length . . . . . : 4 Section . . . . . . . : Answer A (Host) Record . . . : 127.0.0.1 activate.adobe.com ---------------------------------------- No records of type AAAA app.dziennik.edu.pl ---------------------------------------- Name does not exist. ##### ##### tracert app.dziennik.edu.pl ##### Unable to resolve target system name app.dziennik.edu.pl. ##### ##### tracert ghs.google.com ##### Tracing route to ghs.l.google.com [74.125.79.121] over a maximum of 30 hops: 1 8 ms 23 ms 8 ms 87-207-162-1.dynamic.chello.pl [87.207.162.1] 2 7 ms 8 ms 6 ms 89-75-3-33.dynamic.chello.pl [89.75.3.33] 3 30 ms 30 ms 28 ms 84.116.252.106 4 * 56 ms 38 ms 84.116.252.109 5 30 ms 29 ms 29 ms 84.116.134.189 6 29 ms 37 ms 30 ms de-fra01a-ri2-xe-0-2-0.aorta.net [213.46.179.110] 7 31 ms 31 ms 30 ms 72.14.198.165 8 30 ms 29 ms 29 ms 209.85.254.108 9 31 ms 30 ms 37 ms 72.14.236.20 10 36 ms 37 ms 37 ms 209.85.241.226 11 40 ms 41 ms 41 ms 216.239.49.36 12 46 ms * * 209.85.255.130 13 40 ms 43 ms 42 ms ey-in-f121.1e100.net [74.125.79.121] Trace complete.
######## Another:
##### ##### ping dziennik.edu.pl ##### Badanie dziennik.edu.pl [62.146.68.215] z 32 bajtami danych: Odpowied« z 62.146.68.215: bajt˘w=32 czas=64ms TTL=48 Odpowied« z 62.146.68.215: bajt˘w=32 czas=64ms TTL=48 Odpowied« z 62.146.68.215: bajt˘w=32 czas=65ms TTL=48 Odpowied« z 62.146.68.215: bajt˘w=32 czas=64ms TTL=48 Statystyka badania ping dla 62.146.68.215: Pakiety: Wys ane = 4, Odebrane = 4, Utracone = 0 (0% straty), Szacunkowy czas b Ądzenia pakiet˘w w millisekundach: Minimum = 64 ms, Maksimum = 65 ms, Czas redni = 64 ms ##### ##### ping app.dziennik.edu.pl ##### ˝Ądanie polecenia ping nie moľe znale«† hosta app.dziennik.edu.pl. Sprawd« nazw© i pon˘w pr˘b©. ##### ##### ping ghs.google.com ##### Badanie ghs.l.google.com [74.125.77.121] z 32 bajtami danych: Odpowied« z 74.125.77.121: bajt˘w=32 czas=40ms TTL=51 Odpowied« z 74.125.77.121: bajt˘w=32 czas=41ms TTL=50 Odpowied« z 74.125.77.121: bajt˘w=32 czas=41ms TTL=50 Odpowied« z 74.125.77.121: bajt˘w=32 czas=42ms TTL=51 Statystyka badania ping dla 74.125.77.121: Pakiety: Wys ane = 4, Odebrane = 4, Utracone = 0 (0% straty), Szacunkowy czas b Ądzenia pakiet˘w w millisekundach: Minimum = 40 ms, Maksimum = 42 ms, Czas redni = 41 ms ##### ##### ipconfig /all ##### Konfiguracja IP systemu Windows Nazwa hosta . . . . . . . . . . . : Stacjonarny Sufiks podstawowej domeny DNS . . : Typ w©z a . . . . . . . . . . . . : Hybrydowy Routing IP w Ączony . . . . . . . : Nie Serwer WINS Proxy w Ączony. . . . : Nie Karta bezprzewodowej sieci LAN Po Ączenie sieci bezprzewodowej: Sufiks DNS konkretnego po Ączenia : Opis. . . . . . . . . . . . . . . : TP-LINK 11b/g Wireless Adapter Adres fizyczny. . . . . . . . . . : 54-E6-FC-D5-DE-9D DHCP w Ączone . . . . . . . . . . : Tak Autokonfiguracja w Ączona . . . . : Tak Adres IPv6 po Ączenia lokalnego . : fe80::2593:60e4:77b1:69fa%15(Preferowane) Adres IPv4. . . . . . . . . . . . . : 192.168.1.2(Preferowane) Maska podsieci. . . . . . . . . . : 255.255.255.0 Dzierľawa uzyskana. . . . . . . . : 23 wrze nia 2011 19:52:10 Dzierľawa wygasa. . . . . . . . . : 25 wrze nia 2011 07:24:47 Brama domy lna. . . . . . . . . . : 192.168.1.1 Serwer DHCP . . . . . . . . . . . : 192.168.1.1 Identyfikator IAID DHCPv6 . . . . : 374662908 Identyfikator DUID klienta DHCPv6 : 00-01-00-01-14-08-A2-D2-6C-F0-49-B9-9C-EE Serwery DNS . . . . . . . . . . . : 192.168.1.1 NetBIOS przez Tcpip . . . . . . . : W Ączony Karta Ethernet Po Ączenie lokalne: Stan no nika . . . . . . . . . . .: No nik od Ączony Sufiks DNS konkretnego po Ączenia : komp5 Opis. . . . . . . . . . . . . . . : Karta Realtek RTL8168D/8111D Family PCI-E Gigabit Ethernet NIC (NDIS 6.20) Adres fizyczny. . . . . . . . . . : 6C-F0-49-B9-9C-EE DHCP w Ączone . . . . . . . . . . : Tak Autokonfiguracja w Ączona . . . . : Tak Karta tunelowa isatap.komp5: Stan no nika . . . . . . . . . . .: No nik od Ączony Sufiks DNS konkretnego po Ączenia : Opis. . . . . . . . . . . . . . . : Karta Microsoft ISATAP Adres fizyczny. . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP w Ączone . . . . . . . . . . : Nie Autokonfiguracja w Ączona . . . . : Tak Karta tunelowa Teredo Tunneling Pseudo-Interface: Sufiks DNS konkretnego po Ączenia : Opis. . . . . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface Adres fizyczny. . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP w Ączone . . . . . . . . . . : Nie Autokonfiguracja w Ączona . . . . : Tak Adres IPv6. . . . . . . . . . . . : 2001:0:5ef5:79fb:34de:2a6f:a6b4:79eb(Preferowane) Adres IPv6 po Ączenia lokalnego . : fe80::34de:2a6f:a6b4:79eb%12(Preferowane) Brama domy lna. . . . . . . . . . : :: NetBIOS przez Tcpip . . . . . . . : Wy Ączony Karta tunelowa isatap.{38E6CBA4-163C-4070-A193-D0A9840961D0}: Stan no nika . . . . . . . . . . .: No nik od Ączony Sufiks DNS konkretnego po Ączenia : Opis. . . . . . . . . . . . . . . : Karta Microsoft ISATAP #2 Adres fizyczny. . . . . . . . . . : 00-00-00-00-00-00-00-E0 DHCP w Ączone . . . . . . . . . . : Nie Autokonfiguracja w Ączona . . . . : Tak ##### ##### ipconfig /flushdns ##### Konfiguracja IP systemu Windows Pomy lnie opr˘ľniono pami©† podr©cznĄ programu rozpoznawania nazw DNS. ##### ##### ping app.dziennik.edu.pl ##### ˝Ądanie polecenia ping nie moľe znale«† hosta app.dziennik.edu.pl. Sprawd« nazw© i pon˘w pr˘b©. ##### ##### ipconfig /displaydns ##### Konfiguracja IP systemu Windows app.dziennik.edu.pl ---------------------------------------- Nazwa nie istnieje. ##### ##### ping ghs.google.com ##### Badanie ghs.l.google.com [74.125.77.121] z 32 bajtami danych: Odpowied« z 74.125.77.121: bajt˘w=32 czas=40ms TTL=50 Odpowied« z 74.125.77.121: bajt˘w=32 czas=42ms TTL=50 Odpowied« z 74.125.77.121: bajt˘w=32 czas=42ms TTL=51 Up ynĄ limit czasu ľĄdania. Statystyka badania ping dla 74.125.77.121: Pakiety: Wys ane = 4, Odebrane = 3, Utracone = 1 (25% straty), Szacunkowy czas b Ądzenia pakiet˘w w millisekundach: Minimum = 40 ms, Maksimum = 42 ms, Czas redni = 41 ms ##### ##### ipconfig /displaydns ##### Konfiguracja IP systemu Windows ghs.google.com ---------------------------------------- Nazwa rekordu . . . . . . . .: ghs.google.com Typ rekordu . . . . . . . . .: 5 Czas wyga ni©cia (licznik TTL): 196 D ugo † danych . . . . . . . .: 8 Sekcja. . . . . . . . : Odpowied« Rekord CNAME . . . . : ghs.l.google.com www.rescuetime.com ---------------------------------------- Nazwa rekordu . . . . . . . .: www.rescuetime.com Typ rekordu . . . . . . . . .: 5 Czas wyga ni©cia (licznik TTL): 3 D ugo † danych . . . . . . . .: 8 Sekcja. . . . . . . . : Odpowied« Rekord CNAME . . . . : elb-all-services-472859123.us-east-1.elb.amazonaws.com app.dziennik.edu.pl ---------------------------------------- Nazwa nie istnieje. ##### ##### tracert app.dziennik.edu.pl ##### Nie moľna rozpozna† nazwy systemu docelowego app.dziennik.edu.pl. ##### ##### tracert ghs.google.com ##### —ledzenie trasy do ghs.l.google.com [74.125.77.121] z maksymalnĄ liczbĄ 30 przeskok˘w: 1 1 ms <1 ms <1 ms 192.168.1.1 2 12 ms 6 ms 5 ms 10.158.128.1 3 8 ms 9 ms 5 ms 89-75-16-1.dynamic.chello.pl [89.75.16.1] 4 36 ms 32 ms 32 ms 84.116.252.121 5 31 ms 28 ms 33 ms 84.116.252.117 6 32 ms 30 ms 29 ms 84.116.132.129 7 30 ms 31 ms 29 ms 84.116.132.146 8 106 ms 31 ms 28 ms 72.14.219.9 9 31 ms 31 ms 32 ms 209.85.255.170 10 31 ms 31 ms 33 ms 72.14.236.68 11 35 ms 35 ms 37 ms 209.85.241.226 12 41 ms 43 ms 58 ms 216.239.49.38 13 40 ms 39 ms 49 ms 209.85.255.110 14 40 ms 39 ms 39 ms ew-in-f121.1e100.net [74.125.77.121] —ledzenie zakoäczone.
Reply all
Reply to author
Forward
0 new messages