On Sun, 2020-02-16 at 14:43 -0700, Joe Zeff wrote:
On 02/16/2020 02:39 PM, Robert G (Doc) Savage via users wrote:
> AT&T U-verse customers are forced to use the DNS service in their
> residential gateway, which would be fine for IPTV and VOIP
> sessions.
How? Does the router block outgoing DNS requests?
U-verse does not allow the user to change the Primary DNS address on
the residential gateway's DHCP configuration page. It is hard-coded to
192.168.1.254, which is the gateway itself. I want to change that to
192.168.1.1 which is the static IP address for my Pi-Hole appliance. If
I could, the Pi-Hole would become a stealthy and very effective whole-
home ad blocker.
There is no technical reason for AT&T to lock this down. I might
understand this for the VOIP and IPTV segments of the gateway. Those
probably have very complex and proprietary DHCP configurations. But for
the Internet data segment, not allowing the user to redirect the
Primary DNS spec is not justifiable. I may be able to use a Ubiquity
EdgeX router to set up a user space downstream from the residential
gateway using a totally different address space from the default
192,168.1.0/24, but I'm running into a WiFi conflict between the
gateway and the EdgeX router I haven't yet been able to resolve.
--Doc Savage
Fairview Heights, IL