no dns on modem

@XfinityBenny​ I am a Linux user, and was in system administration for a number of years. I used the command

      nmap 10.0.0.1/24

to obtain the listing of devices attached to the local network. The command polls the network command device to report the device information of all the connections. The command returns:

Starting Nmap 7.93 ( https://nmap.org ) at 2024-05-17 10:02 EDT
Nmap scan report for 10.0.0.1
Host is up (0.0088s latency).
Not shown: 990 closed tcp ports (conn-refused)
PORT      STATE    SERVICE
22/tcp    filtered ssh
23/tcp    filtered telnet
53/tcp    open     domain
80/tcp    open     http
111/tcp   filtered rpcbind
443/tcp   open     https
8080/tcp  filtered http-proxy
8181/tcp  filtered intermapper
9000/tcp  filtered cslistener
49152/tcp open     unknown

Nmap scan report for 10.0.0.117
Host is up (0.011s latency).
Not shown: 995 closed tcp ports (conn-refused)
PORT    STATE SERVICE
22/tcp  open  ssh
80/tcp  open  http
139/tcp open  netbios-ssn
443/tcp open  https
445/tcp open  microsoft-ds

The listing shows two of the devices on the network, first is the network channel with all the services available, but there is no line for the device name which should be returned by the DNS. Likewise, the second device that has a name "PiAudio" does not have a listed name. It should be in line 2 of the listing after the IP address. This tells me the internal DNS does not provide the device names. I am able to check that the channel has the proper name information by using the browser interface to access to 10.0.0.1. My question is why doesn't the request show up in my network request?

That's an interesting question, @user_3omh51. If your modem is being managed through the Xfinity app, it could impact the results on the browser interface. Most of the admin functions are directed to the Xfinity app if you have one of our newer gateways, like the XB7 or the XB8.

Sorry, I read the last return message and threw up my hands, because you are missing the point completely. The gateway is a newer XB8-T. The problem is with name registry and DNS service providing named access to server (ie. HTTPS://MyPiServer) should provide access to the named server on my network. It responds with a "not found" error.

The server is accessible using direct IP (ie. 10.0.0.168)

Hello, @user_3omh51! If you prefer more control of the DNS settings, another option would be setting the xFi gateway to bridge mode and using a personal router. This should let you configure the personal router's DNS settings.