DSN pointing to router IP

Kaveman
Contributor

Hi all, 

I connected to the bell router configuration page and updated my DSN settings to use Google DSN (8.8.8.8 -> primary and 8.8.4.4 -> secondary).  I need to use a public DNS, like Google, for some work applications, hence the changes.

Even though the correct IP addresses are shown on the router configuration page, when looking at the DSN servers on my computer, the primary DSN server points to 198.168.2.1, which is my router's IP address.  

Using 3rd party tools on my Android phone for network checks also indicates the router IP address as my DSN server.

Is there any reason why the DSN configured on the router is not taking effect? I have saved multiple times and rebooted the router several times as well with no luck.

 

DNS pointing to RouterDNS pointing to RouterRouter DNS configurationRouter DNS configuration

 

 

 

0 9 7,278
1 helpful reply

Accepted Solutions

Vanadiel
Community All-Star
Community All-Star

The router uses whatever DNS servers you provided, in your case 8.8.8.8 and 8.8.4.4. If providing none it uses the default ISP DNS servers.

When using DHCP, it will automatically configure your TCP/IP parameters. In this case, your router is the gateway and it hosts a DNS service, hence your DNS is pointed to the same location where the service is located.

So PC->router DNS service->8.8.8.8

 

 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

View reply in original post

9 REPLIES 9

Vanadiel
Community All-Star
Community All-Star

The router uses whatever DNS servers you provided, in your case 8.8.8.8 and 8.8.4.4. If providing none it uses the default ISP DNS servers.

When using DHCP, it will automatically configure your TCP/IP parameters. In this case, your router is the gateway and it hosts a DNS service, hence your DNS is pointed to the same location where the service is located.

So PC->router DNS service->8.8.8.8

 

 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

It's possible to setup on my Giga Hub with firmware version 1.19.6 a DNS overt HTTPS ?

You can change the default DNS servers to let's say 1.1.1.1 and check afterwards here to verify it's setup correctly.

There is a picture here of the page where you can manually configure a primary and secondary DNS server for your home hub. You will need to log into your home hub as administrator to do so.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

That does not anser my question.. I know how to change my DNS.. but my question is about DNS over HTTPS .. or DoH .. it's possible ?

You need a DNS server that allows that protocol to be used.

I use 1.1.1.1 myself and have it configured as DNS server rather then the Bell DNS default server.

I have DNS over HTTPS available and enabled as per the test site I linked above. (Cloudflare).

 

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

I already have a DNS server that allows DoH (DNS over HTTPS) 

By default 1.1.1.1 or others servers are not encripted .. the message are sent in plain text.. but if you are able to user DOH the message are going to be encripted.

In other words.. all the call you make to 8.8.8.8, 1,1,1,1 or even Bell DNS are in plain text not encripted.

That's why I'm looking a way to setup DoH (DNS over HTTPS )or DoT (DNS over TLS).. totally different from DNS.

Connected to 1.1.1.1Yes
Using DNS over HTTPS (DoH)Yes
Using DNS over TLS (DoT)No
Using DNS over WARPNo
AS NameCloudflare
AS Number13335
Cloudflare Data CenterYYZ

See the second line...

Using DNS over HTTPS (DoH)Yes
I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

Vanadiel
Community All-Star
Community All-Star

Or you can try this test 

I pass everything except Secure SNI, but that is not widely adopted yet.

I do pass secure DNS.

Secure DNS

Nobody listening on the wire can see the DNS queries you make when you are browsing the Internet.

All by configuring 1.1.1.1 as DNS server.

Traditionally, DNS queries are sent in plaintext. Anyone listening on the Internet can see which websites you are connecting to.

To ensure your DNS queries remain private, you should use a resolver that supports secure DNS transport such as DNS over HTTPS (DoH) or DNS over TLS (DoT).

The fast, free, privacy focused 1.1.1.1 resolver supports DNS over TLS (DoT), which you can configure by using a client that supports it. For a list of these take a look here. DNS over HTTPS can be configured in Firefox today using these instructions. Both will ensure your DNS queries remain private.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.

Vanadiel
Community All-Star
Community All-Star

And you can also see the Wiki: Wikimedia DNS 

Do I need to install some extra software to use this?

[edit]

All major desktop and mobile operating systems and browsers support either DoH or DoT in 2023. Users will need to point their browser/OS to Wikimedia DNS but no extra software is required.

There are no discovery mechanisms for DoH and DoT yet, so the configuration is still manual; the hostname or IP address of the service is all that is required for someone to use the service.

If you don't want to use Wikimedia DNS nothing will change for you.

I am a Community All-Star and customer. I'm here to help by sharing my knowledge and experience. My views on Bell and the Community Forum are my own and not the views of Bell or any of its affiliates.