Opened 16 years ago
Closed 16 years ago
#9226 closed (fixed)
djangoproject.com doesn't have a correct reverse DNS entry
Reported by: | Owned by: | nobody | |
---|---|---|---|
Component: | *.djangoproject.com | Version: | 1.0 |
Severity: | Keywords: | reverse DNS IP | |
Cc: | Triage Stage: | Unreviewed | |
Has patch: | no | Needs documentation: | no |
Needs tests: | no | Patch needs improvement: | no |
Easy pickings: | no | UI/UX: | no |
Description
You need to configure a reverse DNS entry for IP address 64.207.133.30
, ie. so that DNS maps the IP address in ARPA notation back to the server name djangoproject.com
.
It prevents receiving of your activation mails sent for each new account. This way you might lose potential users and contributors.
Note:
See TracTickets
for help on using tickets.
This appears to be configured correctly as of right now. If I do nslookup on using my ISP's nameserver, I get back djanoproject.com on the address you cite (and .18, which is what I get when I do the forward lookup). Similarly when I tried various 'reverse DNS lookup' sites found via Google, I did not find any that failed to resolve a djangoproject.com IP address back to djangoproject.com.