Reply
Thread Tools
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#1
Is it just me??

Thanks
 
Posts: 2,829 | Thanked: 1,459 times | Joined on Dec 2009 @ Finland
#2
Originally Posted by DaveQB View Post
Is it just me??

Thanks
working fine for me.
 
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#3
Hmmm yeah I can get to it from my VPS, but can't from my home network, timeout.
Hmmm odd.

PS
Ahhh looks like a DNS update hasn't come through to my DNS server...


Code:
host repository.maemo.org
repository.maemo.org is an alias for repository.maemo.org.edgesuite.net.
repository.maemo.org.edgesuite.net is an alias for a515.g.akamai.net.
a515.g.akamai.net has address 150.101.98.80
a515.g.akamai.net has address 150.101.98.85
Code:
repository.maemo.org is an alias for repository.maemo.org.edgesuite.net.
repository.maemo.org.edgesuite.net is an alias for a515.g.akamai.net.
a515.g.akamai.net has address 72.246.53.24
a515.g.akamai.net has address 72.246.53.64
Should be right by morning....I hope...
 
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#4
This issue has continued for me using Internodes DNs servers.

I wrote this to them

Code:
david@david ~/public_html/archives $
dig @192.231.203.132 repository.maemo.org

; <<>> DiG 9.6.1-P2 <<>> @192.231.203.132 repository.maemo.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 35315
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 9, ADDITIONAL: 9

;; QUESTION SECTION:
;repository.maemo.org.          IN      A

;; ANSWER SECTION:
repository.maemo.org.   4505    IN      CNAME  
repository.maemo.org.edgesuite.net.
repository.maemo.org.edgesuite.net. 2793 IN CNAME a515.g.akamai.net.
a515.g.akamai.net.      20      IN      A       150.101.98.85
a515.g.akamai.net.      20      IN      A       150.101.98.80

;; Query time: 34 msec
;; SERVER: 192.231.203.132#53(192.231.203.132)
;; WHEN: Mon Jan 11 11:57:55 2010
;; MSG SIZE  rcvd: 452

david@david ~/public_html/archives $
dig @4.2.2.1 repository.maemo.org

; <<>> DiG 9.6.1-P2 <<>> @4.2.2.1 repository.maemo.org
; (1 server found)
;; global options: +cmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 63053
;; flags: qr rd ra; QUERY: 1, ANSWER: 4, AUTHORITY: 0, ADDITIONAL: 0

;; QUESTION SECTION:
;repository.maemo.org.          IN      A

;; ANSWER SECTION:
repository.maemo.org.   43200   IN      CNAME  
repository.maemo.org.edgesuite.net.
repository.maemo.org.edgesuite.net. 21600 IN CNAME a515.g.akamai.net.
a515.g.akamai.net.      20      IN      A       69.22.138.130
a515.g.akamai.net.      20      IN      A       69.22.138.136

;; Query time: 317 msec
;; SERVER: 4.2.2.1#53(4.2.2.1)
;; WHEN: Mon Jan 11 11:58:07 2010
;; MSG SIZE  rcvd: 146



The issue is Nodes DNS servers keep returning 150.101.98.85/150.101.98.80
for host repository.maemo.org

All other DNS servers I have tested and others have tested are returning
the correct current IP.
This host seems to change IP's somewhat regularly.

Can this be fixed please?
The response was:


.....here is currently no WHOIS record for your domain. When there is no WHOIS record, there is no authoritive name servers specified for your domain, meaning that when a lookup is done, there is no name servers for our DNS to query for an IP address. This is the reason that it isn't working.

Which I can't argue with that.

So who is in charge of this repository.maemo.org?
Looking at maemo.org, we have NS.NOKIA.COM among other DNS servers, but it isn't giving back and answer when I run dig against it.

Code:
david@remote:~$ dig repository.maemo.org @NS.NOKIA.COM

; <<>> DiG 9.5.1-P3 <<>> repository.maemo.org @NS.NOKIA.COM
;; global options:  printcmd
;; Got answer:
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 21278
;; flags: qr aa rd; QUERY: 1, ANSWER: 0, AUTHORITY: 1, ADDITIONAL: 0
;; WARNING: recursion requested but not available

;; QUESTION SECTION:
;repository.maemo.org.          IN      A

;; AUTHORITY SECTION:
maemo.org.              3600    IN      SOA     ns.nokia.com. hostmaster.nokia.com. 2010011701 7200 3600 1209600 3600

;; Query time: 324 msec
;; SERVER: 131.228.20.19#53(131.228.20.19)
;; WHEN: Sun Jan 17 16:31:18 2010
;; MSG SIZE  rcvd: 97
But that doesn't sound like correct DNS protocol, repository.maemo.org should have an authoritative DNS, should it not?

Thanks
 
Posts: 3 | Thanked: 0 times | Joined on Jan 2010
#5
I'm having the same problem.

"could not resolve 'repository.maemo.org'"
 
Posts: 323 | Thanked: 118 times | Joined on Nov 2007 @ Australia
#6
I'm with Internode as well, Just noticed this as well.

Cheers
 
Posts: 323 | Thanked: 118 times | Joined on Nov 2007 @ Australia
#7
Even my VPS in the US can't ping it.
 
Posts: 152 | Thanked: 41 times | Joined on Dec 2009 @ Sydney
#8
My VPS is the US and a shell account in WA both resolve it fine. Works DNS servers resolve it fine, it is only Internode.

I think Internode are by the book and thus not using maemo.org etc to find and use their authoritative DNS servers, other DNS's providers must be taking alternative steps to work it out....

Just theorising
 
Posts: 323 | Thanked: 118 times | Joined on Nov 2007 @ Australia
#9
Kinda strange then. Was working fine last night for me. Today I can't ping it with my Internode connection or from my VPS.

VPS in the US has:

$> ping repository.maemo.org
ping: unknown host repository.maemo.org
 
Posts: 323 | Thanked: 118 times | Joined on Nov 2007 @ Australia
#10
 

The Following 2 Users Say Thank You to RipTorn For This Useful Post:
Reply


 
Forum Jump


All times are GMT. The time now is 02:41.