Internal DNS not being resolved properly

As of about a month ago after an update (currently I am running 1.73.89), I started running into issues resolving internal DNS addresses. My registrar is PorkBun and I will start seeing the URLs resolve to “parked on the Bun” rather than the internal server. My DHCP hands out internal DNS server addresses. Also, this can happen intermittently. If I try to go to “https://server.internal.com” it will fail, but occasionally, if I go to “https://server.internal/com/ui” it will SOMETIMES work.

For example, if I try to go “https://server.internal.com” which resolves to 10.10.10.10, the page is redirected to the “parked on the Bun” page OR I get a DNS probe error.

If I go to brave://net-internals/#dns and lookup the DNS name, the IP resolves properly and even after clearing the cache, the issue still happens.

I do not use the secure DNS option in Brave either. Also, this is not an issue on any other browser I’ve tried (Chrome, Firefox, Edge).

Any thoughts on this are appreciated!

I hope that you can clarify the following:

internal.com

is a substitute that you are using to make a point in your description? I am asking, because, I used the DNS Lookup tool at:

https://mxtoolbox.com/SuperTool.aspx#

and the IP addresses shown, do not include the “10.0.0.0” subnet.


My guess is, that you used “internal.com” as a substitute for your own domain (not mentioned, here), instead of something like “xzample.com” . . . and . . . you are writing about your share (or dedicated server) that is hosted by _________ (not mentioned, here, but maybe ironically: Akamai?).

You certainly do not have to mention what you do not want to . . . mention.

But, my initial guess, about the trouble you are having, is that somehow, more than 1 DHCP server (or effectively acting as an extra DHCP server) might be a source of that trouble.

Though there is almost always a need to review DNS records that you know about, and attempt to discover DNS records about which, you have not been aware.

And, there may be some DNS issues on your Windows OS machine, in which case - might work:

Clear browsing data on your Windows OS PC

In a Brave Browser New Window, go to:

brave://settings/clearBrowserData

Select the Advanced tab

Set Time range to “All time”

ENABLE everything except:

  • Passwords and other sign-in data

(Myself, I would NOT make that exception)
(because I would have a backup prepared.)
(In other words, be prepared.)

Click on the “Clear data” button


In a Brave Browser New Window, go to:

brave://net-internals/#dns

Click on Clear host cache

Next, same window, select “Sockets” on the left.

Click Close idle sockets

Click Flush socket pools

Quit everything and Restart your Windows OS PC


Flush the Windows OS DNS cache:

Open a Command prompt, then run it as an administrator:

  • Right click CMD
  • Click Run as administrator

Type or paste each command below

  • ipconfig /release
  • ipconfig /flushdns
  • ipconfig /renew
  • netsh int ip reset
  • netsh winsock reset

Then Restart your Windows OS computer.


And locate wherever are the Brave Browser Settings switches that upgrade HTTP to HTTPS, and disable such switches - as a test.

Hey there and thanks for the reply! On the internal thing, you are correct, that is not the domain that I’m using. I was using it as an example. I have done most of that troubleshooting that you mentioned, but it did not resolve the issue.

As for DHCP, I have just one server, my firewall but I do have two DNS servers and they are in sync. The interesting thing is that when I ping an internal domain, it resolves correctly. No other browser manifests this issue either, only Brave.

I did confirm through the #dns page that Brave is resolving the IPs properly and I did flush the data as well but still run into the issue. I did fail to mention that I have a .local domain as well and it always works in Brave on the two sites that I have internally without fail…it’s just the .com internal domains that I have issues with.

I will run through these steps again and see if I see any improvement.

Thank you again!

After going to the advanced section on clear browser data and doing as you suggested, it seems like the issue may have cleared up! Thank you!

I had cleared everything, but not via advanced…just basic. Silly on my part!

Once again, thank you so much!

1 Like

Welp - it worked great for about 4 hours, and then started up again. :frowning: The workaround is to clear the cache like you mentioned, but it comes back again. This time, in about 2 since the first time.

Suggest: Manually setting a fixed IP address for each local DNS server.

Suggest: All local network devices looking to your DHCP server for their IP address (subnet mask, gateway IP address) assignments, use the DHCP server’s fixed IP address.

Good book (I learned from):

Probably also worth its weight:

I’m curious if you have anything setup for your hosts file?
C:\Windows\System32\drivers\etc\hosts

It sounds like the two DNS servers you have might be caching the records for too long. Are they not respecting the TTL for DNS records being looked up?

Hello there!

As of now, my hosts file is blank. I’m assuming that the TTL is fine…when I do a lookup from Brave, the right IP is reported back to me. I have been using Brave for years and just ran into this issue as of about a month and a half ago.

Also, no other browser on this PC has this issue, and I have three others that I’ve tested with.

Hi!
I am experiencing the same problem and looking for a solution to this for at least 2 months now. It is getting on my nerves.

To explain my setup: I have local services running on my network which aren’t publicly accessable, only via the local network or VPN.

When I use Brave, after some random amount of time, my local services won’t resolve and results in an error message ERR_CONNECTION_TIMED_OUT. Pinging the local domainname or IP on Windows CMD does work while Firefox still works, opening a Brave incognito strangely works too, but the non-incognito still doesn’t respond. When I flick the ‘Use secure DNS’ switch (brave://settings/security) on and off everything starts resolving again, and after some time it won’t again…

I’ve also tried Arc and I am experiencing the same problem there so I think this must be a Chromium problem?

Would love to see this solved. All the other forum post about this issue got closed due to the 30 days limit on this forum. Thinking about switching to Firefox because I depend too much on the local DNS for resolving local services.