Business CommunityGatewaysLAN DNS CNAME record pointing to IP record
Gateways

LAN DNS CNAME record pointing to IP record

LAN DNS CNAME record pointing to IP record

LAN DNS CNAME record pointing to IP record
LAN DNS CNAME record pointing to IP record
2026-02-11 19:07:45 - last edited 2026-04-23 06:25:01
Model: ER706W  
Hardware Version: V1
Firmware Version: 1.2.2 Build 20250821

Hello,

I want to set my LAN DNS entries to point to the Nginx Proxy Manager IP entry.
I created an IP record with the following settings:
Domain name: nginx.lan.domain

Type: IP
IP Address: 192.168.10.123
Apply To Lan: MyVLAN

 

It is correctly resolved by the nslookup query.

 

Later, I createda  CNAME record with settings:
Domain name: grafana.lan.domain
Type: CNAME
CNAME: nginx.lan.domain

Apply To Lan: MyVLAN

When running nslookup grafana.lan.domain I get only "** server can't find grafana.lan.domain: NXDOMAIN"

What could be the case?
In the DHCP settings, I set up two DNS servers - 192.168.10.1 and the IP of my PiHole server.

  0      
0
#1
Options
1 Accepted Solution
Re:LAN DNS CNAME record pointing to IP record-Solution
2026-04-17 03:27:52 - last edited 2026-04-23 06:25:01

 

Hello,@Kamool 

We are writing to follow up and confirm whether your previously reported issue has been resolved.
 

You currently have two DNS servers configured: 192.168.10.1 and a Pi-Hole instance. When clients initiate DNS queries, requests may be routed to either server. A potential cause of the issue you encountered is that the CNAME record you created may not be recognized or cached by the Pi-Hole server. If a client’s query happens to be sent to Pi-Hole, and neither Pi-Hole’s upstream DNS nor its local records contain an entry for grafana.lan.domain, Pi-Hole will return an NXDOMAIN response.

We would like to recommend the following troubleshooting steps for your reference:

Add an A record that maps grafana.lan.domain to 192.168.10.123 in Pi-Hole’s local DNS records.
Alternatively, you may temporarily set 192.168.10.1 as the sole DNS server on your client, then test whether the query nslookup grafana.lan.domain 192.168.10.1 returns a successful result.

After adjusting the configuration, please clear the DNS cache on both your Pi-Hole server and test on the client.

Thank you for your cooperation.

 

Recommended Solution
  0  
0
#5
Options
4 Reply
Re:LAN DNS CNAME record pointing to IP record
2026-02-12 08:04:22

Hi  @Kamool 

Thanks for posting in our business forum.

May I ask what is your network topology as well as the configuration screenshots?

If possible, may I check the error page as well when you use the Type as CNAME?

Best Regards! >> Omada EAP Firmware Trial Available Here << >> Get the Latest Omada SDN Controller Releases Here << *Try filtering posts on each forum by Label of [Early Access]*
  0  
0
#2
Options
Re:LAN DNS CNAME record pointing to IP record
2026-02-12 17:44:32

  @Hank21 

When it comes to my network topology:
Provider fiber -> ONT -> ER706W <-wireless-> EAP670 <-LAN-- (Home server with hosted Omada controller)

This is the configuration for Nginx:


Configuration for Grafana CNAME:


What errors are you looking for? I'm not getting any.

  0  
0
#3
Options
Re:LAN DNS CNAME record pointing to IP record
2026-04-05 08:08:23
Any idea on that?
  0  
0
#4
Options
Re:LAN DNS CNAME record pointing to IP record-Solution
2026-04-17 03:27:52 - last edited 2026-04-23 06:25:01

 

Hello,@Kamool 

We are writing to follow up and confirm whether your previously reported issue has been resolved.
 

You currently have two DNS servers configured: 192.168.10.1 and a Pi-Hole instance. When clients initiate DNS queries, requests may be routed to either server. A potential cause of the issue you encountered is that the CNAME record you created may not be recognized or cached by the Pi-Hole server. If a client’s query happens to be sent to Pi-Hole, and neither Pi-Hole’s upstream DNS nor its local records contain an entry for grafana.lan.domain, Pi-Hole will return an NXDOMAIN response.

We would like to recommend the following troubleshooting steps for your reference:

Add an A record that maps grafana.lan.domain to 192.168.10.123 in Pi-Hole’s local DNS records.
Alternatively, you may temporarily set 192.168.10.1 as the sole DNS server on your client, then test whether the query nslookup grafana.lan.domain 192.168.10.1 returns a successful result.

After adjusting the configuration, please clear the DNS cache on both your Pi-Hole server and test on the client.

Thank you for your cooperation.

 

Recommended Solution
  0  
0
#5
Options

Information

Helpful: 0

Views: 316

Replies: 4