Home Network Community > Wi-Fi Routers > How To Change PORT For Upstream DNS Server
< Wi-Fi Routers

How To Change PORT For Upstream DNS Server

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.

How To Change PORT For Upstream DNS Server

This thread has been locked for further replies. You can start a new thread to share your ideas or ask questions.
How To Change PORT For Upstream DNS Server
How To Change PORT For Upstream DNS Server
2024-10-31 20:58:55
Model: Archer AXE5400  
Hardware Version:
Firmware Version:

Hello,

 

I own a AEX5400 WiFi router (which works great).

 

Q:  Is it possible to configure:    Network -> DHCP Server -> "Secondary DNS",  using a another port (rather than than the default port 53)?

 

I've installed a local Pi-hole/cloudflared docker on a RPI5 that accepts DNS requests on port 4353 (rather than the default/assumed port 53).

I've not attempted to specify something like:   ELERPI5:4353,   in the configuration screen (yet).

 

Thanks for any hints.

 

EricLEdberg

 

My RPI has the default DNS configuration blocking port 53 which I don't want to mess with if I can help it....

 

 

 

 

 

 

 

  0      
 
  0      
 
#1
Options
2 Reply
Re:How To Change PORT For Upstream DNS Server
2024-11-01 20:39:58

  @EricLEdberg 

 

Hi Eric, Unfortunately, that feature is not supported by the router. The DNS protocol specifies port 53 and cannot be changed. 

What's New? Sync Your Tapo Doorbell and Door Lock Optimize Your Network with the Wi-Fi Toolkit App Join our Official Subreddits: r/tplink, r/tapo, and r/omada_networks
  0  
  0  
#2
Options
Re:How To Change PORT For Upstream DNS Server
2024-11-01 20:50:01 - last edited 2024-11-01 20:51:53

Thanks for the quick answer, which is what I assumed....

  • On my RPI, I disabled "system.resolved" (enabled by default) and started Pi-hole using the default dns port 53.
  • On my AXE5300, my DHCP primary DNS resolver is now the RPI IP; the secondary being the AXE5300 router itself for local host names that Pi-hole didn't/can't resolve...
  0  
  0  
#3
Options

Information

Helpful: 0

Views: 564

Replies: 2

About Us
Press
Copyright © TP-Link Systems Inc. All rights reserved.