Opened 17 years ago

Closed 17 years ago

#5541 closed (fixed)

djangoproject.org not reachable

Reported by: christophrauch@… Owned by: nobody
Component: *.djangoproject.com Version: dev
Severity: Keywords: domain dns
Cc: Triage Stage: Unreviewed
Has patch: no Needs documentation: no
Needs tests: no Patch needs improvement: no
Easy pickings: no UI/UX: no

Description

Despite being found via various search terms (Google, etc.), the domain djangoproject.org (although registered) does not point to the new server. It is definitely a DNS problem.

djangoproject.com is OK.

$ dig www.djangoproject.com
;; ->>HEADER<<- opcode: QUERY, status: NOERROR, id: 51720
[...]
www.djangoproject.com.  600     IN      A       64.207.133.18

djangoproject.org has no records:

$ dig www.djangoproject.org
[...]
;; ->>HEADER<<- opcode: QUERY, status: SERVFAIL, id: 33978

Mediatemple owns the DNS server.

$ whois djangoproject.org | egrep "Name Server:"
Name Server:NS1.MEDIATEMPLE.NET
Name Server:NS2.MEDIATEMPLE.NET
[...]

If the Domain should not be used any longer, I recommend a permanent redirect of http://([^\.]+).djangoproject.org(.*)$ to http://$1.djangoproject.com$2 to redirect all the existing links to the .com domain.

Change History (3)

comment:1 by Jacob, 17 years ago

Resolution: → fixed
Status: new → closed

Oops! I just put in the fix; DNS should propagate shortly. Thanks!

comment:2 by christophrauch@…, 17 years ago

Resolution: fixed
Status: closed → reopened

Jacob, you fixed it... only to reveal another problem. :)

This one comes on www.djangoproject.org and code.djangoproject.org

404 - Not Found
Not Found (no configured vhost)

comment:3 by Jacob, 17 years ago

Resolution: → fixed
Status: reopened → closed

Like ships passing in the night... I think I fixed this moments after you posted this :)

Thanks!

Note: See TracTickets for help on using tickets.
Back to Top