> >>>>>>> For some reasons, i notice that i am not able to access some website > >>>>>>> in > >>>>>>> the first 10 minutes when i have my machine turned on. > >>>>>> > >>>>>> If you have a broadband on premises equipment like a converter, modem, > >>>>>> router, switch etc, you may consider replacing these, as with age some > >>>>>> of them degrade (in capacitors, solder joints, jacks) and such devices > >>>>>> have trouble working reliably until it warms up (or when they > >>>>>> overheat). > >>>>>> > >>>>>> To report further details to the list, please start a new empty > >>>>>> message. > >>>>> > >>>>> Well,the modem hardware is new. > >>>>> my switches are ok, i have a local server that is up for 24/7, en even > >>>>> that machine is loosing contact to the website. > >>>> > >>>> So you're absolutely sure the hardware environment is fine. There are > >>>> two important tactics to employ then in troubleshooting. First one is > >>>> to bypass every equipment and connect the troubleshooting device direct > >>>> to the upstream connection. Then ensure you have full connectivity and > >>>> move down the line to the point you find your issue. You would follow > >>>> this with the second tactic, drop the configuration from zero and make > >>>> sure you have working connectivity and then start adding each piece of > >>>> the software set up, until you find the part that generates the issues. > >>>> > >>>>> it is pure a dns isue, but what i can resolv, i rewrote the complete > >>>>> named stuff, added even the DNS server pool from that website, heck, > >>>>> still no result... > >>>> > >>>> Try unbound / nsd and see if this gives you a different result. It is > >>>> often just such a simple common issue, that it's hidden in plain sight. > >>>> > >>>> Once you have found it, please report to the list your process+results. > >>>> > >>> > >>> This gonna be fun for me. > >>> But i will do it. > >> > >> I know very well what you mean. Then, if you want to cut time short, > >> you can preemptively start looking direct into the suspected trouble > >> zone, either hardware, equipment configuration and/or software set up. > >> > >> With this second approach, you can ask a direct question once you find > >> the point of hesitation and/or concern. Just walking the trouble path > >> is often enough to get you out of the "unseeing" mode and find it quick. > > > > One more important thing, if you are using the ISP provided name servers > > or name service from the broadband equipment (duh), you can bypass these > > and use own local direct resolving recursive name server on your gateway. > > but i looked this morning in my modem, i readed somewhere the thing > should get new firmware, and surpricingly it had a option in the dns > section where i can add 8 more dns servers.
If you want to resolve it (pun intended), try not putting more name servers after the one with the issues, but ONE only without issues. This means instead of the other name servers, put a local recursive resolving name server, e.g. unbound(8) facing your internal clients: unbound - Unbound DNS validating resolver [http://man.openbsd.org/unbound] Don't forget to edit your /var/unbound/etc/unbound.conf file as per: unbound.conf - Unbound configuration file [http://man.openbsd.org/unbound.conf] Also, make sure your DHCP server provides the local internal listening IP address of the local unbound(8) name server to your local clients. If in doubt, disable all name servers and DHCP options in your modem and simply use unbound(8) and dhcpd(8) on your local OpenBSD gateway dhcpd - Dynamic Host Configuration Protocol (DHCP) server [http://man.openbsd.org/dhcpd] dhcpd.conf - DHCP server configuration file [http://man.openbsd.org/dhcpd.conf]
