Mastodawn

looks like there are DNS troubles today.
for those who may not know, I run my own inhouse #dns #server at home using #adguard / #adguardhome . well, while I was gone, it took a shit, and the DNS server wasn't sending much back.
went to start the windows service, and get a "could not start" issue.
well I figured out that my (local) IP had changed from 192.168.1.7 to 192.168.1.9 , meaning nothing could actually get through. and Adguard was *hard coded) to use the 1.7 range had to change that, and now it should work regardless of IP

Show thread

Andrew Hodgson 1d ago

@adisonverlice You should ideally set the machine that AdGuard is running on to be static. I do this from the router itself using a DHCP reservation. You can then use that static IP address for other machines on your network as their DNS server. If AdGuard is running on your local Windows machine, you can set the DNS resolver on that box to 127.0.0.1 which will also work meaning that it uses the loopback interface.