#37022: manage.py runserver fails with "nodename nor servname provided" when run
using an rfc6761 hostname
-------------------------------+--------------------------------------
Reporter: Chris Rose | Owner: (none)
Type: Uncategorized | Status: closed
Component: Utilities | Version: 5.2
Severity: Normal | Resolution: worksforme
Keywords: dns runserver | Triage Stage: Unreviewed
Has patch: 0 | Needs documentation: 0
Needs tests: 0 | Patch needs improvement: 0
Easy pickings: 0 | UI/UX: 0
-------------------------------+--------------------------------------
Comment (by Chris Rose):
`nomnom.dev.localhost` does not resolve for me in DNS.
https://datatracker.ietf.org/doc/html/rfc6761#section-6.3 suggests that
it's supposed to resolve to loopback.
{{{
$ ping nomnom.dev.localhost
ping: cannot resolve nomnom.dev.localhost: Unknown host
$ dig @ns-59.awsdns-07.com nomnom.dev.localhost
$ dig @8.8.8.8 nomnom.dev.localhost
$ dog @8.8.8.8 nomnom.dev.localhost
Status: NXDomain
SOA 23h59m55s A "a.root-servers.net." "nstld.verisign-grs.com."
2026040400 30m00s 15m00s 7d0h00m00s 1d0h00m00s
}}}
From what I can tell, it doesn't resolve anywhere, so I'm not sure what my
local setup is going to be doing with it.
At a bare minimum I sure would love it if `--traceback` would show me
where this resolution is happening, so that I can attempt to troubleshoot
it in more detail, but I can't get a stack trace out of that command.
--
Ticket URL: <https://code.djangoproject.com/ticket/37022#comment:4>
Django <https://code.djangoproject.com/>
The Web framework for perfectionists with deadlines.
--
You received this message because you are subscribed to the Google Groups
"Django updates" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To view this discussion visit
https://groups.google.com/d/msgid/django-updates/0107019d58c14365-22c2ba83-2601-43a4-aaec-df7a87d3aaf1-000000%40eu-central-1.amazonses.com.
