Unresolvable DNS Entries
-
The good news is that it seems like the domain override worked this time. I did it exactly as I did last time, but now I'm wondering if I didn't give it enough time after restarting the forwarder service and renewing my DHCP lease or something. All I know is that I changed the settings, verified I didn't break the network, and then had to head into a meeting. Came out of the meeting, and now it's working properly.
And to reiterated/clarify:
Under general settings I have "ourwebsite.com" and under DHCP there's no search domain specified, but under DNS Forwarder there's a Domain override with "localdomain" for the domain field, and "!" for the IP field.
And of course, I can still access my appliances via hostname. Lovely.
Here's my log, and man this can be tough to hunt down when you've got so much traffic going on. Thanks for the help though. I'm not 100% positive I found all the relative lines to this one request, as it was spread accross about 50 lines, but I think that's all of it.
Feb 24 15:03:50 dnsmasq[87210]: reply www.qwwersdfretdfg.com is NXDOMAIN-IPv4 Feb 24 15:03:50 dnsmasq[87210]: forwarded www.qwwersdfretdfg.com to 8.8.8.8 Feb 24 15:03:50 dnsmasq[87210]: query[A] www.qwwersdfretdfg.com from 192.168.16.19 Feb 24 15:03:50 dnsmasq[87210]: reply qwwersdfretdfg.com is NXDOMAIN-IPv4 Feb 24 15:03:50 dnsmasq[87210]: forwarded qwwersdfretdfg.com to 8.8.8.8 Feb 24 15:03:50 dnsmasq[87210]: query[A] qwwersdfretdfg.com from 192.168.16.19 -
The good news is that it seems like the domain override worked this time. I did it exactly as I did last time, but now I'm wondering if I didn't give it enough time after restarting the forwarder service and renewing my DHCP lease or something. All I know is that I changed the settings, verified I didn't break the network, and then had to head into a meeting. Came out of the meeting, and now it's working properly.
And to reiterated/clarify:
Under general settings I have "ourwebsite.com" and under DHCP there's no search domain specified, but under DNS Forwarder there's a Domain override with "localdomain" for the domain field, and "!" for the IP field.
And of course, I can still access my appliances via hostname. Lovely.
Here's my log, and man this can be tough to hunt down when you've got so much traffic going on. Thanks for the help though. I'm not 100% positive I found all the relative lines to this one request, as it was spread accross about 50 lines, but I think that's all of it.
Feb 24 15:03:50 dnsmasq[87210]: reply www.qwwersdfretdfg.com is NXDOMAIN-IPv4 Feb 24 15:03:50 dnsmasq[87210]: forwarded www.qwwersdfretdfg.com to 8.8.8.8 Feb 24 15:03:50 dnsmasq[87210]: query[A] www.qwwersdfretdfg.com from 192.168.16.19 Feb 24 15:03:50 dnsmasq[87210]: reply qwwersdfretdfg.com is NXDOMAIN-IPv4 Feb 24 15:03:50 dnsmasq[87210]: forwarded qwwersdfretdfg.com to 8.8.8.8 Feb 24 15:03:50 dnsmasq[87210]: query[A] qwwersdfretdfg.com from 192.168.16.19Yeah that looks about right. Glad you got it working. It could have been cached dns on your client. On windows you can ipconfig -flushdns. You can access your website still properly?
-
Yea, I'm on OSX and hadn't done a true flush, just a DHCP renew. Probably was the problem the first go around, since I don't specifically remember changing the URL.
And yes, we can still access our site internally, even the legitimate wildcards. An invalid wildcard turns up our website too, exactly as it would for people on the outside of our network.
Thanks so much for the help! Time to backup the config again…
-
Adding a domain over-ride with IP of "!" solved this problem for me… I wonder how common it is for new users. Seems like a good tip for FAQ if it doesn't already exist.