Could someone please do an FAQ on how I can manually add a TXT record into Pi-hole?
I've just got it setup and so far its working great blocking adds and generally speeding up the internet.
I run an applecaching service accross two internet connections. So I need to add a DNS TXT record. Apple server gives me the bind command which is:
_aaplcache._tcp 259200 IN TXT "prs=CONNECTION1,CONNECTION2"
On my windows box it was easy with a DNS command. However I am not that great with Linux. Big learning curve...
you've not seen my youngest daughter. at 13 months she was swiping to unlock an ipad then bashing the screen to open apps usually got safari open...
Now at almost 4 she has her own iPad and plays peppa pig games (with headphones)
Once she starts reading a bit better I'm gonna try and get her and her older brothers involved with Swift.
I ask for instructions a 5 year could follow becuase thats about my level of understanding.
I tried:
dnsmasq txt-record=_aaplcache._tcp,"92.xxx.xxx.xxx,81.xxx.xxx.xxx"
also tried:
dnsmasq txt-record=_aaplcache._tcp,"92.xxx.xxx.xxx, 81.xxx.xxx.xxx"
But it returns junk found in command.
I then tried:
dnsmasq -txt-record=_aaplcache._tcp.FQDN,"92.xxx.xxx.xxx, 81.xxx.xxx.xxx"
And now I get
dnsmasq: failed to create listening socket for port 53: Address already in use
Even changing my line:
txt-record=_aaplcache._tcp,_aaplcache._tcp,"prs=92.xxx.xxx.xxx, 81.xxx.xxx.xxx"
or
txt-record=_tcp,_aaplcache._tcp,"prs=92.xxx.xxx.xxx, 81.xxx.xxx.xxx"
I've also tried it without prs= but I think the OS X server requires that!
is
pihole restartdns
The correct command or should I be using something else?
Wow just as I thought I was starting to understand it you throw all those numbers and symbols at me. Maybe the bone hit me on the head and those are the birds tweeting round noggin
I've changed my line to exactly the same as your example and I get the same result as I did before when I had .domain.com added to it.
I am sure I had already tried that configuration and it didn't work. Maybe I had a typo!
When I had the domain.com added I tried the Assetcachelocatorutil from the mac and it didn't return any configured public IP address. My understanding is it pulls the public IP's from the DNS record by querying _aaplcache._tcp. Which is only needed if using multiple public IPs. I think but again could and probably I am wrong.
The Mac is currently downloading a file. I'll give it a reboot once its finished to refresh its DNS. Then I'll the locator util again
Dig returns a result as above. Even if I run it on the Mac it gets the same result. Expected as Mac is using PiHole for its DNS.
If I run Assetcachelocatorutil on the mac mini it doesn't find any configured public IP address. But it does find the content cache (Its on the mac mini) so thats expected
Then on a mac book also using PiHole as DNS I get same dig result (expected) and if I run Assetcachelocatorutil it doesnt find any content caches and also states no public IP address configured.
They are on the same subnet but Firewall uses different internet connection for them. but it should see the cache as they are on the same subnet (at least it did when using windows)
I've tried it all combinations of adding search domain and a trailing DOT.
If I dig _aaplcache._tcp @windows-domain-server
I get the same results as having my applecache.conf set to:
Reading the link you provided it states that the TXT record needs to be published in the default search domain. With that in mind am I still creating \ editing the file in the correct location '/etc/dnsmasq.d/applecache.conf'
Or should I be placing it somewhere else?
Unfortunately I am out of time here. I have reverted back to using the windows DNS but use the PiHole as a forwarder so the AD-Blocking still works. Just makes it a little more difficult to to narrow down client issues.
I am going to have a read up a little more on DNS within linux. To try and get a better understanding of how it works in Linux.
My caching now works, and using windows as my DNS I get the same results with DIG TXT _aaplcache._tcp as I did when using PiHole directly.