#37022: manage.py runserver fails with "nodename nor servname provided" when run
using an rfc6761 hostname
-------------------------------+--------------------------------------
Reporter: Chris Rose | Owner: (none)
Type: Uncategorized | Status: new
Component: Utilities | Version: 5.2
Severity: Normal | Resolution:
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
-------------------------------+--------------------------------------
Old description:
> {{{
> $ uv run manage.py runserver nomnom.dev.localhost:8441
> Watching for file changes with StatReloader
> 2026-04-03T15:53:16.440737Z [info ] Watching for file changes with
> StatReloader [django.utils.autoreload]
> Performing system checks...
>
> System check identified no issues (0 silenced).
> Error: [Errno 8] nodename nor servname provided, or not known
> }}}
>
> `nomnom.dev.localhost` doesn't directly resolve in DNS, but it is a valid
> RFC 6761 special use domain.
>
> I've attached my settings, and because ALLOWED_HOSTS is relevant, here's
> that value from manage.py shell:
>
> {{{
> uv run manage.py shell
> 45 objects imported automatically (use -v 2 for details).
>
> Python 3.13.12 (main, Feb 3 2026, 17:53:27) [Clang 17.0.0
> (clang-1700.6.3.2)] on darwin
> Type "help", "copyright", "credits" or "license" for more information.
> (InteractiveConsole)
> >>> from django.conf import settings
> >>> settings.ALLOWED_HOSTS
> ['nomnom.dev.localhost']
> >>>
> }}}
New description:
{{{
$ uv run manage.py runserver nomnom.dev.localhost:8441
Watching for file changes with StatReloader
2026-04-03T15:53:16.440737Z [info ] Watching for file changes with
StatReloader [django.utils.autoreload]
Performing system checks...
System check identified no issues (0 silenced).
Error: [Errno 8] nodename nor servname provided, or not known
}}}
`nomnom.dev.localhost` doesn't directly resolve in DNS, but it is a valid
RFC 6761 special use domain.
I've attached my settings, and because ALLOWED_HOSTS is relevant, here's
that value from manage.py shell:
{{{
uv run manage.py shell
45 objects imported automatically (use -v 2 for details).
Python 3.13.12 (main, Feb 3 2026, 17:53:27) [Clang 17.0.0
(clang-1700.6.3.2)] on darwin
Type "help", "copyright", "credits" or "license" for more information.
(InteractiveConsole)
>>> from django.conf import settings
>>> settings.ALLOWED_HOSTS
['nomnom.dev.localhost']
>>>
}}}
--
Comment (by Chris Rose):
Nope. I've been utterly unable to get a stack trace to appear. --traceback
did nothing for me either.
--
Ticket URL: <https://code.djangoproject.com/ticket/37022#comment:2>
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/0107019d55036087-65b33264-cb82-4e31-893c-affa70e10cc9-000000%40eu-central-1.amazonses.com.
