Sigh ... self-inflicted wounds

[jggimi]

I was just typing up a new thread here to ask a question. Yup. Me. I was lost for several hours trying to debug a new configuration problem. I'd just deployed IPv6 on the home network for the first time, but it was only partially working. Domain queries from browsers were returning NXDOMAIN (unresolved domain name), but direct IPv6 URLs were working normally, and debugging tools worked normally.

• ping6(8) and traceroute(6) worked fine by domain name.
• dig(1) was finding AAAA records just fine when I asked for them.
• PF was passing DOMAIN records without blocking them, both over IPv4 and IPv6.

Unfortunately, the queries from the browsers were for A records, not AAAA.

I checked the browsers. Firefox had the default setting of network.dns.DisableIPv6 = False, so it should have received the AF_INET6 resolution. Chrome no longer has this as a user configurable setting.

So I searched, and searched. No results. I added IPv6 domain resolution locally. I changed unbound(1) settings to accept them. I even switched from using local unbound resolving to resolving from Google's IPv6 nameservers, in case it was my local resolution configuration. Nothing seemed to help. So ... I began typing up a problem post in this thread, to ask if anyone here had seen this before. And as I was about to post it, checking for typos (yes, I know, I'm always posting typos even after checking) ... I went back and looked at the resolv.conf file I'd been editing repeatedly for more than an hour. Here's what I finally noticed:

family inet4

Uh. That eliminates any AAAA queries by default. They can be requested specifically, which is what ping6(), traceroute6() and dig() with an AAAA option will do.

So I rewrote this thread. No need to ask for help, now.

[frcc]

That's the type of situations I get into "ALL" the time!, NO Exceptions.....

Correction/Addition
Yea, and if I got the hint of what the problem was, I would have gone to resolv.conf FIRST ONLY
Because I am not smart enough to look where you looked prior to going to that file. Hope this post is taken as meant.

[fvgit]

Originally Posted by jggimi

So I rewrote this thread. No need to ask for help, now.

Heh, I was in a very similar situation just five days ago. I was typing my praise topic for OpenBSD's autoinstall and wanted to add just a minor question pertaining to it just below. But while I was copying over the relevant config files to the daemonforums edit window I realised it was just a typo in my config file. So need to ask for help, either. I think those are the best moments.

[jggimi]

Originally Posted by frcc

I would have gone to resolv.conf FIRST ...

But I'd been staring at the resolv.conf file for two hours, and it is only 7 lines long. How could I miss that???

..Hope this post is taken as meant.

Originally Posted by fvgit

Heh, I was in a very similar situation just five days ago. ... I think those are the best moments.

I don't think they're "best."

[shep]

I burned some bandwith and disk space trying to set up different lpr print ques. Documented my oversights too

[IdOp]

It's good to be self-correcting. I used to have that feature, but these days I'm not so sure, and I think the warranty has expired.

[bsd-keith]

Glad you decided to post, shows that everyone has 'one of those days' now & again.

[sacerdos_daemonis]

Unfortunately, when it comes to computers, I have one of those days every day.