Weird Domains

Oh ps, that CN TLD is conflicting with Internet DNS:

$ whois cn.
[..]
domain:       CN

organisation: China Internet Network Information Center (CNNIC)
address:      No. 4, South 4th Street
address:      Zhong Guan Cun
address:      Beijing 100190
address:      China

EDIT: If you can configure that CN name in the router, you could change it into one of the recomendations at the bottom of that Multicast DNS RFC:

Appendix G. Private DNS Namespaces

The special treatment of names ending in ".local." has been
implemented in Macintosh computers since the days of Mac OS 9, and
continues today in Mac OS X and iOS. There are also implementations
for Microsoft Windows [B4W], Linux, and other platforms.

Some network operators setting up private internal networks
("intranets") have used unregistered top-level domains, and some may
have used the ".local" top-level domain. Using ".local" as a private
top-level domain conflicts with Multicast DNS and may cause problems
for users. Clients can be configured to send both Multicast and
Unicast DNS queries in parallel for these names, and this does allow
names to be looked up both ways, but this results in additional
network traffic and additional delays in name resolution, as well as
potentially creating user confusion when it is not clear whether any
given result was received via link-local multicast from a peer on the
same link, or from the configured unicast name server. Because of
this, we recommend against using ".local" as a private Unicast DNS
top-level domain. We do not recommend use of unregistered top-level
domains at all, but should network operators decide to do this, the
following top-level domains have been used on private internal
networks without the problems caused by trying to reuse ".local." for
this purpose:

  .intranet.
  .internal.
  .private.
  .corp.
  .home.
  .lan.

https://www.rfc-editor.org/rfc/rfc6762.html#appendix-G

Or home.arpa which is a more recent RFC and has added protection when local queries unintentinaly leak to the Internet DNS servers upstream:

$ xargs -n 1 whois <<< 'intranet. internal. private. corp. home. lan. home.arpa.'
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
No whois server is known for this kind of object.
[..]
domain:       HOME.ARPA
[..]
contact:      technical
name:         Internet Assigned Numbers Authority (IANA)
organisation: Internet Corporation for Assigned Names and Numbers (ICANN)
[..]
remarks:      This domain is administered as part of the .ARPA zone
remarks:      management, described at https://iana.org/domains/arpa
$ dig dummy.name.home.arpa.
[..]
;; ->>HEADER<<- opcode: QUERY, status: NXDOMAIN, id: 27385
[..]
;; AUTHORITY SECTION:
home.arpa.              900     IN      SOA     prisoner.iana.org.
hostmaster.root-servers.org. 1 604800 60 604800 604800

About above prisoner.iana.org.:

https://www.iana.org/help/dns-blackhole