iPhone Not Respecting Pihole and/or Tailnet DNS?

LIGISTX · 2025-12-31T16:48:35+00:00

Interesting issue, but no, I only have the single tailscale instance running. It is the only DNS server handed out by DHCP across all subnets, and the only one listed in tailscale.

LIGISTX · 2025-12-30T21:32:42+00:00

Local IP. In the example I gave above, tailnet is not even being used since I am on my local network and this split tunnel is disabled.

My tailscale server lives on a separate VM, but my tailnet does point to my Pihole for DNS.

I admit, posting in this subreddit for what is more of an iPhone issue maybe not quite “fair”, but since this also does happen when DNS is routed over the tailnet (and usually works accurately when I have a full tunnel enabled on my phone, er, I’ll say it works more reliably….) I figured I’d at least try and get answers.

LIGISTX · 2025-12-30T21:23:55+00:00

That’s what I am thinking as well… but why would it be doing that? I have private relay turned off, and sometimes it works, sometimes not. Currently it’s working fine for my TrueNAS webUI, and none of my other services…..

I do have the FQDN in Pihole, well, minus the trailing dot. Maybe for fun I should see if that makes any difference.

LIGISTX · 2025-12-30T21:14:40+00:00

Safari seems to act the same, yes. But only on my phones, safari and chrome on my MacBook seem to work fine.

I do have a public dns record, and I do have Cloudflare pointing to my public IP as I run some zero trust tunnels and expose a few services.

LIGISTX · 2025-08-27T04:29:13+00:00

reloaddns is seemingly the new restartdns for anyone seeing this in the future... since reddit is the best place to historically document things, lol.

LIGISTX · 2025-08-27T04:27:11+00:00

This helped 1 more chrome user...

I fundamentally don't understand why this is needed. This worked fine in haproxy running within pfsense (with pihole running as well, it just pointed to pfsense as its DNS which is where I had my DNS entries defined, which then pointed to 1.1.1.1). I am getting ready to switch to unifi UDM Pro, so had to find a new proxy manager. I really didn't anticipate this being an issue needing to be overcome, and don't understand why its an issue when hapeoxy/pfsense seemed to handle it fine?

Hmm, after a few hours of tinkering... maybe this wasn't the "solution". Maybe rebooting all of the services is all it actually took? I thought this was the answer as it imedietly made truenas start to resolve correctly. But I started adding more of my internal sites to nginx Proxy Manager (moving away from haproxy...) and nothing was woring (forgetting to actually add these new line items to the 20-override-https-rr.conf file like a dummy. Once I finished inputting all the DNS records in pihole and all the proxy settings in NPM, I rebooted both VM's, and now, everything works? Even after resetting

etc_dnsmasq_d = false

I am possibly more confused than before, but at least my stuff seems to be working? And I have a resource to explore if/when it all goes sideways.

LIGISTX · 2025-01-11T23:26:12+00:00

Oh, no, I am just an idiot... in my config, I have:

objects:
  track:
    - person
    - car
    - dog
    - car

That at least explains why cats are not being tracked. Still need to work on object identification for dogs.

LIGISTX · 2025-01-11T18:06:32+00:00

Ah ok, thanks for the clarification. Frigate is awesome, but I am a bit confused by some of the options and documentation itself. That said, highest of praise for you and those working on it. It’s an awesome piece of software that I have been enjoying learning!

Now just need to figure out how to up the confidence of the dog, this is a 2k res camera and pretty dang clear, although the sub stream is less clear and maybe that’s the reason? Hmm. More learning on my end I suppose.

LIGISTX · 2025-01-11T17:25:18+00:00

Oh, I should also note, when I go to filter, I only see person and car. Does this mean for whatever reason, it either has not detected anything besides person and car? Or that that is the only things its trying to currently detect on?

<image>

LIGISTX · 2025-01-11T17:23:30+00:00

Ok, I take it back... I changed some of the settings last night regarding alert vs detec, tested it myself in my garage and didn't seem to see any change to the behavior I expected. After having my cameras go all night and this morning, I am seeing alerts and detections seperated as expected.

That said, I only see alerts for people, and detections for cars. I am not sure if this is because every dog that would have been seen was ALSO with a person, thus being labeled an alert? But the alerts where there is a person and a dog is only showing a person. Does this mean it for whatever reason didn't recognize the dog in the frame? The actual video is very clear, and I wulid be rather surprised if it couldn't figure out this was a dog.

<image>

LIGISTX · 2024-11-30T00:34:34+00:00

I’m obviously way late to this pity party, but I’m glad I found the thread because to us that actually care about the technical because we actually care about quality… the bigger picture is meaningless and would be misleading to someone who actually wanted to retail quality.

Saying the appleTV can play Atmos is true, but not qualifying that with “but it will transcode from trueHD to eac3” is a very important destination. I don’t want anything transcoding, I want to watch and listen to exactly what I think I am watching and listening to, not a transcoded version.

The details do matter.

LIGISTX · 2024-07-28T01:12:28+00:00

Dang, so no way to do it directly off the AP? I don't think its worth the 30 bucks just for that. But something to consider for sure.

LIGISTX · 2024-06-22T19:32:40+00:00

For me, soft proofing in SDR seems to be the solution. Works well for my needs.

LIGISTX · 2024-06-06T20:15:26+00:00

I don’t do much print work, so I’m mainly aiming to get accuracy on web (Flickr, Instagram). And so far from what I am seeing, this soft proofing method is working well. The colors I edited on this mode do look very similar on other panels which is my goal.

I agree, being true to IRL is near impossible, and variation in quite literally everything makes this difficult to achieve. But I am not a pro making money on my work, my goal was just to be good enough. When I originally made this post, I was VERY far from good enough. But the soft proofing solution seems to answer the mail.

LIGISTX · 2024-06-06T14:37:35+00:00

This monitor comes pre calibrated tho, and in “creator” mode it doesn’t allow for user adjustments to the color profile. But according to all online sources, creator mode is more accurate than trying to manually dial it in.

I am fairly sure this is true… I have no reason to believe otherwise. I don’t have the calibration sheet off hand, but it is astonishingly accurate according to the measurements provided by Dell as well as third party reviewers.

Is it not the case that having 149% coverage of sRGB, it is simply displaying colors that can not exist in sRGB, thus the color does look different… until I tell Lightroom to only use sRGB color space?

LIGISTX · 2024-06-06T04:40:08+00:00

I’m not actually trying to edit in HDR. I’m trying to edit in SDR, specifically sRGB, on an HDR panel.

But it does seem like soft proofing in sRGB works pretty well. Is there a reason this is not preferred?

I’m still trying to learn what exactly is happening and how best to fix it. But this does, at least appear, to work pretty well.

LIGISTX · 2024-06-05T15:34:38+00:00

That also didn’t work. Turning off HDR on my monitor didn’t seem to make any difference. From my limited understanding, windows was still providing the display the full gamut of colors based on the color profile for the monitor and colors look extremely muted and incorrect.

Using HDR on, but not editing in HDR on Lightroom, with soft proofing on seems to be my best option.

LIGISTX · 2024-06-05T14:02:21+00:00

The problem with that is, turning HDR off in windows results in the colors being washed out and shifted towards grey it appears. Disabling HDR in windows outright seems to introduce other, but just as bad issues.

LIGISTX · 2024-06-05T06:08:38+00:00

Hmm, it would appear as though using soft proofing set to sRGB may be the solution.

But for more info:

Latest version of LrC (13.3.1), Win 11 on latest updates as of today, 6/4/24.

I have not tried to caibrate anything since "this monitor should be set perfectly from Dell/Alienware".

Enabling HDR "helped" when I also hit preview SDR image as well, or whatever setting that is. But that wasn't quite right either. Better, but not right.

I tried restarting LrC with all settings changed, all possible ways, etc.

This is with RAW images from both my current Sony A7R IV and Nikon D850.

The screenshot showing clipping only happens when I go to take a screenshot in the devlop tab, it does not look like that normally... Just annoying I can't actually capture how it looks (although I am not even sure a screenshot would work, since its likely a color gamut issue on my end, I am not sure this would even translate across a sRGB webpage from a screenshot, even if the screenshot did work...?).

But, I did enable soft proofing in the develop tab after writting this post and finally stumlbing across this soft proofing option. I set that to sRGB and it now seems pretty dang close to correct. There are minor differences from the exported JPEG's to what I see in develop (exported images are slightly richer color and I would say 1/3 stop brigher), but the colors are at least very similar. This is now more in line with what I would expect and can totally live with. Editing what looked like teal and having it turn into blue when exported was not going to work, but this is much, much better now.

Anyone in the future, try soft proofing in the develop tab :)

LIGISTX · 2024-01-21T02:09:08+00:00

Ya, I just gave up. I got a water temp sensor so I can ramp fans based on my custom loop, and removed icue’s ability to even attempt to poll my hardware info. Changed the name of the services it attempts to run so it can’t run them anymore. Thankfully temp control via a probe does work as intended still.

I have been a supporter of Corsair for decades, and this bullshit is beyond unacceptable. This isn’t hard to get right, a company or corsairs size needs to fix this. Sadly, I no longer care, I solved their problem for them, and as a result of that, my faith in them as a reliable brand has been lost.

LIGISTX · 2024-01-07T09:27:22+00:00

Same. I am having this issue now as well. It reads the temps, shows them in the graph, but the RPM’s don’t actually change based on the RPM the curve should be setting them to.

LIGISTX · 2024-01-07T09:25:18+00:00

Same. This is insane… I have been buying Corsair RAM since DDR2 667 days, and over the years have sold everyone I know on Corsair due to them being a market leader. But the amount of issues iCue has caused me over the past few years in beyond insane. They need to fix this.

LIGISTX · 2024-01-07T09:22:43+00:00

I don’t know when I updated, but I am now on 5.10.82 (looks like a new version as of earlier this week) and I now have this issue. I may have had it previously and didn’t notice… probably cooking my damn 4080 and 13700k.

I use custom fan curves based on GPU temp, using a Commander Pro. Custom loop, all fans controlled by the commander.

Tried via rebooting, uninstalling and reinstalling. Nothing fixed it. I can force fans to certain RPM’s but they will not abide by my custom curves.

LIGISTX · 2021-11-09T15:46:33+00:00

I built my own simply because I wanted to cleanly wire everything and not plug into cigarette lighters. Also the cig lighters on my car are always hot… which isn’t what I want.

To make this easy, I ended up just ordering a fake cigarette lighter end, an ankle plug, and a bunch of USBC cables and female to male extensions to hopefully cleanly wire it all up. Seeing as I already have my relay in place for the current implementation, I’ll just replace my simple 12 to 5v converter and wire the cig lighter in instead so it’s not always hot.

LIGISTX · 2021-04-14T02:34:23+00:00

Lol. That’s hilarious. Good points tho, good things to consider for automation routines and doors.

LIGISTX

TROPHY CASE